From f2d595964af5a40cbf75c3a70cfae28dd906c667 Mon Sep 17 00:00:00 2001 From: Sam Whited Date: Wed, 19 Jul 2017 11:59:44 -0500 Subject: [PATCH] Tweak XEP editor readme to mention Docker --- xep-README.xml | 37 ++++++++++++++++++++++++++++++++----- 1 file changed, 32 insertions(+), 5 deletions(-) diff --git a/xep-README.xml b/xep-README.xml index 0d1d1af4..10386971 100644 --- a/xep-README.xml +++ b/xep-README.xml @@ -115,8 +115,20 @@ -

The XMPP Extensions Editor (or, for short, XEP Editor) manages the XMPP extensions process as defined in &xep0001;. In addition, the XEP Editor functions as the XMPP Registrar as defined in &xep0053;. Read those documents first, since this README focuses on mechanics instead of philosophy or policy.

-

Since the inception of the &XSF; in 2001 until early 2014, the &EDITOR; was Peter Saint-Andre. In early 2014, the &XSF; formed a "work team" to dispatch the responsibilities of the XEP Editor and XMPP Registrar. This document describes most of the details about how those responsibilities are performed.

+

+ The XMPP Extensions Editor (or, for short, XEP Editor) manages the XMPP + extensions process as defined in &xep0001;. In addition, the XEP Editor + functions as the XMPP Registrar as defined in &xep0053;. Read those + documents first, since this README focuses on mechanics instead of + philosophy or policy. +

+

+ Since the inception of the &XSF; in 2001 until early 2014, the &EDITOR; was + Peter Saint-Andre. In early 2014, the &XSF; formed a "work team" to + dispatch the responsibilities of the XEP Editor and XMPP Registrar. This + document describes most of the details about how those responsibilities are + performed. +

@@ -160,8 +172,13 @@
  • Set the status to Experimental.
  • Check the file for egregious errors.
  • Add a reference for the new XEP in the xep.ent file and check those changes into source control.
    • -
  • Log into the webserver, change directories to /home/xsf/xmpp-hg/extensions, type 'hg pull' and 'hg update', and run the "gen.py" script to generate HTML and PDF files.
    • +
  • Log into the webserver, change directories to /home/xsf/xmpp-hg/extensions, type 'hg pull' and 'hg update'.
  • Run the "archive.sh" script, which copies this published version to http://xmpp.org/extensions/attic/.
    • +
  • + Run '/docker/xmpp.org_extensions/create.sh' as root, or, if you don't + have root, pester someone on the i-team. +
    • +
  • Wait.
  • Run the "announce.py" script (see note about List Administration).
  • Redirect the HTML file in the "inbox" to the new XEP URL (see existing examples on the webserver).
    • @@ -175,7 +192,17 @@
  • Verify that the version number, status, and other information are correct.
  • Compile the file locally and check the content for accuracy (including the correct date and version number).
  • Check the changes into source control.
    • -
  • Log into the webserver as the 'xsf' user, change directories to /home/xsf/xmpp-hg/extensions, run the "archive.sh" script to copy the previous XEP version to the "attic" (just in case the last editor team member forgot), type 'hg pull' and 'hg update', and run the "gen.py" script to generate HTML and PDF files.
    • +
  • + Log into the webserver as the 'xsf' user, change directories to + /home/xsf/xmpp-hg/extensions, run the "archive.sh" script to copy the + previous XEP version to the "attic" (just in case the last editor team + member forgot), type 'hg pull' and 'hg update'. +
    • +
  • + Run '/docker/xmpp.org_extensions/create.sh' as root, or, if you don't have + root, pester someone on the i-team. +
    • +
  • Wait.
  • Run the "announce.py" script on the webserver (see note about List Administration).
    • @@ -187,7 +214,7 @@ $ . /usr/local/virtualenv/gen/bin/activate $ # or "export PATH=/usr/local/virtualenv/gen/bin:$PATH $ ./archive.sh 0353 0.1 $ hg pull && hg update -$ ./gen.py xep-0353.xml +$ sudo /docker/xmpp.org_extensions/create.sh $ ./announce.py 0353 ]]>