sponsoring service down

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 21fdade7a51ccb962729aebba66f17bbc079355c..80bd2ae62f40b572a9acb90ab1c0ae681a942d61 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.252 $">
+  <!ENTITY cvs-rev "$Revision: 1.254 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -2101,7 +2101,7 @@ We prefer the <tt>closes: #<var>XXX</var></tt> syntax, as it is the
 most concise entry and the easiest to integrate with the text of the
 <file>changelog</file>.
        <p>
-If an upload is identified as <ref id="nmu" name="Non-maintainer upload (NMU)">
+If an upload is identified as <qref id="nmu">Non-maintainer upload (NMU)</qref>
 (and that is the case if the name of the person who commits this change
 is not exactly the same as any one of Maintainer or Uploader,
 except if the maintainer is the qa group),
@@ -4802,9 +4802,11 @@ Sponsoring a package means uploading a package for a maintainer who is not
 able to do it on their own, a new maintainer applicant. Sponsoring a package
 also means accepting responsibility for it.
        <p>
+       <!-- FIXME: service down
 If you wish to volunteer as a sponsor, you can sign up at <url
 id="&url-sponsors;">.
        <p>
+       -->
 New maintainers usually have certain difficulties creating Debian packages
 &mdash; this is quite understandable. That is why the sponsor is there, to check
 the package and verify that it is good enough for inclusion in Debian.