From 6a0a618b63bc76eab2b6bcab058d714b0c3e8291 Mon Sep 17 00:00:00 2001
From: joy <joy@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Sat, 21 Dec 2002 19:03:42 +0000
Subject: [PATCH] noted that debian-devel (not -private! boo!) can be contacted
 to ask about a missing maintainer; rephrased the stuff about conflicts and
 mentioned the ways of resolving such issues

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2014 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 developers-reference.sgml | 20 ++++++++++++++------
 1 file changed, 14 insertions(+), 6 deletions(-)

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 173075a..7adb925 100644
--- 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.155 $">
+  <!entity cvs-rev "$Revision: 1.156 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -2482,11 +2482,16 @@ page for information and procedures.
 It is not OK to simply take over a package that you feel is neglected
 &mdash; that would be package hijacking.  You can, of course, contact the
 current maintainer and ask them if you may take over the package.
-However, without their assent, you may not take over the package.
-Even if they ignore you, that is still not grounds to take over a
-package.  If you really feel that a maintainer has gone AWOL (absent
-without leave), post a query to &email-debian-private;. You may also
-inform the QA group (cf. <ref id="mia-qa">).
+If you have reason to believe a maintainer has gone AWOL
+(absent without leave), see <ref id="mia-qa">.
+	<p>
+Generally, you may not take over the package without the assent of the
+current maintainer. Even if they ignore you, that is still not grounds to
+take over a package. Complaints about maintainers should be brought up on
+the developers' mailing list. If the discussion doesn't end with a positive
+conclusion, and the issue is of a technical nature, consider bringing it to
+the attention of the technical committee (see the <url name="technical
+committee web page" id="&url-tech-ctte;"> for more information).
 	<p>
 If you take over an old package, you probably want to be listed as the
 package's official maintainer in the bug system. This will happen
@@ -3517,6 +3522,9 @@ developer who has actually uploaded the package. Given that they signed the
 package, they're responsible for the upload anyhow, and should 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.
+      <p>
 Once you have gathered all of this, you can contact &email-debian-qa;.
 People on this alias will use the information you provided in order to
 decide how to proceed. For example, they might orphan one or all of the
-- 
2.30.2