Added ';' at the end of an entity.

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index a21ed3bb1776bb563e2558bd920bf4e57887bc54..be1bafe63b223c9c02e051b22ffa7fd9e3b789fd 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.70 $">
+  <!entity cvs-rev "$Revision: 1.74 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -129,7 +129,7 @@ Debian GNU/Linux has grown to over &number-of-maintainers; people and
 our systems are used in several very important places we have to be
 careful about being compromised.  Therefore, we need to verify new
 maintainers before we can give them accounts on our servers and
-letting them upload packages.
+let them upload packages.
        <p>
 Registration requires that the following information be sent in
 appropriate steps described at <url id="&url-newmaint-checklist;"
@@ -309,10 +309,14 @@ you're on vacation.
 In order to inform the other developers, there's two things that you should do.
 First send a mail to &email-debian-private; giving the period of time when
 you will be on vacation.  You can also give some special instructions on what to
-do if any problem occurs. Next you should update your information
+do if any problem occurs. Be aware that some people don't care for vacation
+notices and don't want to read them; you should prepend "[VAC] " to the
+subject of your message so that it can be easily filtered.
+       <p>
+Next you should update your information
 available in the Debian LDAP database and mark yourself as ``on vacation''
 (this information is only accessible to debian developers). Don't forget
-to remove the ``on vacation'' flag when you come back.
+to remove the ``on vacation'' flag when you come back!
 
       <sect id="upstream-coordination">Coordination With Upstream Developers
        <p>
@@ -364,6 +368,22 @@ id="orphaning">). Alternatively, you may ask the help of other people
 in order to catch up the backlog of bugs that you have (you can ask
 for help on &email-debian-qa; or &email-debian-devel;).
 
+    <sect id="mia-qa">Dealing with unreachable maintainers
+      <p>
+If you notice that a package is lacking maintenance, you should
+make sure the maintainer is active and will continue to work on
+their packages. Try contacting them yourself.
+      <p>
+If you do not get a reply after a few weeks you should collect all 
+useful information about this maintainer. Start by logging in to 
+the <url id="http://db.debian.org" name="Debian Developer's Database">
+and doing a full search to check whether the maintainer is on vacation
+and when they were last seen. Collect any important package names
+they maintain and any Release Critical bugs filled against them.
+      <p>
+Send all this information to &email-debian-qa;, in order to let the 
+QA people do whatever is needed.
+
       <sect>Retiring Gracefully
        <p>
 If you choose to leave the Debian project, you should make sure you do