public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Gentoo Council Reminder for June 11
Date: Fri, 05 Jun 2009 00:26:02 +0200	[thread overview]
Message-ID: <1244154362.11496.172.camel@localhost> (raw)

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

This is your friendly reminder! Same bat time (typically the 2nd & 4th
Thursdays at 2000 UTC / 1600 EST), same bat channel (#gentoo-council @
irc.freenode.net) !

If you have something you'd wish for us to chat about, maybe even vote
on, let us know! Simply reply to this e-mail for the whole Gentoo dev
list to see.

For more info on the Gentoo Council, feel free to browse our homepage:
http://www.gentoo.org/proj/en/council/


Following is the preliminary meeting agenda.


EAPI 3: Short discussion of the progress
----------------------------------------

zmedico will provide an update on the progress of the implementation. Short
discussion of problems and implementation decisions if needed.


Default ACCEPT_LICENSE
----------------------
Goal: A possible default value for ACCEPT_LICENSE has been proposed. Decide
whether that's ok. What happens to the X11 license files (one for each app)?


Bash-4 in EAPI-3
----------------
Goal: A request has been made to allow bash-4.0 features in EAPI-3. Decide
first whether or not to open the EAPI-3 feature list at all.


Define EAPI development/deployment cycles
-----------------------------------------

Goal: Start discussion about EAPI development/deployment. For example:
Collect problems of eapi introductions in the past, like reverting
ebuilds to former eapis to get them stable, not waiting for the pm
support a certain eapi before requesting stable keywords for ebuilds
using the new eapi, .... Collect problems of EAPI development like
feature-freeze, late feature removals (due to implementation problems).
Eventually develop a lightweight EAPI development model.



Cheers,
Tiziano

-- 
Tiziano Müller
Gentoo Linux Developer, Council Member
Areas of responsibility:
  Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor
E-Mail   : dev-zero@gentoo.org
GnuPG FP : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30
-- 
Tiziano Müller
Gentoo Linux Developer, Council Member
Areas of responsibility:
  Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor
E-Mail   : dev-zero@gentoo.org
GnuPG FP : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2009-06-04 22:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04 22:26 Tiziano Müller [this message]
2009-06-05  7:35 ` [gentoo-dev] Gentoo Council Reminder for June 11 Nirbheek Chauhan
2009-06-05  8:17   ` Rémi Cardona
2009-06-05 17:14     ` Nirbheek Chauhan
2009-06-10  2:00 ` Doug Goldstein
2009-06-10 16:10   ` Tiziano Müller
2009-06-10 16:17   ` Ciaran McCreesh
2009-06-10 20:58   ` Ulrich Mueller
2009-06-10 21:21 ` Tobias Scherbaum
2009-06-10 22:08   ` Ciaran McCreesh
2009-06-10 22:26     ` Tobias Scherbaum
2009-06-11  6:31       ` [gentoo-dev] " Duncan
2009-06-10 22:14   ` [gentoo-dev] " Roy Bamford
2009-06-10 22:37     ` Tobias Scherbaum
2009-06-10 22:44       ` Ciaran McCreesh
2009-06-11  6:39         ` [gentoo-dev] " Duncan

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=1244154362.11496.172.camel@localhost \
    --to=dev-zero@gentoo.org \
    --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