theadmiraltyjonas’: the portion regarding zash and ipv6
Ge0rGLooks like I'll be late to the party. I'm having fun yelling at incompetent consultants.
mdosch> theadmiralty, explain your amusement please
The Tedd style of writing boring facts down in an amusing way probably. 😃
ZashStrategic brewing of coffee successful
mdosch> Coffee overflow.
Terrible. Get bigger coffee cups?
mdosch> Coffee overflow.
Terrible. Get bigger coffee cups!
Ge0rGmdosch: I have a 370ml cup already. The overflow happens in my body
Ge0rGWow, the call ended just on time for the Council, only 27 minutes overtime.
Zash3 minutes of rest!
jonas’also fun: I still need to write emails
jonas’I’m going to be distracted, I’m sorry for that
jonas’1) Roll Call
Ge0rGis in a post-conference-call phone-call
jonas’explaining to a customer how the internet works and that we cannot inform them every time when they won’t be able to reach our site because some transit network fubar’d
jonas’2) Agenda Bashing
jonas’(this time with correct date!)
ZashWhat Tedd pointed out earlier
jonas’3) Editor’s Update
jonas’- Proposed XMPP Extensions:
- DOAP usage in XMPP
- OMEMO Media Sharing
jonas’4) Items for Voting
Ge0rGI started reading the agenda multiple times, but then got distracted over and over again. Sorry.
jonas’4a) Proposed XMPP Extension: DOAP usage in XMPP
Abstract: This specification defines how XMPP projects can provide a machine-readable description of their abilities, and how external entities can interact with it.
jonas’I am on list, I did not have a minute of non-work time today yet.
danielare XEPs the right format to specify something that isn’t an extension?
danieli mean as a spec the document looks fine
jonas’daniel, if it defines how XEPs are to be used or referenced to, I think it’s borderline OK
dwdI hadn't seen the submission. Not sure what track this should be. Happy for it to be a XEP, though - perhaps even Procedural?
ZashInformational, not Standards Track, so I think that's fine
jonas’I’d suggest informational, it’s not a procedure of the XSF or the Council
Zashor is it, if it touches on management of the website?
dwdI'll got for "on-list" as far as a vote is concerned, but I'm heavily leaning toward +1.
jonas’Zash, it doesn’t seem to
dwdZash, I can see arguments for it being STandards Track, as it's trying to define an interoperable wire format for the community.
jonas’depends on which wires, I suppose
jonas’but true, the typical Last Call / CFE questions would apply to this one
jonas’I suggest we bring that question up to the list
Ge0rGI don't have a strong opinion either way
Ge0rGHowever, with Standards Track, I'll start pondering about namespace versioning the schema.org schema
jonas’(sent the ProtoXEP mail just now, forgot that yesterday, so we have a thread to go on)
jonas’4b) Proposed XMPP Extension: OMEMO Media Sharing
Abstract: An informal way of sharing media files despite limitations in the
Note: We had this one as Standards Track in the past, but it was resubmitted
jonas’the first fun question is whether Link Mauve got the IPR agreement from daniel to resubmit his work under a different Track
Ge0rGWhat happened to the "this one as Standards Track in the past" document?
jonas’rejected by council
danieldidnt council back then decided that moving it to a different track isn’t enough?
danielbecause i vaguely remember offering to do this but it was rejected
danielso if we now +1 we overrule previous council decisions
Ge0rGso technically it was submitted as Standards Track, but never landed there?
jonas’no, not 2018-05-30
jonas’still finding it
Ge0rGon-list, I'll wait for the XEP-0001 taskforce to decide what our legitimate options are.
danielcan we at least fix the example before publishing it