Synchronized with cvs version 1.63 of developers-reference.sgml

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 45dcc2202c0d0a02c85e21d855065e4d4a101ce8..3731cf9b956a60cf32cac6897a371fe127b02956 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.60 $">
+  <!entity cvs-rev "$Revision: 1.63 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -714,7 +714,7 @@ To summarize, the Debian archive has a root directory within an FTP
 server.  For instance, at the mirror site,
 <ftpsite>ftp.us.debian.org</ftpsite>, the Debian archive itself is
 contained in <ftppath>/debian</ftppath>, which is a common location
-(another is <ftppath>/pub/debian</ftppath>).
+(another is <tt>/pub/debian</tt>).
        <p>
 A distribution is comprised of Debian source and binary packages, and the
 respective <tt>Sources</tt> and <tt>Packages</tt> index files, containing
@@ -1065,7 +1065,7 @@ Remove the package, then reinstall it.
 To upload a package, you need a personal account on
 <ftpsite>ftp-master.debian.org</ftpsite>, which you should have as an
 official maintainer. If you use <prgn>scp</prgn> or <prgn>rsync</prgn>
-to transfer the files, place them into <ftppath>&us-upload-dir;</ftppath>;
+to transfer the files, place them into <tt>&us-upload-dir;</tt>;
 if you use anonymous FTP to upload, place them into
 <ftppath>/pub/UploadQueue/</ftppath>.
           <p>
@@ -1094,10 +1094,12 @@ file: <example>dinstall -n foo.changes</example>
        <sect1 id="upload-non-us">Uploading to <tt>non-US</tt> (pandora)
          <p>
 As discussed above, export controlled software should not be uploaded
-to <tt>ftp-master</tt>.  Instead, use <prgn>scp</prgn> or non-anonymous
-FTP to copy the package to <ftpsite>non-us.debian.org</ftpsite>, placing
-the files in <ftppath>&non-us-upload-dir;</ftppath>. By default, you can
+to <tt>ftp-master</tt>.  Instead, use <prgn>scp</prgn> or <prgn>rsync</prgn>
+to copy the package to <ftpsite>non-us.debian.org</ftpsite>, placing
+the files in <tt>&non-us-upload-dir;</tt>. By default, you can
 use the same account/password that works on <tt>ftp-master</tt>.
+If you use anonymous FTP to upload, place the files into
+<ftppath>/pub/UploadQueue/</ftppath>.
          <p>
 The program <prgn>dupload</prgn> comes with support for uploading to
 <tt>non-us</tt>; please refer to the documentation that comes with
@@ -1959,7 +1961,7 @@ list.
 
 
     <chapt id="newmaint">
-      <heading>Interaction with prospective developers</heading>
+      <heading>Interaction with Prospective Developers</heading>
 
       <p>
 This chapter describes procedures that existing Debian developers should
@@ -1977,6 +1979,12 @@ the package and verify that it is good enough for inclusion in Debian.
 (Note that if the sponsored package is new, the FTP admins will also have to
 inspect it before letting it in.)
        <p>
+Sponsoring merely by signing the upload or just recompiling is
+<strong>definitely not recommended</strong>. You need to build the source
+package just like you would build a package of your own. Remember that it
+doesn't matter that you left the prospective developer's name both in the
+changelog and the control file, the upload can still be traced to you.
+       <p>
 If you are an application manager for a prospective developer, you can also
 be their sponsor. That way you can also verify the how the applicant is
 handling the `Tasks and Skills' part of their application.