public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org, gentoo-project@lists.gentoo.org
Subject: [gentoo-dev-announce] Council meeting: Tuesday 11 September 2012, 19:00 UTC
Date: Tue, 4 Sep 2012 12:16:04 +0200	[thread overview]
Message-ID: <20549.54500.967226.363097@a1i15.kph.uni-mainz.de> (raw)

The next council meeting will be on Tuesday 11 September 2012
at 19:00 UTC in the #gentoo-council channel on Freenode.

Proposed agenda:

1. Introduction and roll call (5 minutes)

2. EAPI 5 features (40 minutes)
   A detailed list of proposed features will be sent in a separate
   message to the gentoo-project mailing list.

     - Vote on the list of EAPI 5 features

3. Open bugs with council involvement (5 minutes)

     - Bug 383467 "Council webpage lacks results for 2010 and 2011
       elections"

4. Open floor (10 minutes)

Regards,
Ulrich


                 reply	other threads:[~2012-09-04 18:04 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=20549.54500.967226.363097@a1i15.kph.uni-mainz.de \
    --to=ulm@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