Re: [gentoo-dev] Gentoo Council Reminder for May 14

[Tiziano Müller]

Updated meeting agenda can be found here:

http://dev.gentoo.org/~dev-zero/council/meeting-agenda-20090514.txt

Changes:
- Added the issue of removing old eclasses to the list.

Cheers,
Tiziano

Am Sonntag, den 03.05.2009, 23:47 +0200 schrieb Tiziano Müller:
> 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. It consists of two EAPI-3
> related topics as well as two almost rusty topics where we should
> finally make a decision to be able to move on.
>
>
> 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.
>
>
> EAPI 3: PMS approval
> --------------------
>
> Goal: Approve EAPI-3 extension of the PMS. Any open questions should be
> on the mailing list before the meeting.
>
>
> GLEP 54: Dealing with live SCM packages
> ---------------------------------------
>
> Goal: Since no consensus is reached or progress has been made voting
> seems appropriate.
>
>
> Handling EAPI versioning in a forwards-compatible way
> -----------------------------------------------------
>
> Goal: Since no consensus is reached vote on the implementation for the
> problem solved in GLEP 55.
>
>
> Handling static libraries more flexibly
> ---------------------------------------
>
> Goal: Decision-making by consensus.
> Should we move forward with USE=static-libs to control
> building of static libraries? Should/Must this be an EAPI feature?
>
>
> 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@g.o
GnuPG FP : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30