From: Tim Harder <radhermit@gentoo.org>
To: gentoo-project@lists.gentoo.org, gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-dev-announce] council meeting 2015-03-10
Date: Tue, 10 Mar 2015 10:59:26 -0400 [thread overview]
Message-ID: <20150310145926.GA2105@oregano.analog.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
Hi all,
The council will meet at the usual time of 19:00 UTC in #gentoo-council.
Agenda summary (more in depth one here [1]):
1. Roll call (5 minutes)
2. Infra team staffing issues (10 minutes)
3. Reducing/removing stable tree for some potentially lagging arches (10 minutes)
4. Flagging packages that can be stabilized for all arches at the same time (10 minutes)
5. Combining various keyring related USE flag into one global (10 minutes)
6. Bugs assigned to Council (5 minutes)
7. Open floor (10 minutes)
[1] http://dev.gentoo.org/~radhermit/council/council_agenda_20150310.txt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
reply other threads:[~2015-03-10 15:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150310145926.GA2105@oregano.analog.com \
--to=radhermit@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-project@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