From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FEDWp-0005U0-41 for garchives@archives.gentoo.org; Tue, 28 Feb 2006 22:41:11 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1SMdHE4024011; Tue, 28 Feb 2006 22:39:17 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1SMaDej020227 for ; Tue, 28 Feb 2006 22:36:13 GMT Received: from rl03 by smtp.gentoo.org with local (Exim 4.54) id 1FEDSd-00055M-0H for gentoo-dev@lists.gentoo.org; Tue, 28 Feb 2006 22:36:51 +0000 Date: Tue, 28 Feb 2006 22:36:50 +0000 From: Renat Lumpau To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] QA Team's role Message-ID: <20060228223650.GA20443@toucan.gentoo.org> References: <20060227213321.7ee405ec@snowdrop.home> <200602281539.43661.vapier@gentoo.org> <905929917.20060228220239@gentoo.org> <200602281631.37594.vapier@gentoo.org> <20060228215040.GL11818@toucan.gentoo.org> <4404CB49.2080402@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8" Content-Disposition: inline In-Reply-To: <4404CB49.2080402@gentoo.org> User-Agent: Mutt/1.5.11 X-Archives-Salt: bb8a9a5a-7c83-4dde-920b-c65c1db006b2 X-Archives-Hash: a3c160edb5b051234cb64c1c84ce4712 --ibTvN161/egqYuK8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 28, 2006 at 04:14:33PM -0600, Grant Goodyear wrote: > I think > it's fair to say that these QA checks will find problems ranging from > not-awful-but-annoying to could-break-your-system, but they are all bugs > that ought to be fixed eventually. Now, if you're currently working on > fixing a big problem and thus too busy to fix the little one, that's > perfectly reasonable, but to not fix a small bug because you know there > are larger bugs that aren't fixed just seems lazy. I agree completely. However, ciaranm seems to think that if we don't fix a whitespace issue immediately, we'll ignore the rest of his QA comments and = it's therefore not worth it to let us know about the bigger issues: in #gentoo-qa today: 18:39 <@ciaranm> pfff, if they won't fix whitespace, what're the chances of them fixing anything else? That's an odd position to take. > So, back to the big issue, are there any real complaints about the QA > team essentially formulating QA policy? Should new QA policies instead > follow the same rules as new global USE flags or eclasses--an e-mail to > -dev asking for comments first? Does QA trump, or does the maintainer > trump when it comes to disputes? Yes. Here's a quote from Halcy0n (with his permission): Don't mistake me not getting involved for approval. I am just not going = to get involved in every single dev->dev disagreement, and certainly not whe= n I do not have all of the facts. I wasn't aware that every team leader was accountable for how devs on their team behaved. This is not meant as a comment on Halcy0n's abilities as a team leader, as I understand he has attempted to manage the issue but "reasonable effort" has failed. So, my concern is: if the QA team can't manage its members effectively, sho= uld they be entrusted with tree-wide powers? --=20 Renat Lumpau all things web-apps C6A838DA 04AF B5EE 17CB 1000 DDA5 D3FC 1338 ADC2 C6A8 38DA America - land of the free* *Void where prohibited, restrictions apply. Cash value 1/100c. --ibTvN161/egqYuK8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEBNCCEzitwsaoONoRAp+yAJ0Yt7kmy9Am2oacQtyRekRmqBx5QQCdHhyz +sE1fsGLJAEyDniWG3Q24Tw= =fhtM -----END PGP SIGNATURE----- --ibTvN161/egqYuK8-- -- gentoo-dev@gentoo.org mailing list