From 2d1e601736b9f0e825741d6521eb785dedeffd0b Mon Sep 17 00:00:00 2001
From: Ian Jackson <ijackson@chiark.greenend.org.uk>
Date: Sat, 30 Aug 2014 00:35:17 +0100
Subject: [PATCH] Salvaging by NMUing Maintainer update (as discussed at DC14).

---
 debian/changelog |  7 +++++++
 pkgs.dbk         | 43 +++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 50 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index ef7cada..029d21f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+developers-reference (3.4.14~~iwj) UNRELEASED; urgency=low
+
+  [ Ian Jackson ]
+  * Salvaging by NMUing Maintainer update (as discussed at DC14).
+
+ --
+
 developers-reference (3.4.14) UNRELEASED; urgency=medium
 
   [ Paul Wise ]
diff --git a/pkgs.dbk b/pkgs.dbk
index 5a34b95..f7750c8 100644
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -2219,6 +2219,49 @@ BTS but will be listed as affecting your maintainer version of the package.
 
 </section>
 
+<section id="nmu-salvage">
+<title>Joining the maintainers of a package (aka Salvaging)</title>
+
+<para>
+If you find yourself NMUing the same package on multiple occasions,
+you should consider whether you ought to be formally listed as a
+maintainer for that package.
+</para>
+
+<para>
+As a rule of thumb, if you have made four well-received NMUs of a
+package over a period of between 3 and 12 months, you should probably
+become one of the maintainers on your next (fifth) upload.
+<para>
+
+</para>
+The exact point at which becoming a maintainer is appropriate depends
+on the circumstances.  Particularly relevant are: how much more
+attention the package needs compared to what it's getting; the views
+of the existing maintainer; how many reverse dependencies the package
+has.  Explicit consent from the existing maintainer to become one of
+the maintainers of the package is not required, but of course such a
+change should not be made in the face of opposition from the existing
+maintainer.
+</para>
+
+<para>
+To become one of the maintainers: include, in an NMU, a change which
+adds yourself to the Maintainer field of the package (or to Uploaders
+if the package is team maintained).  Such an upload should be made to
+DELAYED-14, so that the existing maintainer(s) have an opportunity to
+object and revert.
+</para>
+
+<para>
+If you aren't sure whether to add yourself to Maintainers, please feel
+free to get a second opinion.  For a non-DD, your sponsor will be able
+to advise.  If you are a DD, you can still approach another DD to
+sponsor your upload; that will provide the opportunity for another
+developer to explicitly endorse your addition to the maintainer team.
+Alternatively, you can ask on the debian-qa list.
+</para>
+
 <section id="nmu-binnmu">
 <title>Source NMUs vs Binary-only NMUs (binNMUs)</title>
 
-- 
2.30.2