X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=beyond-pkging.dbk;h=77a973947cfcc112422e07f2a00f22e2337108fc;hp=0d27668977c723d4f15da1cf50964b05fa1f119b;hb=3772122364b83f680c4c8486afe9dae5e34acae9;hpb=e3cb6d3f6afc7f8ed94ea6021aa0f9b4fa0e5551
diff --git a/beyond-pkging.dbk b/beyond-pkging.dbk
index 0d27668..77a9739 100644
--- a/beyond-pkging.dbk
+++ b/beyond-pkging.dbk
@@ -124,8 +124,8 @@ many problems as possible. They are announced on
&email-debian-devel-announce; and the announcement explains
which area will be the focus of the party: usually they focus on release
critical bugs but it may happen that they decide to help finish a major upgrade
-(like a new perl version which requires recompilation of all the binary
-modules).
+(like a new perl version which requires recompilation of all
+the binary modules).
The rules for non-maintainer uploads differ during the parties because the
@@ -190,11 +190,11 @@ There is a simple system (the MIA database) in which information about
maintainers who are deemed Missing In Action is 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 with a
-tool known as mia-query. Use mia-query --help
-to see how to query the database. If you find that no information has been
-recorded about an inactive maintainer yet, or that you can add more
-information, you should generally proceed as follows.
+/org/qa.debian.org/mia on the host qa.debian.org
+, and can be queried with the mia-query tool.
+Use mia-query --help to see how to query the database.
+If you find that no information has been recorded about an inactive maintainer yet,
+or that you can add more information, you should generally proceed as follows.
The first step is to politely contact the maintainer, and wait a reasonable
@@ -211,11 +211,12 @@ maintainer in question as possible. This includes:
-The echelon information available through the echelon information available through the developers' LDAP database, which indicates
when the developer last posted to a Debian mailing list. (This includes
-uploads via debian-*-changes lists.) Also, remember to check whether the
-maintainer is marked as on vacation in the database.
+mails about uploads distributed via the &email-debian-devel-changes; list.)
+Also, remember to check whether the maintainer is marked as on vacation in
+the database.
@@ -237,11 +238,11 @@ groups.
A bit of a problem are packages which were sponsored â 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
-package, they're responsible for the upload anyhow, and are likely to know what
-happened to the person they sponsored.
+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 are likely to know
+what happened to the person they sponsored.
It is also allowed to post a query to &email-debian-devel;,
@@ -272,9 +273,9 @@ someone with more time.
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;.
+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;.