116
edits
Difference between revisions of "User:Larma/Council Candidacy 2019"
Jump to navigation
Jump to search
User:Larma/Council Candidacy 2019 (view source)
Revision as of 15:24, 3 November 2019
, 15:24, 3 November 2019no edit summary
m |
|||
| Line 17: | Line 17: | ||
* It should solve a problem. If it's not obvious which problem it solves, the problem must be outlined in the XEP itself. Personal opinions can be a valid problem description, as long as they are justified. | * It should solve a problem. If it's not obvious which problem it solves, the problem must be outlined in the XEP itself. Personal opinions can be a valid problem description, as long as they are justified. | ||
For the elevation to Draft status I understand "''generally stable and appropriate for further field experience''" from [https://xmpp.org/extensions/xep-0001.html#approval-std XEP-0001] such, that there should be at least two implementations of the latest version (not necessarily used a lot in the wild, but existing and tested for interoperability). I'd also like to ensure that we move things to Draft faster as well as to actually move things to Final if they become wildly implemented. As an example, XEP-0363 should probably be in Final already, but it didn't even reach Draft yet. | For the elevation to Draft status I understand "''generally stable and appropriate for further field experience''" from [https://xmpp.org/extensions/xep-0001.html#approval-std XEP-0001] such, that there should be at least two implementations of the latest version (not necessarily used a lot in the wild, but existing and tested for interoperability). I'd also like to ensure that we move things to Draft faster as well as to actually move things to Final if they become wildly implemented. As an example, [https://xmpp.org/extensions/xep-0363.html XEP-0363] should probably be in Final already, but it didn't even reach Draft yet. | ||
Moving things faster to Draft and Final status also means we should rarely do namespace bumps within a XEP anymore. That's because Experimental will become Experimental again (i.e. not widely implemented) and as such breaking things without a namespace bump in an Experimental XEP is actually fine. Draft standards however should remain backwards-compatible, which usually means that a namespace bump is not possible. If a significantly new iteration of a Draft or Final XEP is needed (that would imply a namespace bump), it should just start as a new ProtoXEP (and soon Experimental XEP). | Moving things faster to Draft and Final status also means we should rarely do namespace bumps within a XEP anymore. That's because Experimental will become Experimental again (i.e. not widely implemented) and as such breaking things without a namespace bump in an Experimental XEP is actually fine. Draft standards however should remain backwards-compatible, which usually means that a namespace bump is not possible. If a significantly new iteration of a Draft or Final XEP is needed (that would imply a namespace bump), it should just start as a new ProtoXEP (and soon Experimental XEP). | ||