diff --git a/xep-README.xml b/xep-README.xml index ad3e623b..853ad320 100644 --- a/xep-README.xml +++ b/xep-README.xml @@ -22,6 +22,12 @@ N/A &stpeter; + + 0.3 + 2015-07-12 + ssw +

Update the accepting an XEP section.

+
0.2 2016-05-16 @@ -113,17 +119,17 @@

These functions are specified below.

-

Periodically, people send email to editor@xmpp.org with new proposals. Here is how to process such submissions.

+

Periodically, people send email to editor@xmpp.org or submit pull requests with new proposals. Here is how to process such submissions.

  1. Receive proposal from authors.
  2. -
  3. 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 http://xmpp.org/extensions/ipr-policy.shtml.
  4. +
  5. 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 https://xmpp.org/about/xsf/ipr-policy.
  6. Give it a descriptive filename that does not include the string 'xep' or a XEP number.
  7. Set the version to 0.0.1.
  8. Set the status to ProtoXEP.
  9. Locally convert XML to HTML and check the results for accuracy in accordance with normal XEP formatting (see &xep0143;).
  10. -
  11. 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.
  12. -
  13. 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 > /var/www/vhosts/xmpp.org/extensions/inbox/protoxepfile.html', and remove the file from the extensions/ directory.
  14. -
  15. Run the "inxep.py" script on the webserver (see note about List Administration).
  16. +
  17. Check the XML file into the main branch of the XEP repository in the inbox/ subdirectory and then push the changes.
  18. +
  19. Log into the webserver, change directories to /home/xsf/xmpp-hg/extensions, perform an hg pull && hg update, copy the protoxep file from the inbox/ subdirectory to the extensions/ directory, type 'xsltproc protoxepfile.xml > /var/www/vhosts/xmpp.org/extensions/inbox/protoxepfile.html', and remove the file from the extensions/ directory.
  20. +
  21. Run "inxep.py name approvingbody" script on the webserver (eg. "./inxep.py pars council"; see note about List Administration).
  22. 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).
  23. If rejected, retain the XML file in git and the HTML file in the "inbox".