friendly poke for any available editor to issue XEP-0368 call for experience :)
Guushas left
Guushas left
jonasw
moparisthebest, I’m still not sure on how the process works, sorry.
Guushas left
jonasw
moparisthebest, but I’ll give it a shot now anyways
moparisthebest
jonasw, I don't think anyone is, how about just an email like "Subject: Call for Experience: XEP-0368" "The council is going to consider moving this to final and is looking for feedback" or something
moparisthebest
I'm bad with words :)
jonasw
I can’t simply say council is going to do anything unless council said so
Guushas left
moparisthebest
that's what xep-0001 says though
jonasw
XEP-0001 says that the editor (without specifying what triggers this) issues a CFE *before* the XEP is laid before council for advancement.
jonasw
there’s nothing in XEP-0001 (I thnik, point me to it if I’m wrong) which says that council MUST look at something which has been CFE’d
moparisthebest
right, that's what I'm looking to get to happen
jonasw
I’m still trying to figure out what stops me from issuing CFEs for all (old enough) Draft XEPs at once
moparisthebest
oh yea, but it'll be presented to them at least 14 days after anyway
jonasw
it seems fishy :)
Guushas left
jonasw
anyways, let’s give this a shot
moparisthebest
yea jonasw I'm just trying to push it towards final I only know what xep-1 says and it seems like next step is for editor to send email so :shrug: :)
jonasw
somebody will complain if we did anything wrong
moparisthebest
that's kind of what I figured, if it's wrong, xep-1 should be clarified
jonasw
you’re the author, right?
moparisthebest
yep
jonasw
okay
jonasw
there you go, email sent (will take a minute or two to propagate through the list)
moparisthebest
thanks much
jonasw
will also comment on it once the mail got through, I actually implemented it.
moparisthebest
oh yea in your client, library, or both?
jonasw
library
jonasw
(from which follows, client)
jonasw
(I didn’t bother with implementing an off switch)
moparisthebest
yea I was going to try to pull up all implementations I know about in a mail later
moparisthebest
dwd said he implemented it in a server, it's the only s2s implementation I know of, there are a few client ones iirc
moparisthebest
it's arguably much more useful for clients
jonasw
there you go
moparisthebest
thanks
Guushas left
Guus
368 appendix A - Short Name: NOT_YET_ASSIGNED ... If this is going from draft to final, it's likely never getting one?
Guus
(perhaps simply remove that line?)
Guus
also, section 4 starts with a undefined referal: "this provides". It being the start of a paragraph titled "Use Cases", makes it unclear if 'this' refers to the entire XEP, or rather the ALPN description in the previous paragraph. I'd reword it slightly.
SamWhited
I think the council assigns a short name when it goes to draft or final.
Guus
in unrelated news: I'm going to have a beautiful bike shed. Been working on its plans for years.
Guus
xep-0053 suggests short names can be assigned as early as when a xep is published as experimental: "When a XEP is first published in the Experimental state, the XMPP Registrar shall work with the author(s) to mint an appropriate namespace name, which shall be of the form "urn:xmpp:ShortName:0" or, where appropriate, "urn:xmpp:ShortName:SubName:0"
Guus
I don't care to much, by the way. I just thought the 'yet' part was misplaced in something that's about to be 'final'