XMPP Council - 2016-09-28

it is time

0) Roll call

Peter sends apologies

here

Here

Dave Cridland?

I'm not aware of any voting items for today

1) Date of next

sbtsbc?

wfm :)

2) Elections

Just a FYI, elections will be coming up soon

I'm not planning on running for next term

3) AOB?

no AOB here

thanks Tobias

thank you

We should do some recruiting

Dave Cridland, btw: any news regarding Matrix's Olm?

Tobias, Dave Cridland: RE Olm, I think I might have forgotten to paste it in this room, it's public domain. It's in the spec's RST file.

Apologies for the confusion last week.

Yes, indeed - I'd assumed SamWhited has effectively solved his own problem.

Tobias, I’ve been sending them some patches to make it installable and packageable, but haven’t really played with it yet.

SamWhited, isn’t public domain a concept that doesn’t exist everywhere and thus could cause issues in those countries?

Dave Cridland, so..what would be the next step? adjust the OMEMO spec to use OLM and resubmit it to get a number on it?

Link Mauve: No idea; that's getting too far into the legal weeds for me to think it's worth caring about

Heh.

Tobias: https://github.com/xsf/xeps/pull/248

More changes are needed

SamWhited, oh..didn't notice that PR, will give it a read/review

Tobias: It's really just terminology changes; no actual technical changes have been made yet.

And there's still some random Axolotl terminology scattered throughout.

does any change to a draft XEP require council vote?

non editorial, yeah

which one needs an update?

https://github.com/xsf/xeps/pull/219

i don't have permissions do merge, so i just left a comment

i don't have permissions to merge, so i just left a comment

We really need to automate publishing XEPs more (I say despite having no desire to be the one to do it)

I think that 219 should have a Council vote.

Kev, what requires a council vote and what not? shouldn't that be specified somewhere?

I think that it is a clarification of existing text, but it's existing text that has been widely ignored, and I don't think the Editors should take it upon themselves to do that.

Kev, it just clarifies the existing description and doesn't change any meaning of the document IIUC

Tobias: In theory it's any change to Draft, but we (Council) agreed a few years ago that anything that's obviously only editorial the Editors could sort out, IIRC.

Kev, is that defined in XEP-0001?

Yes, that's right. But I think that it makes clear that people haven't been implementing it the way it's written, and therefore I'd rather Council gave their blessing.

Given it doesn't really hurt Council to review the change.

Goodness knows, I don't remember which bits are in the XEPs, or the bylaws, and which bits are just things Council have voted over the years.

but our council meetings are allready packed full :P

Obviously.

XEP-0001 Section 8.1: Any changes to a Draft XEP that could reasonably be construed as material must be provisionally published at <http://www.xmpp.org/extensions/tmp/>, announced and discussed on the Standards mailing list, and formally approved by the XMPP Council before being officially published at the canonical URL for the XEP. Ultimate authority for Draft XEPs rests with the XMPP Council, which can at its discretion demand the reversal of any changes made by the XMPP Extensions Editor or the XEP author while the XEP is in the Draft state.

ahh..ok

i'll add it to the trello then for next week

Lance, btw, ping again for https://github.com/xsf/xeps/pull/223