From: Ciaran McCreesh <ciaran.mccreesh@blueyonder.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo-Status
Date: Tue, 22 Aug 2006 01:06:12 +0100 [thread overview]
Message-ID: <20060822010612.00243cae@snowdrop.home> (raw)
In-Reply-To: <44EA3A0B.7000401@gentoo.org>
On Mon, 21 Aug 2006 18:56:11 -0400 Alec Warner <antarus@gentoo.org>
wrote:
| I request that these teams present status reports bi-weekly (thats one
| every two weeks). You don't even have to write the reports, I will
| volunteer to bug you every two weeks about what is going on in your
| project and you can just drop a few words. I will author the report
| for you and post it to dev (if you wish for me to do so).
Bringing up something I proposed previously... How about having teams
that are considered 'important' (not a fixed list; this can vary
depending upon what's going on) or 'to be having issues' deliver status
reports to the council for their monthly meeting?
--
Ciaran McCreesh
Mail : ciaran dot mccreesh at blueyonder.co.uk
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-08-22 0:08 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
2006-08-22 0:06 ` Ciaran McCreesh [this message]
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=20060822010612.00243cae@snowdrop.home \
--to=ciaran.mccreesh@blueyonder.co.uk \
--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