chapter titles need caps

[developers-reference.git] / developers-reference.sgml

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 0b0de53fac9614ff1b7301e56bd6819a400ff0e0..8a32ae87557077b71aca12e31f1079e80c429497 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.88 $">
+  <!entity cvs-rev "$Revision: 1.90 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -34,7 +34,7 @@
 
       <copyright>
        <copyrightsummary>
-copyright &copy;1998 &ndash 2001 Adam Di Carlo</copyrightsummary>
+copyright &copy;1998 &ndash 2002 Adam Di Carlo</copyrightsummary>
        <copyrightsummary>
 copyright &copy;1997, 1998 Christian Schwarz</copyrightsummary>
        <p>
@@ -89,13 +89,14 @@ generally agreed-upon best practices.  Thus, it is what is called a
 
     <chapt id="new-maintainer">Applying to Become a Maintainer
        
-      <sect>Getting started
+      <sect id="getting-started">Getting started
        <p>
-So, you've read all the documentation, you understand what everything
-in the <package>hello</package> example package is for, and you're about to
-Debianize your favourite piece of software.  How do you actually
-become a Debian developer so that your work can be incorporated into
-the Project?
+So, you've read all the documentation, you've gone through the <url
+id="&url-newmaint-guide;" name="Debian New Maintainers' Guide">,
+understand what everything in the <package>hello</package> example
+package is for, and you're about to Debianize your favourite piece of
+software.  How do you actually become a Debian developer so that your
+work can be incorporated into the Project?
        <p>
 Firstly, subscribe to &email-debian-devel; if you haven't already.
 Send the word <tt>subscribe</tt> in the <em>Subject</em> of an email
@@ -237,7 +238,7 @@ before actually applying.  If you are well prepared, you can save
 a lot of timer later on.
 
 
-      <sect id="mentors">Debian Mentors
+      <sect id="mentors">Debian Mentors and Sponsors
        <p>
 The mailing list &email-debian-mentors; has been set up for novice
 maintainers who seek help with initial packaging and other
@@ -246,6 +247,13 @@ to that list (see <ref id="mailing-lists"> for details).
        <p>
 Those who prefer one-on-one help (e.g., via private email) should also
 post to that list and an experienced developer will volunteer to help.
+       <p>
+In addition, if you have some packages ready for inclusion in Debian,
+but are waiting for your new maintainer application to go through, you
+might be able find a sponsor to upload your package for you.  Sponsors
+are people who are official Debian maintainers, and who are willing to
+critique and upload your packages for you.  Sponsorees can request a
+sponsors at <url id="&url-sponsors;">.
 
 
     <chapt id="developer-duties">Debian Developer's Duties
@@ -868,7 +876,7 @@ symbolic links for <em>stable</em>, <em>testing</em>, and
 <em>unstable</em> point to the appropriate release directories.
 
 
-    <chapt id="upload">Package uploads
+    <chapt id="upload">Package Uploads
 
       <sect>New packages
        <p>