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 1GVlyu-0007A4-SC for garchives@archives.gentoo.org; Fri, 06 Oct 2006 09:27:01 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k969Q6De004881; Fri, 6 Oct 2006 09:26:06 GMT Received: from heisenberg.zen.co.uk (heisenberg.zen.co.uk [212.23.3.141]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k969O6gI006961 for ; Fri, 6 Oct 2006 09:24:07 GMT Received: from [62.3.120.141] (helo=spike) by heisenberg.zen.co.uk with esmtp (Exim 4.50) id 1GVlw6-0004Cp-3k for gentoo-dev@lists.gentoo.org; Fri, 06 Oct 2006 09:24:06 +0000 Date: Fri, 06 Oct 2006 10:24:05 +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> In-Reply-To: <1159972037.10543.28.camel@inertia.twi-31o2.org> (from wolf31o2@gentoo.org on Wed Oct 4 15:27:17 2006) X-Mailer: Balsa 2.3.13 Message-Id: <1160126645l.10360l.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-Heisenberg-IP: [62.3.120.141] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k969O6gI006961 X-Archives-Salt: d287440e-24d3-439b-89c6-9dee0db76376 X-Archives-Hash: 568a7bb6f587afffa34d52ab0fe687d8 On 2006.10.04 15:27, Chris Gianelloni wrote: [snip] > > I'll give you Release Engineering's "status reports" for September, > October, and November: > > September: taking a well-deserved break > October: taking a well-deserved break > November: taking a well-deserved break > > How about other projects that rely on things like upstream's release > cycle? What about projects that just maintain ebuilds? > > Here's the games team's "status reports" for every month: > > "Fixed more bugs, added more packages, cleaned up some ebuilds." > > Now, perhaps what everyone would like, instead, would be status > reports > *where necessary* from certain projects? > > In fact, the council has been discussing asking a few projects about > the > status on some of their tasks. The main reason for this is for > communications purposes. Basically, we'd just get a "Hey, where are > you > at on $x?" response from the teams. > > I don't *want* to drown projects in bureaucracy and paperwork. I want > them to *accomplish* things, instead. > > -- > Chris Gianelloni > Release Engineering Strategic Lead > Alpha/AMD64/x86 Architecture Teams > Games Developer/Council Member/Foundation Trustee > Gentoo Foundation > 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. With progress reports against plans and updated plans, everyone can see whats happened, why some things haven't and what the fallback is, if one is required. The old saw, "If you don't have a plan, then plan to fail" remains true for volunteer projects as well as funded ones. The content and update rate of plans/reports can vary from project to project and it need not be onerous. Reporting can even be by exception, so to take your "well-deserved break" example, if it was in your plan, no report would be needed. Regards, Roy Bamford (NeddySeagoon) -- gentoo-dev@gentoo.org mailing list