No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-README.xml 25KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>XEP Editor README</title>
  10. <abstract>This document describes work processes followed by the XMPP Extensions Editor.</abstract>
  11. &LEGALNOTICE;
  12. <number>README</number>
  13. <status>Experimental</status>
  14. <type>Procedural</type>
  15. <sig>N/A</sig>
  16. <approver>N/A</approver>
  17. <dependencies>
  18. <spec>XEP-0001</spec>
  19. <spec>XEP-0053</spec>
  20. </dependencies>
  21. <supersedes/>
  22. <supersededby/>
  23. <shortname>N/A</shortname>
  24. &stpeter;
  25. <revision>
  26. <version>0.15</version>
  27. <date>2017-03-09</date>
  28. <initials>ssw</initials>
  29. <remark><p>Remove invalid step from advancing an XEP section</p></remark>
  30. </revision>
  31. <revision>
  32. <version>0.14</version>
  33. <date>2017-01-28</date>
  34. <initials>ssw</initials>
  35. <remark><p>Update superseding an XEP since references are now auto generated.</p></remark>
  36. </revision>
  37. <revision>
  38. <version>0.13</version>
  39. <date>2016-10-29</date>
  40. <initials>ssw</initials>
  41. <remark><p>Update the Last Call section.</p></remark>
  42. </revision>
  43. <revision>
  44. <version>0.12</version>
  45. <date>2016-07-12</date>
  46. <initials>ssw</initials>
  47. <remark><p>Update the accepting an XEP section.</p></remark>
  48. </revision>
  49. <revision>
  50. <version>0.11</version>
  51. <date>2016-05-16</date>
  52. <initials>ssw</initials>
  53. <remark><p>Make the updating an XEP section match current process.</p></remark>
  54. </revision>
  55. <revision>
  56. <version>0.10</version>
  57. <date>2016-01-21</date>
  58. <initials>asw</initials>
  59. <remark><p>Added reminders to remove &lt;interim&gt; elements.</p></remark>
  60. </revision>
  61. <revision>
  62. <version>0.9</version>
  63. <date>2014-02-25</date>
  64. <initials>psa</initials>
  65. <remark><p>Modernized to reflect updated scripts and processes, as well as the existence of the XSF's Editor Team.</p></remark>
  66. </revision>
  67. <revision>
  68. <version>0.8</version>
  69. <date>2009-11-19</date>
  70. <initials>psa</initials>
  71. <remark><p>Updated to reflect newer processes and provide more complete coverage of XEP Editor and XMPP Registrar responsibilities.</p></remark>
  72. </revision>
  73. <revision>
  74. <version>0.7</version>
  75. <date>2008-07-16</date>
  76. <initials>psa</initials>
  77. <remark><p>Updated to reflect use of SVN.</p></remark>
  78. </revision>
  79. <revision>
  80. <version>0.6</version>
  81. <date>2007-09-28</date>
  82. <initials>psa</initials>
  83. <remark><p>Updated to reflect new scripts and use of mailserver.</p></remark>
  84. </revision>
  85. <revision>
  86. <version>0.5</version>
  87. <date>2005-05-26</date>
  88. <initials>psa</initials>
  89. <remark><p>Adjusted to reflect ProtoXEP status.</p></remark>
  90. </revision>
  91. <revision>
  92. <version>0.4</version>
  93. <date>2005-03-16</date>
  94. <initials>psa</initials>
  95. <remark><p>Converted to XEP format; adjusted to reflect server move.</p></remark>
  96. </revision>
  97. <revision>
  98. <version>0.3</version>
  99. <date>2004-10-22</date>
  100. <initials>psa</initials>
  101. <remark><p>Clarified schema handling.</p></remark>
  102. </revision>
  103. <revision>
  104. <version>0.2</version>
  105. <date>2004-10-11</date>
  106. <initials>psa</initials>
  107. <remark><p>Defined XMPP Registrar processes.</p></remark>
  108. </revision>
  109. <revision>
  110. <version>0.1</version>
  111. <date>2004-10-01</date>
  112. <initials>psa</initials>
  113. <remark><p>Initial version.</p></remark>
  114. </revision>
  115. </header>
  116. <section1 topic='Overview' anchor='overview'>
  117. <p>
  118. The XMPP Extensions Editor (or, for short, XEP Editor) manages the XMPP
  119. extensions process as defined in &xep0001;. In addition, the XEP Editor
  120. functions as the XMPP Registrar as defined in &xep0053;. Read those
  121. documents first, since this README focuses on mechanics instead of
  122. philosophy or policy.
  123. </p>
  124. <p>
  125. Since the inception of the &XSF; in 2001 until early 2014, the &EDITOR; was
  126. Peter Saint-Andre. In early 2014, the &XSF; formed a "work team" to
  127. dispatch the responsibilities of the XEP Editor and XMPP Registrar. This
  128. document describes most of the details about how those responsibilities are
  129. performed.
  130. </p>
  131. </section1>
  132. <section1 topic='XEP Editor Responsibilities' anchor='ed'>
  133. <p>There are several XEP-related functions performed by the XEP Editor:</p>
  134. <ol>
  135. <li>Accepting a XEP</li>
  136. <li>Updating a XEP</li>
  137. <li>Deferring a XEP</li>
  138. <li>Retracting a XEP</li>
  139. <li>Issuing a Last Call</li>
  140. <li>Counting Council Votes</li>
  141. <li>Advancing a XEP</li>
  142. <li>Deprecating a XEP</li>
  143. <li>Obsoleting a XEP</li>
  144. <li>XEP Maintenance</li>
  145. <li>List Administration</li>
  146. </ol>
  147. <p>These functions are specified below.</p>
  148. <section2 topic='Accepting a XEP' anchor='accepting'>
  149. <p>Periodically, people send email to editor@xmpp.org or submit pull requests with new proposals. Here is how to process such submissions.</p>
  150. <ol>
  151. <li>Receive proposal from authors.</li>
  152. <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>
  153. <li>Give it a descriptive filename that does <em>not</em> include the string 'xep' or a XEP number.</li>
  154. <li>Set the version to 0.0.1.</li>
  155. <li>Set the status to ProtoXEP.</li>
  156. <li>Locally convert XML to HTML and check the results for accuracy in accordance with normal XEP formatting (see &xep0143;).</li>
  157. <li>Check the XML file into the main branch of the XEP repository in the inbox/ subdirectory and then push the changes.</li>
  158. <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>
  159. <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>
  160. <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>
  161. <li>If rejected, retain the XML file in git and the HTML file in the "inbox".</li>
  162. <li>
  163. <p>If accepted, do the following:</p>
  164. <ol>
  165. <li>Assign the XEP the next available number in the XEP series.</li>
  166. <li>Modify the &lt;number/&gt; element in the XML file.</li>
  167. <li>Set the version to 0.1 and the initials to "XEP Editor (psa)" where "psa" would be changed to your personal initials.</li>
  168. <li>Remove the &lt;interim/&gt; element from the XML file if it's included</li>
  169. <li>Set the status to Experimental.</li>
  170. <li>Check the file for egregious errors.</li>
  171. <li>Add a reference for the new XEP in the xep.ent file and check those changes into source control.</li>
  172. <li>Log into the webserver, change directories to /home/xsf/xmpp-hg/extensions, type 'hg pull' and 'hg update'.</li>
  173. <li>Run the "archive.sh" script, which copies this published version to <link url='http://xmpp.org/extensions/attic/'>http://xmpp.org/extensions/attic/</link>.</li>
  174. <li>
  175. Run '/docker/xmpp.org_extensions/create.sh' as root, or, if you don't
  176. have root, pester someone on the i-team.
  177. </li>
  178. <li>Wait.</li>
  179. <li>Run the "announce.py" script (see note about <link url='#lists'>List Administration</link>).</li>
  180. <li>Redirect the HTML file in the "inbox" to the new XEP URL (see existing examples on the webserver).</li>
  181. </ol>
  182. </li>
  183. </ol>
  184. </section2>
  185. <section2 topic='Updating a XEP' anchor='updating'>
  186. <p>Once a XEP has been published, it will be periodically updated in source control, and sometimes those changes are significant enough to warrant a new version (e.g., version 0.2 after 0.1). Often a request to release a new version will come from the document author, sometimes from the Council (e.g., after the XEP has reached version 1.0 or version 2.0 or when the status is changing from, say, Deprecated to Obsolete). Here is how to update a XEP.</p>
  187. <ol>
  188. <li>Verify that the version number, status, and other information are correct.</li>
  189. <li>Compile the file locally and check the content for accuracy (including the correct date and version number).</li>
  190. <li>Check the changes into source control.</li>
  191. <li>
  192. Log into the webserver as the 'xsf' user, change directories to
  193. /home/xsf/xmpp-hg/extensions, run the "archive.sh" script to copy the
  194. previous XEP version to the "attic" (just in case the last editor team
  195. member forgot), type 'hg pull' and 'hg update'.
  196. </li>
  197. <li>
  198. Run '/docker/xmpp.org_extensions/create.sh' as root, or, if you don't have
  199. root, pester someone on the i-team.
  200. </li>
  201. <li>Wait.</li>
  202. <li>Run the "announce.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
  203. </ol>
  204. <p>For example, to update XEP-0353 from version 0.1 to 0.2, you might do something like the following:</p>
  205. <code><![CDATA[
  206. $ sudo -u xsf -i
  207. $ cd ~xsf/xmpp-hg/extensions
  208. $ . /usr/local/virtualenv/gen/bin/activate
  209. $ # or "export PATH=/usr/local/virtualenv/gen/bin:$PATH
  210. $ ./archive.sh 0353 0.1
  211. $ hg pull && hg update
  212. $ sudo /docker/xmpp.org_extensions/create.sh
  213. $ ./announce.py 0353
  214. ]]></code>
  215. </section2>
  216. <section2 topic='Deferring a XEP' anchor='deferring'>
  217. <p>The status of a XEP shall be automatically changed to Deferred if a new version has not been submitted in 12 months, except if the XEP is actively in the Council queue for consideration of issuance of a Last Call. Here is the process.</p>
  218. <ol>
  219. <li>Change the &lt;status/&gt; element to "Deferred" in the XML file.</li>
  220. <li>Check your changes into source control (note: do not modify the version number!).</li>
  221. <li>Run the "gen.py" script on the webserver.</li>
  222. <li>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.</li>
  223. <li>Run the "archive.sh" script, which copies this published version to <link url='http://xmpp.org/extensions/attic/'>http://xmpp.org/extensions/attic/</link>.</li>
  224. <li>Run the "deferred.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
  225. </ol>
  226. </section2>
  227. <section2 topic='Retracting a XEP' anchor='retracting'>
  228. <p>Sometimes an author retracts a XEP because it is no longer deemed worthy of consideration. Here is the process.</p>
  229. <ol>
  230. <li>Change the &lt;status/&gt; element to "Retracted" in the XML file.</li>
  231. <li>Modify the &lt;abstract/&gt; element with appropriate content (see existing Retracted XEPs).</li>
  232. <li>Add a new revision block with an incremented version number, explaining that the XEP has been Retracted and why (see existing Retracted XEPs).</li>
  233. <li>Check your changes into source control.</li>
  234. <li>Log into the webserver, 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.</li>
  235. <li>Run the "announce.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
  236. </ol>
  237. </section2>
  238. <section2 topic='Issuing a Last Call' anchor='lastcall'>
  239. <p>The XMPP Council determines whether and when to issue a Last Call on an Experimental XEP. Here is the process.</p>
  240. <ol>
  241. <li>Receive notice from the Council Chair that a Last Call shall be issued.</li>
  242. <li>Determine the ending date, which must be at least 14 days in the future (sometimes 3 weeks if a great deal of discussion is expected).</li>
  243. <li>Change the &lt;status/&gt; element to "Proposed" in the XML file.</li>
  244. <li>Check your changes into source control.</li>
  245. <li>Log into the webserver, 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.</li>
  246. <li>Run the "lastcall.py" script on the webserver, eg. "./lastcall.py 0300 2016-11-12".</li>
  247. <li>Review the XMPP Registrar Considerations section to ensure accuracy.</li>
  248. </ol>
  249. </section2>
  250. <section2 topic='Counting Council Votes' anchor='councilvotes'>
  251. <p>The XEP Editor is responsible for counting the votes of Council members. The process is as follows.</p>
  252. <ol>
  253. <li>Monitor the Council list and Council meeting minutes for votes.</li>
  254. <li>Log into the website and modify the vote tally page linked to from &lt;<link url='http://xmpp.org/about-xmpp/xsf/xmpp-council/'>http://xmpp.org/about-xmpp/xsf/xmpp-council/</link>&gt;.</li>
  255. <li>When all Council members have voted, update the XEP accordingly (see below on Advancing a XEP).</li>
  256. </ol>
  257. </section2>
  258. <section2 topic='Advancing a XEP' anchor='advancing'>
  259. <p>When the Council approves a XEP, it advances to either Draft (Standards Track XEPs) or Active (other XEP types). Here is the process.</p>
  260. <ol>
  261. <li>Change the &lt;status/&gt; element to "Active" or "Draft" as appropriate.</li>
  262. <li>Add a new revision block; set the version number to "1.0" and the initials to "XEP Editor (psa)" where "psa" would be changed to your personal initials (see existing XEPs for appropriate remarks).</li>
  263. <li>Remove the &lt;interim/&gt; element from the XML file if it's included</li>
  264. <li>If there are any XML schemas associated with the XEP, do the following:
  265. <ol>
  266. <li>Add an annotation to each schema (see existing examples).</li>
  267. <li>In the 'schemas' directory, create one .xsd file for each schema.</li>
  268. <li>For each schema, add a &lt;schemaloc/&gt; element to the XEP file.</li>
  269. </ol>
  270. </li>
  271. <li>Add the protocol namespace (if any) to the protocol namespaces registry and complete any other XMPP Registrar actions called for in the XEP (see below).</li>
  272. <li>Check your changes into source control.</li>
  273. <li>Log into the webserver, 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.</li>
  274. <li>Run the "announce.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
  275. </ol>
  276. </section2>
  277. <section2 topic='Deprecating a XEP' anchor='deprecating'>
  278. <p>The Council can decide to change the status of a XEP to Deprecated (e.g., when a new technology has been developed to supersede the old technology). Here is the process:</p>
  279. <ol>
  280. <li>Add a new revision block; increment the version number and set the initials to "XEP Editor (psa)" where "psa" would be changed to your personal initials.</li>
  281. <li>Change the &lt;status/&gt; element to "Deprecated" in the XML file.</li>
  282. <li>If instructed to do so by the Council, add an &lt;expires/&gt; element to the header.</li>
  283. <li>Add a &lt;spec/&gt; child to the &lt;supersededby/&gt; element, pointing to the specification that supersedes this one.</li>
  284. <li>Check your changes into source control.</li>
  285. <li>Log into the webserver, 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.</li>
  286. <li>Run the "announce.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
  287. </ol>
  288. </section2>
  289. <section2 topic='Obsoleting a XEP' anchor='obsoleting'>
  290. <p>The Council can decide to change the status of a XEP from Deprecated to Obsolete. Here is the process:</p>
  291. <ol>
  292. <li>Add a new revision block; increment the version number and set the initials to "XEP Editor (psa)" where "psa" would be changed to your personal initials.</li>
  293. <li>Change the &lt;status/&gt; element to "Obsolete" in the XML file.</li>
  294. <li>If the file includes an &lt;expires/&gt; element in the header, remove it.</li>
  295. <li>If appropriate, add a &lt;spec/&gt; child to the &lt;supersededby/&gt; element, pointing to the specification that supersedes this one.</li>
  296. <li>Check your changes into source control.</li>
  297. <li>Log into the webserver, 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.</li>
  298. <li>Run the "announce.py" script on the webserver (see note about <link url='#lists'>List Administration</link>).</li>
  299. </ol>
  300. </section2>
  301. <section2 topic='XEP Maintenance' anchor='maintenance'>
  302. <p>At any time (even after a XEP has advanced to Draft or Final), it is appropriate for the XEP Editor to correct small errors in XEPs (typographical errors, XML errors in examples, etc.).</p>
  303. <p>However, care must be taken in editing Draft and Final XEPs, because any material changes to such specifications need to be approved by the XMPP Council. See <cite>XEP-0001</cite> for details.</p>
  304. <p>The XEP Editor can choose to perform more advanced maintenance of XEPs, such as validation of schemas, checking of examples, and copy editing in accordance with the styleguide in <cite>XEP-0143</cite>. Such work is best done while a XEP is still Experimental.</p>
  305. </section2>
  306. <section2 topic='List Administration' anchor='lists'>
  307. <p>XEPs are discussed on the standards@xmpp.org email list, about which information is available at &lt;<link url='http://mail.jabber.org/mailman/listinfo/standards'>http://mail.jabber.org/mailman/listinfo/standards</link>&gt;. Traditionally the XEP Editor acted as an administrator for this list. In particular, email from editor@xmpp.org is held for approval on this list to prevent spammers from sending fake emails from the Editor. Before running the "announce.py" script, empty the queue of messages held for moderation; after running the script, approve the message generated by that script so that it is sent to the list.</p>
  308. <p>With the transition to the XSF Editor Team, the editor@xmpp.org address is also an email list, used by the team. Incoming messages need to be screened for legitimacy and approved as appropriate.</p>
  309. </section2>
  310. </section1>
  311. <section1 topic='XMPP Registrar Responsibilities' anchor='reg'>
  312. <section2 topic='Advancing a XEP' anchor='reg-advance'>
  313. <p>Registry files are contained in the 'registry' directory. In general, there are several files that might need to be updated when a XEP advances to Active or Draft. In particular, most XEPs specify one or more protocol namespaces, which need to be added to the namespaces.xml file in the 'registry' directory. Refer to the list of registries at http://xmpp.org/registrar/ in order to determine which other registries might need to be updated. The reg.ent file will probably need to be updated as well. Once the Registrar actions have been completed, update the text of the XEP's XMPP Registrar Considerations section accordingly (e.g., to change "shall include" to "includes").</p>
  314. </section2>
  315. <section2 topic='Creating a New Registry' anchor='reg-newreg'>
  316. <p>A XEP might call for one or more new registries to be created. If so, carefully review the XMPP Registrar Considerations section of the XEP before it advances to Draft or Active in order to provide appropriate feedback to the XEP author. (Alternatively, make the changes directly in the XEP file in consultation with the author.)</p>
  317. <p>When creating a new registry, it is best to copy the DTD, XML, and XSL files for an existing registry, then modify them in accordance with the definition of the new registry in the relevant XEP. The gen.sh script will need to be updated to reflect the existence of the new registry, as will the index file for the http://xmpp.org/registrar/ web page.</p>
  318. <p class='note'>Note: Registry entries are often a source of confusion and error. It is recommended for several members of the XSF Editor Team to review registry changes before pushing them to the website.</p>
  319. <p>Check all your changes into source control, update the registrar/ directory from source on the webserver, run the gen.sh script to update the XMPP Registrar web pages, and run the "announce.py" script to send an announcement to the Standards list (see note about <link url='#lists'>List Administration</link>).</p>
  320. </section2>
  321. <section2 topic='Updating an Existing Registry' anchor='reg-update'>
  322. <p>New versions of XEPs might provide modified registry data. The XEP Editor needs to be aware of changes to Draft and Final XEPs in order to make appropriate updates to existing registries. The registry itself shall not be changed until the new XEP version is approved by the XMPP Council.</p>
  323. <p>The XMPP Registrar also periodically receives requests for additions to existing registrations outside of XEPs, either directly to registrar@xmpp.org or indirectly via the standards@xmpp.org list. If the Registrar receives such a request directly, it shall send an email about the proposed registration to the standards@xmpp.org for public comment. If no objections are raised within a reasonable period of time, the Registrar shall update the relevant registry accordingly.</p>
  324. </section2>
  325. </section1>
  326. <section1 topic='Tools' anchor='tools'>
  327. <section2 topic='XML Processing' anchor='tools-xml'>
  328. <p>In order to convert XML files into HTML and other formats, the XEP Editor currently uses the xsltproc tool, which is part of libxml2 (created by Daniel Veillard). This tool is extremely handy and it is recommended that use of xsltproc be continued, especially since the shell scripts (described below) make calls to xsltproc.</p>
  329. </section2>
  330. <section2 topic='XSL Transformations' anchor='tools-xsl'>
  331. <p>Most of the "magic" behind creating the HTML-formatted XEPs, as well as the IETF-style reference files, is perfomed by XSLT stylesheets. The main file here is xep.xsl, although ref.xsl is used to create the reference files. A future version of this README might explain these files in more depth.</p>
  332. </section2>
  333. <section2 topic='Entity References' anchor='tools-refs'>
  334. <p>The xep.ent file contains handy references that can be incorporated into any XEP XML document, thus providing a centralized location for various document references. The XEP Editor keeps this file up to date (e.g., by adding all new XEPs to it), and should be the only person who makes changes to the file.</p>
  335. </section2>
  336. <section2 topic='Python Scripts' anchor='tools-python'>
  337. <p>Several Python scripts are under source control. These are:</p>
  338. <ol>
  339. <li>
  340. <p>announce.py</p>
  341. <p>This script announces a new version of a XEP by sending a message to standards@xmpp.org (see note about <link url='#lists'>List Administration</link>).</p>
  342. </li>
  343. <li>
  344. <p>deferred.py</p>
  345. <p>This script updates the database and sends a message to standards@xmpp.org when the status of a XEP is changed to Deferred. Before running this script, make sure that you modify the &lt;status/&gt; element in the XEP itself and run the gen.py shell script.</p>
  346. </li>
  347. <li>
  348. <p>gen.py</p>
  349. <p>This script converts one XEP XML file into HTML and PDF, and updates the XEP "database". Run this script before announcing a new version. This script can also be used for minor edits to the current version.</p>
  350. </li>
  351. <li>
  352. <p>lastcall.py</p>
  353. <p>This script announces a Last Call for a XEP by updating the database and sending a message to standards@xmpp.org.</p>
  354. </li>
  355. <li>
  356. <p>protoxep.py</p>
  357. <p>This script announces availability of a new "proto-XEP" (i.e., a document not yet accepted as a XEP by the XMPP Council) by sending a message to standards@xmpp.org. Before running this script, place the new proto-XEP so that it is available at http://xmpp.org/extensions/inbox/ (normally this is done by running 'xsltproc inbox/docname.xml > /var/www/vhosts/xmpp.org/extensions/inbox/docname.html' from the editor's working SVN directory on the webserver).</p>
  358. </li>
  359. </ol>
  360. </section2>
  361. <section2 topic='Shell Scripts' anchor='tools-shell'>
  362. <p>Several shell scripts are under source control. These are:</p>
  363. <ol>
  364. <li>
  365. <p>all.sh</p>
  366. <p>This script converts all XEP XML files into HTML and PDF. Use this if the xep.xsl file changes in ways that affect all XEPs. But make sure that SVN is synced up first -- you don't want to be publishing interim versions of XEPs!</p>
  367. </li>
  368. <li>
  369. <p>archive.sh</p>
  370. <p>This script archives the version of a XEP currently on the website. Run this script before publishing a new version!</p>
  371. </li>
  372. </ol>
  373. </section2>
  374. </section1>
  375. </xep>