public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo-Status
Date: Mon, 21 Aug 2006 20:13:50 -0400	[thread overview]
Message-ID: <44EA4C3E.8000701@gentoo.org> (raw)
In-Reply-To: <20060822015159.2deb84f7@c1358217.kevquinn.com>

Kevin F. Quinn wrote:
> On Mon, 21 Aug 2006 18:56:11 -0400
> Alec Warner <antarus@gentoo.org> wrote:
> 
>> [...] So below we have 3 large far-reaching projects.
>>
>> Gentoo Quality Assurance Team
>> Gentoo Infrastructure Team
>> Gentoo Portage Team
>> Gentoo Foundation
>> Gentoo Council
>>
>> All 5 of these projects are active
> 
> it's growing ;)

Doh, I wrote the e-mail and then added 2 projects ;p
> 
>> [...]
>> I request that these teams present status reports bi-weekly (thats one
>> every two weeks).
> 
> I'm not aware of the issue that sparked this, but if regular reports are
> a solution, I suggest that rather than mandating a bi-weekly report,
> each of the relevant projects should propose a reporting schedule that
> is appropriate to them.
> 
> For example, the Council meets once a month, so a bi-weekly status
> update seems inappropriate (half the reports are likely to be empty,
> the other half a copy of the meeting minutes which we already get).
> Perhaps the Foundation would be happier with a regular three- or
> six-month update, with the occasional ad-hoc update as need arises.
> Whatever, the point is that each project knows best how often it
> ought to communicate stuff.
> 

The bi-weekly thing was just something I arbitrarily chose, and I agree
that it could be different per project.

However I myself don't mind empty reports.  If there is nothing to
report, then there is nothing to report *shrugs*.  For projects like
council and foundation, that is to be expected more often than not.

However if there is a pending issue I'd rather see "we are still waiting
on the lawyers" or "the guy who was supposed to setup the server got an
internship" or "there was a portage release last week so I've been
fixing bugs for two weeks instead of working on thing X".

It's a status report, it doesn't have to be lively, the point is to keep
developers and users informed of what is going on in these projects.

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-08-22  0:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21 22:56 [gentoo-dev] Gentoo-Status Alec Warner
2006-08-21 23:27 ` Seemant Kulleen
2006-08-22  0:12   ` Joshua Jackson
2006-08-21 23:51 ` Kevin F. Quinn
2006-08-22  0:13   ` Alec Warner [this message]
2006-08-22  0:06 ` Ciaran McCreesh
2006-08-22  0:21   ` Alec Warner
2006-08-22  0:27     ` Ciaran McCreesh
2006-08-22 13:20   ` Lance Albertson
2006-08-22 14:33     ` Simon Stelling
2006-08-22 14:40       ` Ciaran McCreesh
2006-08-22 14:45         ` Elfyn McBratney
2006-08-22 14:52           ` Ciaran McCreesh
2006-08-22 14:45       ` Lance Albertson
2006-08-22 15:10         ` Simon Stelling
2006-08-22 15:17           ` Lance Albertson
2006-08-23 17:18   ` Sune Kloppenborg Jeppesen
2006-08-22  6:09 ` Marius Mauch
2006-08-22 12:57   ` Alec Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44EA4C3E.8000701@gentoo.org \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox