subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cmpil...@apache.org
Subject svn commit: r901364 - /subversion/site/publish/docs/community-guide/index.html
Date Wed, 20 Jan 2010 20:17:13 GMT
Author: cmpilato
Date: Wed Jan 20 20:17:13 2010
New Revision: 901364

URL: http://svn.apache.org/viewvc?rev=901364&view=rev
Log:
* site/publish/docs/community-guide/index.html
  Fix a slew of broken or stale links, and update mailing list
  references to point to the new lists.

Modified:
    subversion/site/publish/docs/community-guide/index.html

Modified: subversion/site/publish/docs/community-guide/index.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/docs/community-guide/index.html?rev=901364&r1=901363&r2=901364&view=diff
==============================================================================
--- subversion/site/publish/docs/community-guide/index.html (original)
+++ subversion/site/publish/docs/community-guide/index.html Wed Jan 20 20:17:13 2010
@@ -163,12 +163,12 @@
 <p>The community exists mainly through mailing lists and a Subversion
 repository.  To participate:</p>
 
-<p>Go to <a href="http://subversion.tigris.org/"
->http://subversion.tigris.org/</a> and</p>
+<p>Go to <a href="http://subversion.apache.org/"
+>http://subversion.apache.org/</a> and</p>
 
 <ul>
 <li><p>Join the "dev", "svn", and "announce" mailing lists.
-       The dev list, dev@subversion.tigris.org, is where almost all
+       The dev list, dev@subversion.apache.org, is where almost all
        discussion takes place.  All development questions should go
        there, though you might want to check the list archives first.
        The "svn" list receives automated commit emails.</p></li>
@@ -190,16 +190,12 @@
 <li><p>The bugs/issues database
        <a href="http://subversion.tigris.org/issue-tracker.html"
                >http://subversion.tigris.org/issue-tracker.html</a></p></li>
-
-<li><p>The bite-sized tasks page
-       <a href="http://subversion.tigris.org/project_tasks.html"
-               >http://subversion.tigris.org/project_tasks.html</a></p></li>
 </ul>
 
 <p>To submit code, simply send your patches to
-dev@subversion.tigris.org.  No, wait, first read the rest of this
+dev@subversion.apache.org.  No, wait, first read the rest of this
 file, <i>then</i> start sending patches to
-dev@subversion.tigris.org. :-)</p>
+dev@subversion.apache.org. :-)</p>
 
 <p>To help manage the issues database, read over the issue summaries,
 looking and testing for issues that are either invalid, or are
@@ -207,7 +203,7 @@
 because bugs often get unknowingly fixed as side effects of other
 changes in the code, and the second because people sometimes file an
 issue without noticing that it has already been reported.  If you are
-not sure about an issue, post a question to dev@subversion.tigris.org.
+not sure about an issue, post a question to dev@subversion.apache.org.
 ("Subversion: We're here to help you help us!")</p>
 
 <p>Another way to help is to set up automated builds and test suite
@@ -226,10 +222,11 @@
 <ol>
 <li><p>Design</p>
 
-     <p>A <a href="design.html">design spec</a> was written in June 2000,
-     and is a bit out of date.  But it still gives a good theoretical
-     introduction to the inner workings of the repository, and to
-     Subversion's various layers.</p>
+     <p>A <a href="http://svn.apache.org/repos/asf/subversion/trunk/notes/subversion-design.html"
+     >design spec</a> was written in June 2000, and is a bit out of
+     date.  But it still gives a good theoretical introduction to the
+     inner workings of the repository, and to Subversion's various
+     layers.</p>
 </li>
 
 <li><p>API Documentation</p>
@@ -248,10 +245,10 @@
 
 <li> <p>Network Protocols</p>
 
-     <p>The <a href="webdav-usage.html">WebDAV Usage</a> document is
-     an introduction to Subversion's DAV network protocol, which is
-     an extended dialect of HTTP and uses URLs beginning with
-     "http://" or "https://".</p>
+     <p>The <a href="http://svn.apache.org/repos/asf/subversion/trunk/notes/http-and-webdav/webdav-usage.html"
+     >WebDAV Usage</a> document is an introduction to Subversion's DAV
+     network protocol, which is an extended dialect of HTTP and uses
+     URLs beginning with "http://" or "https://".</p>
 
      <p>The <a
 href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_ra_svn/protocol"
@@ -354,11 +351,6 @@
 <li><p><tt>doc/</tt><br />
     User and Developer documentation.</p>
 </li>
-<li><p><tt>www/</tt><br />
-    Subversion web pages (live content at
-      <a href="http://subversion.tigris.org/"
-      >http://subversion.tigris.org/</a>).</p>
-</li>
 <li><p><tt>tools/</tt><br />
     Stuff that works with Subversion, but that Subversion doesn't
     depend on.  Code in tools/ is maintained collectively by the
@@ -669,7 +661,7 @@
 <div class="h2" id="patches" title="patches">
 <h2>Patch submission guidelines</h2>
 
-<p>Mail patches to dev@subversion.tigris.org, starting the subject
+<p>Mail patches to dev@subversion.apache.org, starting the subject
 line with <tt>[PATCH]</tt>.  This helps our patch manager spot patches
 right away.  For example:</p>
 
@@ -1968,10 +1960,8 @@
 <p>In general, there is a tension between making entries easy to find
 by searching for identifiers, and wasting time or producing unreadable
 entries by being exhaustive.  Use the above guidelines and your best
-judgment, and be considerate of your fellow developers.  (Also, <a
-href="http://subversion.tigris.org/servlets/BrowseList?listName=svn">
-run "svn log"</a> to see how others have been writing their log
-entries.)</p>
+judgment, and be considerate of your fellow developers.  (Also, use
+"svn log" to see how others have been writing their log entries.)</p>
 
 <p>Log messages for documentation or translation have somewhat looser
 guidelines.  The requirement to name every symbol obviously does not
@@ -2924,7 +2914,7 @@
 <div class="h2" id="sending-patches" title="sending-patches">
 <h2>Sending patches</h2>
 
-<p>See <a href="patches">here</a> for advice on how to send in a
+<p>See <a href="#patches">here</a> for advice on how to send in a
 patch.  Note that you can send in a patch to modify these web pages as
 well as to modify code; the web pages' repository URL is
 <a href="http://svn.apache.org/repos/asf/subversion/site/"
@@ -3034,8 +3024,10 @@
 >users@subversion.apache.org</a>, or ask in IRC, <a
 href="irc://irc.freenode.net/#svn">irc.freenode.net, channel #svn</a>.</p>
 
-<p>You should also <a href="issue-tracker.html#find" >search in the bug
-tracker</a> to see if anyone has already reported this bug.  </p>
+<p>You should
+also <a href="http://subversion.tigris.org/issue-tracker.html#find"
+>search in the bug tracker</a> to see if anyone has already reported
+this bug.</p>
 
 <p>Once you've established that it's a bug, and that we don't know
 about it already, the most important thing you can do is come up with
@@ -3089,8 +3081,8 @@
 href="mailto:dev@subversion.apache.org"
 >dev@subversion.apache.org</a>, or if you have already been there and
 been asked to file an issue, then go to the <a
-href="issue-tracker.html">Issue Tracker</a> and follow the
-instructions there.</p>
+href="http://subversion.tigris.org/issue-tracker.html">Issue
+Tracker</a> and follow the instructions there.</p>
 
 <p>Thanks.  We know it's a lot of work to file an effective bug
 report, but a good report can save hours of a developer's time, and
@@ -3108,9 +3100,10 @@
     <a href="mailto:users@subversion.apache.org"
                    >users@subversion.apache.org</a>.
     Once it's confirmed as a bug, someone, possibly you, can enter it
-    into the <a href="issue-tracker.html">issue tracker</a>.  (Or if
-    you're pretty sure about the bug, go ahead and post directly to 
-    our development list, <a href="mailto:dev@subversion.apache.org"
+    into the <a href="http://subversion.tigris.org/issue-tracker.html"
+    >issue tracker</a>.  (Or if you're pretty sure about the bug, go
+    ahead and post directly to our development
+    list, <a href="mailto:dev@subversion.apache.org"
     >dev@subversion.apache.org</a>.  But if you're not sure, it's
     better to post to <a href="mailto:users@subversion.apache.org"
     >users@</a> first; someone there can tell you whether the behavior
@@ -4154,11 +4147,14 @@
 <h2>The actual releasing</h2>
 
 <p><b>Upload the tarballs to
-  http://subversion.tigris.org/downloads/.</b></p>
-<p>The RM will be given details on how to do this via private
-channels.</p>
+   http://subversion.tigris.org/downloads/.</b></p>
+
+<p>We currently do this by adding and committing them to the
+  <tt>/trunk/www/downloads</tt> directory of the Subversion repository
+  associated with http://subversion.tigris.org/.</p>
 
 <p><b>Update Tigris "Documents &amp; files" area</b></p>
+
 <p>Update the links to the tarballs in the Documents &amp; files
 Tigris webapp.</p>
 
@@ -4321,7 +4317,7 @@
 <p>Currently available translations can be found in <a
 href="http://svn.apache.org/repos/asf/subversion/trunk/subversion/po/"
 >the po section of the repository</a>.  Please contact
-dev@subversion.tigris.org when you want to start a translation not
+dev@subversion.apache.org when you want to start a translation not
 available yet.  Translation discussion takes place both on that list
 and on dedicated native language mailing lists (<a
 href="http://subversion.tigris.org/servlets/ProjectMailingListList"
@@ -4411,8 +4407,8 @@
 
 <p>Please replace those with these two lines:</p>
 <pre>
-  "Last-Translator: Subversion Developers &lt;dev@subversion.tigris.org&gt;\n"
-  "Language-Team: YOUR LANGUAGE &lt;dev@subversion.tigris.org&gt;\n"
+  "Last-Translator: Subversion Developers &lt;dev@subversion.apache.org&gt;\n"
+  "Language-Team: YOUR LANGUAGE &lt;dev@subversion.apache.org&gt;\n"
 </pre>
 
 </div>  <!-- unix-gnu-gettext -->
@@ -4427,7 +4423,8 @@
 <div class="h3" id="windows" title="windows">
 <h3>Windows</h3>
 
-<p>See <a href="/issues/show_bug.cgi?id=1977">issue #1977</a>.</p>
+<p>See <a href="http://subversion.tigris.org/issues/show_bug.cgi?id=1977"
+>issue&nbsp;#1977</a>.</p>
 
 </div>  <!-- windows -->
 
@@ -4458,7 +4455,7 @@
 <h2>Submitting your po file</h2>
 
 <p>Please don't mail large po files to the mailing lists.  There are many
-subscribers on dev@subversion.tigris.org who are on slow links and do
+subscribers on dev@subversion.apache.org who are on slow links and do
 not want to receive a large file by email.  Instead, place the po file
 somewhere on the Internet for download, and just post the URL.  If you
 do not have a site available, please ask on dev@ and someone will help
@@ -4583,7 +4580,7 @@
 this field.</p>
 
 <p>Since some tools require this field to consider the po file valid
-(i.e. Emacs PO Mode), you can put "dev@subversion.tigris.org" into
+(i.e. Emacs PO Mode), you can put "dev@subversion.apache.org" into
 this field.</p>
 
 </div>  <!-- empty-string-conventions -->



Mime
View raw message