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 1EvbY1-0005Zh-VG for garchives@archives.gentoo.org; Sun, 08 Jan 2006 14:29:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k08ESaxI011622; Sun, 8 Jan 2006 14:28:36 GMT Received: from mail.twi-31o2.org (66-191-187-123.dhcp.gnvl.sc.charter.com [66.191.187.123]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k08EPVGD016980 for ; Sun, 8 Jan 2006 14:25:31 GMT Received: from localhost (localhost [127.0.0.1]) by mail.twi-31o2.org (Postfix) with ESMTP id E8F54248022 for ; Sun, 8 Jan 2006 09:16:10 -0500 (EST) Received: from mail.twi-31o2.org ([127.0.0.1]) by localhost (gravity.twi-31o2.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32107-15 for ; Sun, 8 Jan 2006 09:16:08 -0500 (EST) Received: from [192.168.1.50] (unknown [192.168.1.50]) by mail.twi-31o2.org (Postfix) with ESMTP id E2FB2248021 for ; Sun, 8 Jan 2006 09:16:08 -0500 (EST) Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for January From: Chris Gianelloni To: gentoo-dev@lists.gentoo.org In-Reply-To: <200601081440.52311.carlo@gentoo.org> References: <200601011053.k01ArjOh019213@robin.gentoo.org> <200601080115.31137.carlo@gentoo.org> <200601081440.52311.carlo@gentoo.org> Content-Type: text/plain Date: Sun, 08 Jan 2006 09:25:43 -0500 Message-Id: <1136730344.30850.9.camel@inertia.twi-31o2.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 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at twi-31o2.org X-Archives-Salt: 5d15a24f-0055-4920-b76a-26546f2bad9a X-Archives-Hash: cf14d59122580d7837a0b7bb051d2eb0 On Sun, 2006-01-08 at 14:40 +0100, Carsten Lohrke wrote: > > If you feel so strongly about this, why not setup a "cleaning crew" > > project that goes around doing exactly this? > > Don't you think that it is pretty much barefaced to let a small group do the > dirty, boring and annoying work, while those who don't care a bit can > continue to do so?! Not really... We already have a QA project. Join it. If certain developers are constantly breaking QA, inform them. If they continue to do it after being warned, go to devrel. While the QA team can go and clean up some things, it should only really do so *once* and inform the developer. Otherwise, the developer might not honestly know that he is doing something incorrectly, or that anyone is even paying attention. Doing this allows for a cleanup of the tree, without putting restrictions arbitrarily on the entire developer pool. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux -- gentoo-dev@gentoo.org mailing list