Update the section on accepting an XEP

This commit is contained in:
Sam Whited 2016-07-12 10:04:30 -05:00
parent b87c35353c
commit bc17ea846f
1 changed files with 11 additions and 5 deletions

View File

@ -22,6 +22,12 @@
<supersededby/>
<shortname>N/A</shortname>
&stpeter;
<revision>
<version>0.3</version>
<date>2015-07-12</date>
<initials>ssw</initials>
<remark><p>Update the accepting an XEP section.</p></remark>
</revision>
<revision>
<version>0.2</version>
<date>2016-05-16</date>
@ -113,17 +119,17 @@
<p>These functions are specified below.</p>
<section2 topic='Accepting a XEP' anchor='accepting'>
<p>Periodically, people send email to editor@xmpp.org with new proposals. Here is how to process such submissions.</p>
<p>Periodically, people send email to editor@xmpp.org or submit pull requests with new proposals. Here is how to process such submissions.</p>
<ol>
<li>Receive proposal from authors.</li>
<li>Send a reply to the author(s) in order to verify that, if the proposal is accepted, they will cede rights to the protocol in accordance with the XSF's IPR policy <link url='http://xmpp.org/extensions/ipr-policy.shtml'>http://xmpp.org/extensions/ipr-policy.shtml</link>.</li>
<li>Send a reply to the author(s) in order to verify that, if the proposal is accepted, they will cede rights to the protocol in accordance with the XSF's IPR policy <link url='https://xmpp.org/about/xsf/ipr-policy'>https://xmpp.org/about/xsf/ipr-policy</link>.</li>
<li>Give it a descriptive filename that does <em>not</em> include the string 'xep' or a XEP number.</li>
<li>Set the version to 0.0.1.</li>
<li>Set the status to ProtoXEP.</li>
<li>Locally convert XML to HTML and check the results for accuracy in accordance with normal XEP formatting (see &xep0143;).</li>
<li>Check the XML file into the main branch of the XSF's git repository in the inbox/ subdirectory under extensions/ and then push the changes.</li>
<li>Log into the webserver, change directories to /home/xsf/git, perform a git pull, copy the protoxep file from the inbox/ subdirectory to the extensions/ directory, type 'xsltproc protoxepfile.xml &gt; /var/www/vhosts/xmpp.org/extensions/inbox/protoxepfile.html', and remove the file from the extensions/ directory.</li>
<li>Run the "inxep.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
<li>Check the XML file into the main branch of the XEP repository in the inbox/ subdirectory and then push the changes.</li>
<li>Log into the webserver, change directories to /home/xsf/xmpp-hg/extensions, perform an hg pull &amp;&amp; hg update, copy the protoxep file from the inbox/ subdirectory to the extensions/ directory, type 'xsltproc protoxepfile.xml &gt; /var/www/vhosts/xmpp.org/extensions/inbox/protoxepfile.html', and remove the file from the extensions/ directory.</li>
<li>Run "inxep.py name approvingbody" script on the webserver (eg. "./inxep.py pars council"; see note about <link url='#lists'>List Administration</link>).</li>
<li>Wait until the Council decides whether to accept the proposal as a XEP (this might involve poking the Council Chair, attending Council meetings, and monitoring the Council discussion list).</li>
<li>If rejected, retain the XML file in git and the HTML file in the "inbox".</li>
<li>