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.60) (envelope-from ) id 1GW84E-0004BZ-P6 for garchives@archives.gentoo.org; Sat, 07 Oct 2006 09:01:59 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9790wAY032689; Sat, 7 Oct 2006 09:00:58 GMT Received: from rutherford.zen.co.uk (rutherford.zen.co.uk [212.23.3.142]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k978wlEx003065 for ; Sat, 7 Oct 2006 08:58:47 GMT Received: from [62.3.120.141] (helo=spike) by rutherford.zen.co.uk with esmtp (Exim 4.50) id 1GW819-0006GW-38 for gentoo-dev@lists.gentoo.org; Sat, 07 Oct 2006 08:58:47 +0000 Date: Sat, 07 Oct 2006 09:58:46 +0100 From: Roy Bamford Subject: Re: [gentoo-dev] Gentoo World Domination. a 10 step guide To: gentoo-dev@lists.gentoo.org References: <20061004070014.843d851d.tcort@gentoo.org> <45239C82.2050502@gentoo.org> <1159972037.10543.28.camel@inertia.twi-31o2.org> <1160126645l.10360l.0l@spike> <1160177163.10578.70.camel@inertia.twi-31o2.org> In-Reply-To: <1160177163.10578.70.camel@inertia.twi-31o2.org> (from wolf31o2@gentoo.org on Sat Oct 7 00:26:03 2006) X-Mailer: Balsa 2.3.13 Message-Id: <1160211526l.10273l.0l@spike> 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: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed Content-Disposition: inline X-Originating-Rutherford-IP: [62.3.120.141] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k978wlEx003065 X-Archives-Salt: c2ec030a-ed5d-4d4e-adac-0676b4090b88 X-Archives-Hash: e7c49970bdb71748be57e130e52aec19 On 2006.10.07 00:26, Chris Gianelloni wrote: > On Fri, 2006-10-06 at 10:24 +0100, Roy Bamford wrote: > > Before you can have useful reports, you need a plan to report > against. > > Like a target date for 2007.0 and its contents. Such a plan depends > on > > other projects delivering the contents in accordance with their own > > > plans. Like real life, these plans will have external dependencies > on > > $UPSTREAM, that Gentoo has little or no control over. > > Please stop assuming that Release Engineering has any control over > what goes on in the tree. Not only do we not have any such control, > we also do not *want* any such control. > [snip] > I'll be honest, Release Engineering work is *very* stressful. My > primary goal as the lead is to try to come up with ways to make > working on a release easier for the guys doing the work. I don't see > how doing reporting improves their lives. After all, we put out four > "reports" a year, two releases, and two meetings between the releases > where we plan the next release. Anything more than that is wasteful. > > ;] > > -- > Chris Gianelloni > Release Engineering Strategic Lead > Alpha/AMD64/x86 Architecture Teams > Games Developer/Council Member/Foundation Trustee > Gentoo Foundation Chris, I understand you don't have any control over what goes on in the tree. In Gentoo, nobody outside of the individual projects does. My post was not intended as a crit of yourself or the Release Engineering team. I replied in your part of the thread because Release Engineering are the obvious users of the mooted plans and reports. As long as Gentoo is organised as an anarchy, which I have seen work well in other groups, then the status quo is fine. If Gentoo is to be organised as a single project, then some bureaucracy to oil the wheels is needed. In turn, that would mean setting up a management body of some sort (not Release Engineering) but that's a whole new thread. No replies to that here please. Either organisation can work providing the contributors want it to make it work but there will always be some dissenters discussing change (change != improvement). That's a healthy sign in any group. Regards, Roy Bamford (NeddySeagoon) -- gentoo-dev@gentoo.org mailing list