pep."Accepted"? (I guess if this discussion happens again there will be plenty enough bikeshed). I also agree anyway
Douglas Terabytehas joined
jonas’Accepted is Experimental though
ZashTry harder to push Draft to Final?
flowZash, I don't see the point in the 'final' state FWIW
jonas’final means immutable, there might be some value in that or not
ZashBut things never stop changing unless they are dead. So it's kinda weird.
ZashWhat do you do with an immutable XEP when the requirements inevitably change a decade later?
jonas’RFCs don’t change
ZashRFCs get replaced
jonas’I think the same idea was for Final initially, too
jonas’(and maybe still is)
ZashIETF has Internet-Drafts which are almost like our Experimental. Then it maybe gets published as an Experimental or Propsoed RFC, which is sorta like our Draft. Then you go back to I-D and roll in tweaks based on experiences, which gets published as another type of RFC
ZashTho you can roll in new experiences in Draft XEPs, but with more friction due to Council
GuusI agree that it might be good to adopt a terminology that leans less heavily towards the "this isn't done yet" side. It's off-putting, and can be taken as a sign that there's no maturity to the stack.
ZashRFC 3920 is "Proposed"
ZashWait RFC 6120 is also "PROPOSED STANDARD"
ZashHTTP/1.1 is a draft standard
ZashI think the thing is that nobody looks in that corner
theTeddthe issue is that what we mean by 'Draft' isn't how the word is usually used, and if you have to go out of your way to explain the way you're using a word, maybe you should just use a different word
theTeddwe want to imply "ready for use" as opposed to "a bit rough, but nearly there"
theTeddthis has come up before, of course
jonas’so that it ends up in content filters :)
ZashIsn't that Final?
theTeddStable doesn't rule out changes, Final i supposed to
ZashOr, just do away with the words and use numbers.
theTeddI'm not sure that would help - people will take the highest number as final and anything less as unfinished