X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=developers-reference.sgml;h=63a91b9085d26bb1e4f9737e4f6dba244787237d;hb=770042b07cc441a9a737efd52258c0845423f391;hp=3a52e9f1bbc059ccc2f20a1e7a475136a3d4c608;hpb=6f5535e521e72fdc605aac4238a199c8f378b1c9;p=developers-reference.git diff --git a/developers-reference.sgml b/developers-reference.sgml index 3a52e9f..63a91b9 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -7,7 +7,7 @@ %dynamicdata; - + @@ -31,7 +31,7 @@ -copyright © 2004—2005 Andreas Barth +copyright © 2004—2006 Andreas Barth copyright © 1998—2003 Adam Di Carlo @@ -1357,12 +1357,17 @@ maintainer has set up forwarding commit notifications to the PTS. Translations of descriptions or debconf templates submitted to the Debian Description Translation Project. + + derivatives + +Information about changes made to the package in derivative distributions +(for example Ubuntu). The PTS email interface

You can control your subscription(s) to the PTS by sending -various commands to pts@qa.debian.org. +various commands to pts@qa.debian.org. @@ -1380,6 +1385,11 @@ various commands to pts@qa.debian.org. using the specified email address or the sender address if the second argument is left out. +unsubscribeall [<email>] + + Removes all subscriptions of the specified email address or the sender + address if the second argument is left out. + which [<email>] Lists all subscriptions for the sender or the email address optionally @@ -1396,6 +1406,7 @@ various commands to pts@qa.debian.org. summary: automatic summary mails about the state of a package cvs: notification of CVS commits ddtp: translations of descriptions and debconf templates + derivatives: changes made on the package by derivative distributions upload-source: announce of a new source upload that has been accepted upload-binary: announce of a new binary-only upload (porting) @@ -1412,7 +1423,14 @@ various commands to pts@qa.debian.org. keyword [<email>] {+|-|=} <list of keywords> Accept (+) or refuse (-) mails classified under the given keyword(s). - Define the list (=) of accepted keywords. + Define the list (=) of accepted keywords. This changes the default set + of keywords accepted by a user. + +keywordall [<email>] {+|-|=} <list of keywords> + + Accept (+) or refuse (-) mails classified under the given keyword(s). + Define the list (=) of accepted keywords. This changes the set of + accepted keywords of all the currently active subscriptions of a user. keyword <sourcepackage> [<email>] {+|-|=} <list of keywords> @@ -1425,6 +1443,12 @@ various commands to pts@qa.debian.org. the bot. +

+The pts-subscribe command-line utility (from the +devscripts package) can be handy to temporarily +subscribe to some packages, for example after having made an +non-maintainer upload. + Filtering PTS mails

Once you are subscribed to a package, you will get the mails sent to @@ -5097,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 -with a tool known as mia-history. By default, -mia-history shows information about every person it knows -about, but it accepts regular expressions as arguments which it uses to -match user names. mia-history --help shows which -arguments are accepted. If you find that no information has been recorded +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 already, or that you can add more information, you should generally proceed as follows.

@@ -5136,15 +5158,16 @@ about the maintainer in question as possible. This includes: non-Debian mailing lists or news groups.

-One big problem are packages which were sponsored — the maintainer is not +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 should know what +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;, asking if anyone is aware of the whereabouts of the missing maintainer. +Please Cc: the person in question.

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 @@ -5158,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 — 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!

On the other hand, although we are volunteers, we do have a responsibility. So you can stress the importance of the greater good — if a maintainer does not have the time or interest anymore, they should "let go" and give the package to 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;.