Alioth

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2360 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/debian/changelog b/debian/changelog
index fef1bae299c74ac03867a3937b727028aeebbb83..47cb1857ebacade926caa05555130c0c47e32e69 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,7 @@ developers-reference (3.3.4) WORKING VERSION; urgency=low
     + fixed language in the PTS section, prompted by a patch from
       Romain FRANCOISE, thank you, closes: #197741.
     + updated the mailing lists section (again)
+    + documented Alioth, somewhat
 
  -- Adam Di Carlo <aph@debian.org>  Mon, 16 Jun 2003 04:22:22 -0400
 

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 601c837c561db2f3d1e9070fbcef7a1a454ed750..6b2e7a8ab98a051245becb0bd7049b8b1e536d01 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!ENTITY % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!ENTITY cvs-rev "$Revision: 1.213 $">
+  <!ENTITY cvs-rev "$Revision: 1.214 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -487,8 +487,8 @@ Before requesting a mailing list that relates to the development of a
 package (or a small group of related packages), please consider if using
 an alias (via a .forward-aliasname file on master.debian.org, which
 translates into a reasonably nice <var>you-aliasname@debian.org</var>
-address) or a self-managed mailing list on
-<url name="Alioth" id="&url-alioth;"> is more appropriate.
+address) or a self-managed mailing list on <qref id="alioth">Alioth</qref>
+is more appropriate.
        <p>
 If you decide that a regular mailing list on lists.debian.org is really what
 you want, go ahead and fill in a request, following <url name="the HOWTO"
@@ -1403,7 +1403,7 @@ indefinitely) and news items in the "latest news" section.
        <p>
 Static news items can be used to indicate:
 <list>
-<item>the availability of a project hosted on alioth.debian.org for co-maintaining the package
+<item>the availability of a project hosted on <qref id="alioth">Alioth</qref> for co-maintaining the package
 <item>a link to the upstream web site
 <item>a link to the upstream bug tracker
 <item>the existence of an IRC channel dedicated to the software
@@ -1477,6 +1477,21 @@ It is a good idea to look up your own data regularly so that
 you don't forget any open bug, and so that you don't forget which
 packages are under your responsibility.
 
+    <sect id="alioth">Debian *Forge: Alioth
+       <p>
+Alioth is a fairly new Debian service, based on a slightly modified version
+of the GForge software (which evolved from SourceForge). This software
+offers developers access to easy-to-use tools such as bug trackers, patch
+manager, project/task managers, file hosting services, mailing lists, CVS
+repositories etc. All these tools are managed via a web interface.
+       <p>
+It is intended to provide facilities to free software projects backed or led
+by Debian, facilitate contributions from external developers to projects
+started by Debian, and help projects whose goals are the promotion of Debian
+or its derivatives.
+       <p>
+For more information please visit <url id="&url-alioth;">.
+
 
    <chapt id="pkgs">Managing Packages
        <p>
@@ -3071,7 +3086,8 @@ the <tt>Maintainer</tt> field of the <file>debian/control</file> file.
 Co-maintainers are all the other maintainers.</p>
         <p>
 In its most basic form, the process of adding a new co-maintainer is
-quite easy:<list>
+quite easy:
+<list>
             <item>
               <p>
 Setup the co-maintainer with access to the sources you build the
@@ -3095,10 +3111,12 @@ Using the PTS (<ref id="pkg-tracking-system">), the co-maintainers
 should subscribe themselves to the appropriate source package.</p>
             </item>
           </list></p>
+       <p>
+Collaborative maintenance can often be further eased with the use of
+tools on Alioth (see <ref id="alioth">).
       </sect>
 
 
-
   <chapt id="best-pkging-practices">
     <heading>Best Packaging Practices</heading>
     <p>