Gentoo Archives: gentoo-qa

From: "Tomáš Chvátal" <scarabeus@g.o>
To: gentoo-qa@l.g.o
Subject: Re: [gentoo-qa] Proposed changes to GLEP48
Date: Sun, 23 Jan 2011 12:06:17
Message-Id: 4D3C1882.7070203@gentoo.org
In Reply to: [gentoo-qa] Proposed changes to GLEP48 by "Diego Elio Pettenò"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dne 22.1.2011 22:07, Diego Elio Pettenò napsal(a):
> Hi all, > > since we've been having a bit of a scratch again regarding the extension > of details defined by GLEP48, I'm trying to edit it a bit to make it > work a bit more smoothly for our needs. > > I'm attaching the diff I'd like to propose the council; please let me > know your comments. > > Thanks,
"The QA team lead can choose one member as deputy, whose decisions should be considered as they were made by the lead in case he (or she) is not available." "The QA team lead can choose one member as deputy. Deputy has all his powers directly delegated from the QA team lead and so his actions and decisions should be considered equal the QA team lead. Deputy is directly responsible only to the QA team lead." NEW: "Any QA team lead decision can be rewoked by major opposing vote from all current QA members. Given the nature of this action new elections should be held within 1 month to elect new QA team lead." "In case a particular developer persistently causes breakage, the QA lead may request his (or her) commit rights to be suspended. Devrel should then proceed to evalute the situation, by finding a compromise or definitely revoking those rights." "In case a particular developer persistently causes breakage, the QA lead may request commit rights of given developer to be suspended by Infra team. Devrel should then proceed to evaluate the situation, by finding a compromise or definitely revoking those rights." Reworded a bit: "Should a situation arise where a developer causes breakage to the point it cannot be ascribed to bona-fide mistake, either the QA lead or two members of the QA team can require the Infra team to temporarily suspend access to said developer, pending analysis of the causes and resolution to be provided by QA team within a 14 days of said suspension. Resolution for this kind of issues is completely in hands of the QA team and only the Gentoo Council can revisit the case." Cheers Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk08GIIACgkQHB6c3gNBRYfw1QCdERvoGS321L4VuD4dYJEQxDUk ewIAnjUQShytmgZEsI+01xIXn60gnm9N =CzxW -----END PGP SIGNATURE-----