From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OrYkH-000343-Ky for garchives@archives.gentoo.org; Fri, 03 Sep 2010 16:04:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4E82AE0877 for ; Fri, 3 Sep 2010 16:04:05 +0000 (UTC) Received: from rookery.halcy0n.com (rookery.halcy0n.com [69.72.242.50]) by pigeon.gentoo.org (Postfix) with ESMTP id 824F1E06F3 for ; Fri, 3 Sep 2010 15:12:52 +0000 (UTC) Received: by rookery.halcy0n.com (Postfix, from userid 1000) id 1FE8AA5620; Fri, 3 Sep 2010 11:12:52 -0400 (EDT) Date: Fri, 3 Sep 2010 11:12:52 -0400 From: Mark Loeser To: gentoo-qa@lists.gentoo.org Subject: Re: [gentoo-qa] QA power to suspend access [WAS: Re: Roll-call for the team members and requesting a new election] Message-ID: <20100903151252.GE21473@halcy0n.com> References: <20100821181142.GA32624@halcy0n.com> <1282420055.445.54.camel@yamato.local> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-qa@lists.gentoo.org Reply-to: gentoo-qa@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+KJYzRxRHjYqLGl5" Content-Disposition: inline In-Reply-To: <1282420055.445.54.camel@yamato.local> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Archives-Salt: fc15699d-78ac-476b-bbf5-35c981e00087 X-Archives-Hash: 802966c0daf04010c9100c8368948208 --+KJYzRxRHjYqLGl5 Content-Type: text/plain; charset=utf8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Diego Elio =E2=80=9CFlameeyes=E2=80=9D Petten=C3=B2 s= aid: > Il giorno sab, 21/08/2010 alle 14.11 -0400, Mark Loeser ha scritto: > >=20 > > #2 seems to alleviate any bottlenecks that could happen. What does > > everyone else think? This can wait until after whatever is decided > > with > > the election, but the conversation should take place regardless.=20 >=20 > I agree that #2 sounds the best. >=20 > In case we all agree on that, should we ask devrel nicely to write that > down on their own policy or do we have to pass through council? Well, we seem to have an agreement from the majority here, of 2. I'll push this through the council at the next meeting since it was my assignment to bring the discussion up. The exact text that will be replace is: If a particular developer persistently causes breakage, the QA team may request that devrel re-evaluates that developer's commit rights. Evidence of past breakages will be presented with this request to devrel. It will now become: If a particular developer persistently causes breakage, the QA team can request infra to revoke the developer's commit rights, and will contact devrel to help mediate the case. The QA team can request that the commit rights be revoked either by the lead asking, or 2 members of the QA team requesting such an action be taken. Thanks, --=20 Mark Loeser email - halcy0n AT gentoo DOT org email - mark AT halcy0n DOT com web - http://www.halcy0n.com --+KJYzRxRHjYqLGl5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFMgRB0CRZPokWLroQRAm1xAJ492rkdJrQNOR45CVcH4HqQpkvAfQCgr1gc BZ7ckcdCV2+cGEIBWUONqmY= =QQUN -----END PGP SIGNATURE----- --+KJYzRxRHjYqLGl5--