public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org,  gentoo-project@lists.gentoo.org
Subject: [gentoo-dev-announce] Agenda for Council meeting 2012-03-13
Date: Wed, 07 Mar 2012 11:33:29 +0200	[thread overview]
Message-ID: <4F572B69.1070502@gentoo.org> (raw)

Hi everyone,
Sorry about sending the agenda late. I had a reminder but then didn't
remember to act on it.

So the agenda is as follows:

1. roll call (5 minutes)
2. initial timeline for EAPI 5 suggestions (20min)
3. utf8 as default locale [1] (30min)
 a) should we have one (15min)
 b) what profile exactly (15min)
4. open floor

The git timeline is not in council hands so it should be discussed in
gentoo-scm.

The meeting will be on #gentoo-council@freenode on 2012-03-13 20UTC.
Hope to see you there.

Regards,
Petteri

[1]
http://archives.gentoo.org/gentoo-dev/msg_2ffb7ea72e6209439600c371f6fc071d.xml



                 reply	other threads:[~2012-03-07 12:03 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=4F572B69.1070502@gentoo.org \
    --to=betelgeuse@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