From ab8529095ab1c817b56e1530667b8b5c16f53b6c Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Tue, 19 Jun 2007 16:30:54 +0000 Subject: [PATCH] sourcecontrol link git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@979 4b5297f7-1745-476d-ba37-a9c6900126ab --- editor.shtml | 2 +- index.shtml | 2 +- submit.shtml | 2 +- xep-0001.xml | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/editor.shtml b/editor.shtml index bdd411fc..adc8adf1 100755 --- a/editor.shtml +++ b/editor.shtml @@ -10,7 +10,7 @@
  • ensures that each XEP is properly formatted
  • assigns a unique number to each XEP
  • assigns or modifies the status of each XEP
    • -
  • maintains each XEP under source control
    • +
  • maintains each XEP under source control
  • maintains the canonical list of XEPs
  • publishes each XEP to the xmpp.org website
  • publicly announces the existence and status of each XEP
    • diff --git a/index.shtml b/index.shtml index 06c589eb..934c5e7c 100755 --- a/index.shtml +++ b/index.shtml @@ -7,7 +7,7 @@

    ATOM  RSS

    -

    The XMPP Standards Foundation (XSF) develops extensions to XMPP through a standards process centered around XMPP Extension Protocols (XEPs). The process is managed by the XMPP Extensions Editor and involves intensive discussion on the Standards mailing list, formal review and voting by the XMPP Council, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal IPR Policy for wide implementation. Submissions are welcome (see also the "inbox"). Changes are tracked via a CVS repository (see instructions), old versions are available, and IETF-style XML reference files are provided.

    +

    The XMPP Standards Foundation (XSF) develops extensions to XMPP through a standards process centered around XMPP Extension Protocols (XEPs). The process is managed by the XMPP Extensions Editor and involves intensive discussion on the Standards mailing list, formal review and voting by the XMPP Council, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal IPR Policy for wide implementation. Submissions are welcome (see also the "inbox"). All XEPs and related files are under source control, old versions are available, and IETF-style XML reference files are provided.

    This page lists approved XMPP extensions as well as proposals that are under active consideration. A list of all XEPs (including retracted, rejected, deprecated, and obsolete XEPs) is also available. Good places for developers to start are the basic and intermediate protocol suites.

    diff --git a/submit.shtml b/submit.shtml index 62d1bc85..a5fc4308 100755 --- a/submit.shtml +++ b/submit.shtml @@ -11,5 +11,5 @@

  • Make sure you read, understand, and agree to the XSF's IPR Policy before you submit your proposal!

  • Email the XML file (or a URL for the file) to the XMPP Extensions Editor with a subject line of 'ProtoXEP: [your title here]'.

    • -

    Note: It is the author's responsibility to provide a properly-formatted source file (see the template and CVS repository). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.

    +

    Note: It is the author's responsibility to provide a properly-formatted source file (see the template file maintained under source control). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.

    diff --git a/xep-0001.xml b/xep-0001.xml index e79b8dbf..620ff037 100644 --- a/xep-0001.xml +++ b/xep-0001.xml @@ -225,7 +225,7 @@
  • assign it a number
  • specify an appropriate type
  • specify a status of Experimental
    • -
  • add it to source control XEPs are kept under source control in the 'xmpp' module and 'extensions' directory of the CVS repository maintained at the jabberstudio.org service. Instructions for accessing these files can be found at <http://www.jabberstudio.org/cvs.php>, and a web interface to these files is available at <http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/>.
    • +
  • add it to source control XEPs are kept under source control in the 'xmpp' module and 'extensions' directory of the XSF Subversion repository; instructions for accessing these files can be found at <http://www.xmpp.org/xsf/sourcecontrol.shtml>.
  • add tracking information to the XEPs database
  • publish version 0.1 of the XEP to the xmpp.org website The canonical URL for accessing XMPP Extensions is <http://www.xmpp.org/extensions/>.
  • publicly announce the existence of the XEP by sending a message to the Standards list