I really mean it!

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

diff --git a/README-contrib b/README-contrib
index 38a598e6646f3889e39676c60e76d2622f707b2f..226b5a9c5a2235712993b9564638a3cc514b82b0 100644 (file)
--- a/README-contrib
+++ b/README-contrib
@@ -30,7 +30,8 @@ patches against the CVS sources, about which see below.
 
 Do not commit patches to the developers reference yourself unless
 authorized to do so. Patches need to be finalized and common opinion
 
 Do not commit patches to the developers reference yourself unless
 authorized to do so. Patches need to be finalized and common opinion

-before they are applied.
+before they are applied. This is even true if you happen to have
+cvs access for other reasons.

 
 
 * CVS
 
 
 * CVS

diff --git a/developers-reference.sgml b/developers-reference.sgml
index a00cabd3ace8f97d7fcf6ee63b1a026c12149ca0..63a91b9085d26bb1e4f9737e4f6dba244787237d 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -7,7 +7,7 @@
   <!ENTITY % dynamicdata  SYSTEM "dynamic.ent" > %dynamicdata;
 
   <!-- CVS revision of this document -->
   <!ENTITY % dynamicdata  SYSTEM "dynamic.ent" > %dynamicdata;
 
   <!-- CVS revision of this document -->

-  <!ENTITY cvs-rev "$Revision: 1.291 $">
+  <!ENTITY cvs-rev "$Revision: 1.292 $">

 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->


@@ -31,7 +31,7 @@
 
       <copyright>
        <copyrightsummary>
 
       <copyright>
        <copyrightsummary>

-copyright &copy; 2004&mdash;2005 Andreas Barth</copyrightsummary>
+copyright &copy; 2004&mdash;2006 Andreas Barth</copyrightsummary>

        <copyrightsummary>
 copyright &copy; 1998&mdash;2003 Adam Di Carlo</copyrightsummary>
        <copyrightsummary>
        <copyrightsummary>
 copyright &copy; 1998&mdash;2003 Adam Di Carlo</copyrightsummary>
        <copyrightsummary>


@@ -5121,11 +5121,9 @@ maintainers who are deemed Missing In Action are recorded.  When a member of the
 QA group contacts an inactive maintainer or finds more information about
 one, this is recorded in the MIA database.  This system is available
 in /org/qa.debian.org/mia on the host qa.debian.org, and can be queried
 QA group contacts an inactive maintainer or finds more information about
 one, this is recorded in the MIA database.  This system is available
 in /org/qa.debian.org/mia on the host qa.debian.org, and can be queried

-with a tool known as <prgn>mia-history</prgn>.  By default,
-<prgn>mia-history</prgn> shows information about every person it knows
-about, but it accepts regular expressions as arguments which it uses to
-match user names.  <example>mia-history --help</example> shows which
-arguments are accepted.  If you find that no information has been recorded
+with a tool known as <prgn>mia-query</prgn>.
+Use <example>mia-query --help</example> to see how to query the database.
+If you find that no information has been recorded

 about an inactive maintainer already, or that you can add more information,
 you should generally proceed as follows.
       <p>
 about an inactive maintainer already, or that you can add more information,
 you should generally proceed as follows.
       <p>


@@ -5160,15 +5158,16 @@ about the maintainer in question as possible. This includes:
               non-Debian mailing lists or news groups.
       </list>
       <p>
               non-Debian mailing lists or news groups.
       </list>
       <p>

-One big problem are packages which were sponsored &mdash; the maintainer is not
+A bit of a problem are packages which were sponsored &mdash; the maintainer is not

 an official Debian developer. The echelon information is not available for
 sponsored people, for example, so you need to find and contact the Debian
 developer who has actually uploaded the package. Given that they signed the
 an official Debian developer. The echelon information is not available for
 sponsored people, for example, so you need to find and contact the Debian
 developer who has actually uploaded the package. Given that they signed the

-package, they're responsible for the upload anyhow, and should know what
+package, they're responsible for the upload anyhow, and are likely to know what

 happened to the person they sponsored.
       <p>
 It is also allowed to post a query to &email-debian-devel;, asking if anyone
 is aware of the whereabouts of the missing maintainer.
 happened to the person they sponsored.
       <p>
 It is also allowed to post a query to &email-debian-devel;, asking if anyone
 is aware of the whereabouts of the missing maintainer.

+Please Cc: the person in question.

       <p>
 Once you have gathered all of this, you can contact &email-mia;.
 People on this alias will use the information you provided in order to
       <p>
 Once you have gathered all of this, you can contact &email-mia;.
 People on this alias will use the information you provided in order to


@@ -5182,12 +5181,16 @@ cannot dedicate all of our time to Debian. Also, you are not aware of the
 circumstances of the person who is involved. Perhaps they might be
 seriously ill or might even had died &mdash; you do not know who may be on the
 receiving side. Imagine how a relative will feel if they read the e-mail
 circumstances of the person who is involved. Perhaps they might be
 seriously ill or might even had died &mdash; you do not know who may be on the
 receiving side. Imagine how a relative will feel if they read the e-mail

-of the deceased and find a very impolite, angry and accusing message!)
+of the deceased and find a very impolite, angry and accusing message!

       <p>
 On the other hand, although we are volunteers, we do have a responsibility. 
 So you can stress the importance of the greater good &mdash; if a maintainer does
 not have the time or interest anymore, they should "let go" and give the
 package to someone with more time.
       <p>
 On the other hand, although we are volunteers, we do have a responsibility. 
 So you can stress the importance of the greater good &mdash; if a maintainer does
 not have the time or interest anymore, they should "let go" and give the
 package to someone with more time.

+      <p>
+If you are interested in working in the MIA team, please have a look at the
+README file in /org/qa.debian.org/mia on qa.debian.org where the technical
+details and the MIA procedures are documented and contact &email-mia;.

 
 
     <sect id="newmaint">
 
 
     <sect id="newmaint">