From: Russ Allbery Date: Sat, 3 Jul 2010 19:58:37 +0000 (-0700) Subject: Clarify Maintainer, make Uploaders mandatory for team maintainers X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=4fc5c74d02a4e88c5aadf786fa980ae6f9575f1e;p=debian%2Fdebian-policy.git Clarify Maintainer, make Uploaders mandatory for team maintainers Clarify the duties of the maintainer and state that the maintainer's e-mail address must accept non-spam BTS mail and automated mail from the project software. Rephrase the package orphaning; this does not only happen when someone retires from the project. Require the Uploaders field for a team-maintained package and, in that case, require that it contains at least one human and personal address. --- diff --git a/policy.sgml b/policy.sgml index bad28af..1bc37b3 100644 --- a/policy.sgml +++ b/policy.sgml @@ -886,23 +886,38 @@ - + The maintainer of a package

- Every package must have a Debian maintainer (the - maintainer may be one person or a group of people - reachable from a common email address, such as a mailing - list). The maintainer is responsible for ensuring that - the package is placed in the appropriate distributions. -

- -

- The maintainer must be specified in the - Maintainer control field with their correct name - and a working email address. If one person maintains - several packages, they should try to avoid having - different forms of their name and email address in + Every package must have a Debian maintainer. The maintainer may + be one person or a group of people reachable from a common email + address, such as a mailing list. The maintainer is responsible + for maintaining the Debian packaging files, evaluating and + responding appropriately to reported bugs, uploading new + versions of the package, ensuring that the package is placed in + the appropriate archive area and included in Debian releases as + appropriate for the stability and utility of the package, and + requesting removal of the package from the Debian distribution + if it is no longer useful or maintainable. +

+ +

+ The maintainer must be specified in the Maintainer + control field with their correct name and a working email + address. The email address given in the Maintainer + control field must accept mail from those role accounts in + Debian used to send automated mails regarding the package. This + includes non-spam mail from the bug-tracking system, all mail + from the Debian archive maintenance software, and other role + accounts or automated processes that are commonly agreed on by + the project. + A sample implementation of such a whitelist written for the + Mailman mailing list management software is used for mailing + lists hosted by alioth.debian.org. + + If one person or team maintains several packages, they should + use the same form of their name and email address in the Maintainer fields of those packages.

@@ -912,15 +927,22 @@

- If the maintainer of a package quits from the Debian - project, "Debian QA Group" - packages@qa.debian.org takes over the - maintainer-ship of the package until someone else - volunteers for that task. These packages are called - orphaned packages. - The detailed procedure for doing this gracefully can - be found in the Debian Developer's Reference, - see . + If the maintainer of the package is a team of people with a + shared email address, the Uploaders control field must + be present and must contain at least one human with their + personal email address. See for the + syntax of that field. +

+ +

+ If the maintainer of a package no longer has time or desire to + maintain a package, it is orphaned. The maintainer then becomes + Debian QA Group <packages@qa.debian.org>. These + packages are considered maintained by the Debian project as a + whole until someone else volunteers to take over maintenance. + + The detailed procedure for doing this gracefully can be found + in the Debian Developer's Reference, see .

@@ -2698,20 +2720,32 @@ Package: libc6 putting the name in round brackets and moving it to the end, and bringing the email address forward).

+ +

+ See for additional requirements and + information about package maintainers. +

Uploaders

- List of the names and email addresses of co-maintainers of - the package, if any. If the package has other maintainers - beside the one named in the - Maintainer field, their names - and email addresses should be listed here. The format of each - entry is the same as that of the Maintainer field, and - multiple entries must be comma separated. This is an optional - field. + List of the names and email addresses of co-maintainers of the + package, if any. If the package has other maintainers beside + the one named in the Maintainer + field, their names and email addresses should be listed + here. The format of each entry is the same as that of the + Maintainer field, and multiple entries must be comma + separated. +

+ +

+ This is normally an optional field, but if + the Maintainer control field names a group of people + and a shared email address, the Uploaders field must + be present and must contain at least one human with their + personal email address.