Proposal - obvious wording bugfix amendment to Debian Maintainers GR Proposal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I propose the wording changes in the diff below and request seconds.
I have tried to include only wording bugfixes. In particular, this
does not remove jetring maintainers from section 1, change section 3's
conditions or remove section 4's advice.
These changes were previously suggested with the others in
http://lists.debian.org/debian-vote/2007/06/msg00073.html
and there was no objection. Recently, Kalle Kivimaa suggested these
should be proposed as a formal amendment in
http://lists.debian.org/debian-vote/2007/06/msg00192.html
==== Wording bugfix proposal ====
- --- dmpgr.txt.orig 2007-06-27 11:44:56.000000000 +0100
+++ dmpgr.txt 2007-06-27 12:04:42.000000000 +0100
@@ -1,50 +1,50 @@
==== Debian Maintainers Proposal ====
The Debian Project endorses the concept of "Debian Maintainers" with
- -limited access, and resolves to
+limited access, and resolves
1) A new keyring will be created, called the "Debian maintainers keyring".
- - It will be initially maintained in alioth subversion using the jetring
- - tool, with commit priveleges initially assigned to:
+ It will initially be maintained in alioth subversion using the jetring
+ tool, with commit privileges assigned to:
* the Debian Account Managers (Joerg Jaspert, James Troup)
* the New-maintainer Front Desk (Christoph Berg, Marc Brockschmidt,
Brian Nelson)
* the FTP masters (James Troup, Ryan Murray, Anthony Towns)
* the Debian Keyring maintenaners (James Troup, Michael Beattie)
* the Jetring developers (Joey Hess, Anthony Towns, Christoph Berg)
The team will be known as the Debian Maintainer Keyring team. Changes
to the team may be made by the DPL under the normal rules for
delegations.
- - The keyring will be packaged for Debian, and regularly uploaded
+ The keyring will be packaged for Debian and uploaded
to unstable.
2) The initial policy for an individual to be included in the keyring
will be:
- - * that the applicant acknowledges Debian's social contract,
- - free software guidelines, and machine usage policies.
+ * that the applicant accepts Debian's social contract
+ and machine usage policies.
* that the applicant provides a valid gpg key, signed by a
Debian developer (and preferably connected to the web of
trust by multiple paths).
- - * that at least one Debian developer (preferable more) is willing
- - to advocate for the applicant's inclusion, in particular to the
- - fact that the applicant is technically competent and good to work
+ * that at least one Debian developer (preferably more) is willing
+ to advocate the applicant's inclusion, in particular
+ that the applicant is technically competent and good to work
with.
All additions to the keyring will be publicly announced to the
debian-project list.
- -3) The initial policy for removals for the keyring will be under any of the
+3) The initial policy for removals for the keyring will be to remove a maintainer in the
following circumstances:
* the individual has become a Debian developer
* the individual has not annually reconfirmed their interest
- - * multiple Debian developers have requested the individual's
+ * multiple Debian developers have requested
removal for non-spurious reasons; eg, due to problematic
uploads, unfixed bugs, or being unreasonably difficult to
work with.
@@ -54,7 +54,7 @@
4) The initial policy for Debian developers who wish to advocate
a potential Debian maintainer will be:
- - * Developers should take care in who they choose to advocate,
+ * Developers should take care about who they choose to advocate,
particularly if they have not successfully participated as an
Application Manager, or in other mentoring roles. Advocacy should
only come after seeing the individual working effectively within
@@ -78,13 +78,13 @@
* none of the uploaded packages are NEW
* the Maintainer: field of the uploaded .changes file matches the
- - key used (ie, maintainers may not sponsor uploads)
+ key used
* none of the packages are being taken over from other source packages
* the most recent version of the package uploaded to unstable
or experimental lists the uploader in the Maintainer: or Uploaders:
- - fields (ie, cannot NMU or hijack packages)
+ fields
* the usual checks applied to uploads from Debian developers pass
==== Wording bugfix proposal ====
Seconds or comments appreciated.
- --
MJR/slef
My Opinion Only: see http://people.debian.org/~mjr/
Please follow http://www.uk.debian.org/MailingLists/#codeofconduct
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGgkTTmUY5euFC5vQRAgB/AJ0fg2w47V53fRdYttgb2Ffp9hUsxgCeNj6G
6Vha66KpjKRe7mn8ztVaWUk=
=EvxI
-----END PGP SIGNATURE-----
Reply to: