XMPP Council - 2020-10-21

I'm still sitting in a conference call and can't promise my attention

1) Roll Call

!

Hiya.

(Just in time!)

do we get a daniel?

hi

excellent

2) Agenda Bashing

anything?

taking that as a no.

3) Editor’s Update - Accepted XEP-0352 (Client State Indication) as Draft - Accepted XEP-0411 (Bookmarks Conversion) as Draft

4) Items for voting

4a) MR!22: add composer, date, genre, language, lyricist, and performer tags; make rating optional URL: https://gitlab.com/xsf/xeps/-/merge_requests/25/diffs Abstract: It seems, that "XEP-0118: User Tune" has been written mainly with pop music in mind, or maybe progressive rock. To make it more interesting for use with classical music or jazz, or audio books, some tags should be added, at least composer, date, genre, language, lyricist, and performer.

Hm, Draft

indeed

and non-versioned namespace

too

not sure what to do with this

would it make sense to put the new stuff in a separate namespace but under the same child?

My gut feeling on this is that the better solution might be to create an entirely new User Tune kind of thing. I'm guessing that there's probably a lot more other/prior art here now, thanks to the likes of Spotify etc.

probably what dwd said

i don’t really have an opinion on that tbh

At least better to explore that avenue first.

do people actually use that?

from a practical perspective, I think no harm is done by adding elements scoped into a different namespace under the same <tune/> ✏

daniel, Yes, though Edwin Mons has been listening to the same music for possibly decades now.

it’s obviously a 90% solution only, however, I doubt that we can get a 100% solution

There's probably not much harm in accepting this either, unless someone has a strict schema validator.

dwd: That sounds likely, TBH.

Kev, I admit the "progressive rock" reference in the PR did make me think of him...

Version 1.2 (2008-01-30) > Added rating element.

Hmmmmm

I’ll be bold and vote +1 on this.

Zash, nice find!

Myeah, +1

I think I'm -0.

any other votes?

What is the harm in namespacing it, vs the known harm of not doing so?

If someone does find a Right Proper standard for audio metadata that we could point to, that'd be cool as a User Tune 2

I'm on-list

Kev, complicates implementations

Kev, round trip with the MR author causing friction vs. potential strict schema validators breaking

if I vote -0 it takes a +1 from Ge0rG for it to go through right?

daniel, true

-0 then

haha

neat

moving on

jonas’: I note that those *are* a thing. People do deploy checkers to ensure content conforms to specs.

daniel, Ge0rG can take the pressure.

4b) Propose Martin Dosch as Editor

+1

+1

+1

+1

I have had, I think, little contact with him, but anyone willing to put in the work sounds like a good idea, so +1.

(formerly known as !XSF_Martin in xsf@)

Oh.

(I feel this falls far short of "backwards-incompatible modifications shall be avoided if at all possible" FWIW, but will drop it now)

(nowadays known as mdosch) ✏

Kev, you’re right

5) Date of Next

+1w?

(logs into calendar thing to find out)

+1w wfm

+1w should wfm, but it’s RIPE GM in that week, so I may not be able to chair

+1w wfm

hoping that we’ll get quorum next week then

6) AOB

None here

ok, I’ll go ahead then: Elections are coming up

put up your application if you want to (deadline is 2020-11-08) and/or encourage folks from the community of whom you’d think they’d be good in this role

that’s it

7) Ite Meeting Est

thanks everyone

thanks Tedd

Thanks

dwd, reminder that you wanted to start a thread on OOB vs. SIMS vs. ??? in the context of the CFE for http upload

Hmmmmmm, will I have more spare cycles next year?

if 2020 taught us anything, it’s how unpredictable the world is *shrug*

Yes, I will.

In fact I've got the CFE up to reply to already. Just haven't written the email, but I will do now.

neat :)

> Any changes to a Draft XEP that could reasonably be construed as material must be *provisionally published, announced and discussed on the Standards mailing list*, and formally approved by the XMPP Council

Zash, Process Smash!

Zash, Although I'm a lot more comfortable when changes are thoroughly discussed within the community.

Relevant discussion: https://logs.xmpp.org/xsf/2020-09-12?p=h#2020-09-12-7b989cb42bd803af