From 1a6828203e473efabc7f17e787ce2e23a12afa58 Mon Sep 17 00:00:00 2001 From: Dave Cridland Date: Tue, 24 Dec 2024 11:14:57 +0000 Subject: [PATCH] XEP-0143 GitHub all the things --- xep-0143.xml | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/xep-0143.xml b/xep-0143.xml index 588676b3..3e84ede1 100644 --- a/xep-0143.xml +++ b/xep-0143.xml @@ -22,6 +22,12 @@ N/A &stpeter; + + 1.1.3 + 2024-12-24 + dwd +

Reflect preference for GitHub pull requests for initial submission, PRs to contain only one XEP change,

+ 1.1.2 2016-12-02 @@ -88,6 +94,7 @@

After completing this research, the prospective author might conclude that a new protocol extension is needed. If so, the author is strongly advised to do the following:

  1. Review &xep0001; and the &xep0134;.
    2. +
  2. Read, understand, and agree to the &XSFIPR;.
  3. Understand the Submission Process.
  4. Become familiar with the XEP XML Format.
  5. Then and only then write a proposal that includes all of the appropriate Sections of a XEP.
    6. @@ -100,7 +107,8 @@
    1. Write your proposal following the guidelines described in this document.
    2. Make sure that you read, understand, and agree to the &XSFIPR; before you submit your proposal.
      3. -
    3. Send your XML file (or a URL pointing to the file) to the &EDITOR; team via email to editor@xmpp.org (make sure that the email subject includes the string "XEP" somewhere in it!)..
      4. +
    4. Ideally: Submit your XEP via a GitHub Pull Request that adds the file (and changes no others) to the "inbox" directory. (See below for a typical working pattern.
      5. +
    5. If this cannot be done (perhaps because you have no GitHub account and do not wish to obtain one), send your XML file (or a URL pointing to the file) to the &SSIG; via email to standards@xmpp.org, and request someone to help you. (There are usually people who help the &EDITOR; in this way).
    @@ -110,10 +118,12 @@
    1. Create your own fork of the XSF's git repository (the address of the GitHub mirror can be found at &SOURCECONTROL;).
    2. Create a dedicated branch for these changes in your forked repository.
      3. -
    3. Make your desired changes to the document or documents, including an updated <revision/> element as described below.
      4. +
    4. Make your desired changes to the document, including an updated <revision/> element as described below.
    5. Commit and push the changes to your branch.
      6. -
    6. Create a pull request from your fork to the master branch at the GitHub mirror.
      7. +
    7. Create a pull request from your fork to the master branch at the GitHub mirror. The title of the Pull Request MUST start with the formal document identifier (eg, "XEP-0143"). Note that each pull request should change only one XEP.
      8. +
    8. Monitor CI output to ensure that errors are corrected.
    +

    As above, if you do not have a GitHub account, and decline to sign up for one, you will need to ask for help from someone who does.

    The XMPP Extensions Editor team will then process your pull request, seek Council approval if necessary, and publish an updated version of your XEP.

    NOTE: As explained in &xep0001;, updated versions of XEPs in the Experimental state are published without the need for approval by the XMPP Council. However, updated versions of XEPs in the Active, Draft, or Final state must be approved by the XMPP Council to ensure proper change control regarding approved protocols.

    @@ -286,7 +296,7 @@ echo -n 'bard@shakespeare.lit' | openssl enc -nopad -base64 -

    Thanks to Tobias Markmann and Kevin Smith for their input.

    +

    Thanks to Daniel Gultsch, Tobias Markmann and Kevin Smith for their input.