Clarify proposing Deferred XEPs for advancement to Draft

This commit is contained in:
Ralph Meijer 2019-01-17 16:33:45 +01:00
parent f24dff484b
commit 367a4258b4
1 changed files with 11 additions and 4 deletions

View File

@ -21,6 +21,13 @@
<shortname>N/A</shortname>
&stpeter;
&dcridland;
&ralphm;
<revision>
<version>1.23.0</version>
<date>2019-01-17</date>
<initials>rm</initials>
<remark><p>Clarify proposing Deferred XEPs for advancement to Draft.</p></remark>
</revision>
<revision>
<version>1.22.0</version>
<date>2018-11-08</date>
@ -290,7 +297,7 @@
<p>If an Experimental XEP is inactive (i.e., no updated versions are published) for a period of twelve (12) months, the XMPP Extensions Editor shall automatically change the status of the XEP to Deferred unless it is in the queue of XEPs under active consideration for advancement by the Approving Body; upon submission of an updated version, the XMPP Extensions Editor shall change the status back to Experimental.</p>
</section1>
<section1 topic='Proposal Process' anchor='proposal'>
<p>Before an Experimental XEP may be proposed to the Approving Body for advancement to Draft (Standards Track XEPs) or Active (Historical, Informational, and Procedural XEPs), the Approving Body must agree that the XEP is ready to be considered for advancement. Once the Approving Body so agrees, it shall instruct the XMPP Extensions Editor to (1) change the status of the XEP from Experimental to Proposed and (2) issue a Last Call for open discussion on the Standards list. The Last Call shall expire not less than fourteen (14) days after the date of issue.</p>
<p>Before an Experimental (or Deferred) XEP may be proposed to the Approving Body for advancement to Draft (Standards Track XEPs) or Active (Historical, Informational, and Procedural XEPs), the Approving Body must agree that the XEP is ready to be considered for advancement. Once the Approving Body so agrees, it shall instruct the XMPP Extensions Editor to (1) change the status of the XEP from Experimental (or Deferred) to Proposed and (2) issue a Last Call for open discussion on the Standards list. The Last Call shall expire not less than fourteen (14) days after the date of issue.</p>
<p>Once the consensus of the Standards SIG has been incorporated into the XEP and all issues of substance raised during the Last Call have been addressed by the XEP author, the XMPP Extensions Editor shall formally propose a specific revision of the XEP to the Approving Body for its vote. If necessary, the XMPP Extensions Editor may, at his discretion and in consultation with the Approving Body, extend the Last Call or issue a new Last Call if the XEP requires further discussion.</p>
</section1>
<section1 topic='Approval Process' anchor='approval'>
@ -311,9 +318,9 @@
|
|
+--> Deferred +--> Rejected
| |
| |
Experimental ----> Proposed ----> Draft ----> Final
| | |
| | |
Experimental --+-> Proposed ----> Draft ----> Final
^ | | |
+----------------+ | |
+-----------+---> Deprecated