sourcecontrol link

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@979 4b5297f7-1745-476d-ba37-a9c6900126ab

editor.shtml

@@ -10,7 +10,7 @@
 <li>ensures that each XEP is properly formatted</li>
 <li>assigns a unique number to each XEP</li>
 <li>assigns or modifies the status of each XEP</li>
-<li>maintains each XEP under <a href='http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/jeps/'>source control</a></li>
+<li>maintains each XEP under <a href='/xsf/sourcecontrol.shtml'>source control</a></li>
 <li>maintains the canonical <a href='/extensions/'>list of XEPs</a></li>
 <li>publishes each XEP to the xmpp.org website</li>
 <li>publicly announces the existence and status of each XEP</li>

index.shtml

@@ -7,7 +7,7 @@
 
 <p><a class="standardsButton" href="atom.xml">ATOM</a>&nbsp;&nbsp;<a class="standardsButton" href="rss.xml">RSS</a></p>
 
-<p>The <a href='/xsf/'>XMPP Standards Foundation</a> (XSF) develops extensions to <a href="/">XMPP</a> through a standards process centered around XMPP Extension Protocols (XEPs). The <a href="xep-0001.html">process</a> is managed by the <a href="editor.shtml">XMPP Extensions Editor</a> and involves intensive discussion on the <a href="http://mail.jabber.org/mailman/listinfo/standards/">Standards mailing list</a>, formal review and <a href="/council/votes.shtml">voting</a> by the <a href="/council/">XMPP Council</a>, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal <a href="ipr-policy.shtml">IPR Policy</a> for wide implementation. Submissions are <a href='submit.shtml'>welcome</a> (see also the <a href="/extensions/inbox/">&quot;inbox&quot;</a>). Changes are tracked via a <a href="http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/">CVS repository</a> (see <a href='http://www.jabberstudio.org/cvs.php'>instructions</a>), <a href="/extensions/attic/">old versions</a> are available, and IETF-style <a href="/extensions/refs/">XML reference files</a> are provided.</p>
+<p>The <a href='/xsf/'>XMPP Standards Foundation</a> (XSF) develops extensions to <a href="/">XMPP</a> through a standards process centered around XMPP Extension Protocols (XEPs). The <a href="xep-0001.html">process</a> is managed by the <a href="editor.shtml">XMPP Extensions Editor</a> and involves intensive discussion on the <a href="http://mail.jabber.org/mailman/listinfo/standards/">Standards mailing list</a>, formal review and <a href="/council/votes.shtml">voting</a> by the <a href="/council/">XMPP Council</a>, and modification based on implementation experience and interoperability testing. All documents in the XEP series are available under a liberal <a href="ipr-policy.shtml">IPR Policy</a> for wide implementation. Submissions are <a href='submit.shtml'>welcome</a> (see also the <a href="/extensions/inbox/">&quot;inbox&quot;</a>). All XEPs and related files are under <a href="/xsf/sourcecontrol.shtml">source control</a>, <a href="/extensions/attic/">old versions</a> are available, and IETF-style <a href="/extensions/refs/">XML reference files</a> are provided.</p>
 
 <p>This page lists approved XMPP extensions as well as proposals that are under active consideration. A <a href="all.shtml">list of all XEPs</a> (including retracted, rejected, deprecated, and obsolete XEPs) is also available. Good places for developers to start are the <a href='xep-0073.html'>basic</a> and <a href='xep-0117.html'>intermediate</a> protocol suites.</p>
 

submit.shtml

@@ -11,5 +11,5 @@
 <li><p>Make sure you read, understand, and agree to the XSF's <a href='/extensions/ipr-policy.shtml'>IPR Policy</a> before you submit your proposal!</p></li>
 <li><p>Email the XML file (or a URL for the file) to the <a href='editor.shtml'>XMPP Extensions Editor</a> with a subject line of 'ProtoXEP: [your title here]'.</p></li>
 </ol>
-<p><strong>Note:</strong> It is the author's responsibility to provide a properly-formatted source file (see the <a href='template.xml'>template</a> and <a href='http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/'>CVS repository</a>). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.</p>
+<p><strong>Note:</strong> It is the author's responsibility to provide a properly-formatted source file (see the <a href='template.xml'>template</a> file maintained under <a href='/xsf/sourcecontrol.shtml'>source control</a>). Proposals submitted in HTML, TXT, MS Word, Open Document Format, etc. will be returned to the proposal author for proper formatting.</p>
 <!--#include virtual='/includes/foot.txt' -->

xep-0001.xml

@@ -225,7 +225,7 @@
     <li>assign it a number</li>
     <li>specify an appropriate type</li>
     <li>specify a status of Experimental</li>
-    <li>add it to source control <note>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 &lt;<link url='http://www.jabberstudio.org/cvs.php'>http://www.jabberstudio.org/cvs.php</link>&gt;, and a web interface to these files is available at &lt;<link url='http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/'>http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/xmpp/extensions/</link>&gt;.</note></li>
+    <li>add it to source control <note>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 &lt;<link url='http://www.xmpp.org/xsf/sourcecontrol.shtml'>http://www.xmpp.org/xsf/sourcecontrol.shtml</link>&gt;.</note></li>
     <li>add tracking information to the XEPs database</li>
     <li>publish version 0.1 of the XEP to the xmpp.org website <note>The canonical URL for accessing XMPP Extensions is &lt;<link url='http://www.xmpp.org/extensions/'>http://www.xmpp.org/extensions/</link>&gt;.</note></li>
     <li>publicly announce the existence of the XEP by sending a message to the Standards list</li>