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 9 April 2013, *** 19:00 UTC ***
Date: Wed, 3 Apr 2013 00:13:04 +0200	[thread overview]
Message-ID: <20827.22512.428175.868629@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20817.55135.354752.397336@a1i15.kph.uni-mainz.de>

[-- Attachment #1: Type: text/plain, Size: 990 bytes --]

The next council meeting will be on Tuesday 9 April 2013 at 19:00 UTC
(note change of time! [1]) in the #gentoo-council channel on Freenode.


Proposed agenda:

1. Introduction and roll call (5 minutes)

2. Change to newer Bash version in ebuilds (15 minutes)

   Take an initial look, and possibly vote on switching to a newer
   Bash version (e.g. 4.2) for the next EAPI [2,3].

3. EAPI deprecation (10 minutes)

   Should we have stricter rules, in order to limit the number of
   EAPIs that are in active usage? [4]

4. Open bugs with council involvement (15 minutes)

     - Bug 457000 "Missing log and summary for 20090122 and 20090625
       council meetings"
     - Bug 464250 "Encourage developers to use the latest EAPI"

5. Open floor

Regards,
Ulrich


[1] http://www.gentoo.org/proj/en/council/utctolocal.html?time=1900
[2] http://article.gmane.org/gmane.linux.gentoo.project/2371
[3] https://bugs.gentoo.org/431340
[4] http://article.gmane.org/gmane.linux.gentoo.project/2377

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2013-04-02 22:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 17:14 [gentoo-dev-announce] Call for agenda items - Council meeting 2013-04-09 Ulrich Mueller
2013-04-02 22:13 ` Ulrich Mueller [this message]

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=20827.22512.428175.868629@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