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 1GVEaQ-0006Ew-Ap for garchives@archives.gentoo.org; Wed, 04 Oct 2006 21:47:30 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k94Lk1WO017241; Wed, 4 Oct 2006 21:46:01 GMT Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k94Lh6TY015032 for ; Wed, 4 Oct 2006 21:43:06 GMT Received: by nf-out-0910.google.com with SMTP id x30so621738nfb for ; Wed, 04 Oct 2006 14:43:06 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=QgEei1WwmqqBVZ6Fq/77Pqft0k67kKix0wVvFLkBPaxKc00zlB75tfYUot8bsWqcZaTYiNVV4VYAmTUnwouWaSbqM28++s2+P1/Gf4oJmr3KaS2b5QJovTsz+wyLo/bD++lsiLNOTE1tXyIbIbNELjd7tfYaIKkalHgbhL4JFu8= Received: by 10.49.8.15 with SMTP id l15mr2989404nfi; Wed, 04 Oct 2006 14:43:06 -0700 (PDT) Received: by 10.49.42.20 with HTTP; Wed, 4 Oct 2006 14:43:06 -0700 (PDT) Message-ID: Date: Wed, 4 Oct 2006 17:43:06 -0400 From: "Mike Pagano" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Gentoo World Domination. a 10 step guide In-Reply-To: <1159997107.10543.84.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 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061004070014.843d851d.tcort@gentoo.org> <45239C82.2050502@gentoo.org> <1159972037.10543.28.camel@inertia.twi-31o2.org> <4523F47F.2070502@gentoo.org> <452409B0.5060101@gentoo.org> <1159997107.10543.84.camel@inertia.twi-31o2.org> X-Archives-Salt: 963dc761-58ee-49c7-9d15-e0a98b445588 X-Archives-Hash: 216cf97d437e7d0a3b4f73ee9843ec64 On 10/4/06, Chris Gianelloni wrote: > On Wed, 2006-10-04 at 12:21 -0700, Donnie Berkholz wrote: > > Donnie Berkholz wrote: > > > Chris Gianelloni wrote: > > >> 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. > > > > > > I really like the concept of answering questions rather than giving > > > arbitrary reports. The problem is, sometimes nobody outside your project > > > knows the right questions to ask. > > > > I was thinking more about this. What if, instead of these periodic > > status reports, you just send out a note when something interesting > > happens? There's no point in holding it back till your monthly required > > report, and it saves the trouble of the report when nothing's happening. > > That's really a good idea. When I was writing, I was thinking more > along the lines of things like: > > What's the status of bugs getting updated? > What's the status of anonsvn/anoncvs? > What's the status of QA's policy document? > > These are things that either are interesting to a large number of > developers, and easier to answer once rather than 300 times, or things > the council itself has asked a group to do based on one of our > decisions. Of course, we could/would take ideas for things to ask, and > again, all we need really is something like this (mock) answer: > > "Well, we have all the hardware in place and have gotten access to the > systems. We've installed the OS and setup the main databases, but we're > still having some issues with the virtual IP scheme, and that's slowing > us down on getting this implemented." > > That's it. No long "report" or anything is necessary. Just a simple, > short few sentences on the current status is all that's really needed > for the long ongoing projects. For other things, like, xorg 7.1 going > stable or KDE 3.5.5 being unmasked, a simple announcement from the team > when it happens should really cover it. That isn't even necessary from > most projects, as they simply do maintenance tasks which don't really > need an announcement. > > -- > Chris Gianelloni > Release Engineering Strategic Lead > Alpha/AMD64/x86 Architecture Teams > Games Developer/Council Member/Foundation Trustee > Gentoo Foundation > > > How about something in the "planet" format that where each group reporting status could do so at their schedule when they feel an update is necessary or warrented. Then users could just read the website for the latest status updates. There are a few "hot" items many people are interested in such as kde or gnome stablization, for example. A simple line like "Don't expect KDE 5.0 to go stable before the end of the year" provides transparency and a bit of communication to the user community. -- gentoo-dev@gentoo.org mailing list