[gentoo-dev-announce] Council meeting: Tuesday 14 August 2012, 19:00 UTC

[gentoo-dev-announce] Council meeting: Tuesday 14 August 2012, 19:00 UTC

[Fabian Groffen]

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

The next council meeting will be on Tuesday 14 August 2012 at 19:00
UTC [1] in the #gentoo-council channel on Freenode.

Proposed agenda:

1. Intro / Roll call (5 minutes)

2. EAPI5 features (10 minutes)
   (no link, archives is not up-to-date, gmane misses the mail, marc
   doesn't have gentoo-project, mail by ulm in reply to dilfridge on 21st
   of July)
   * vote on the tentative list of EAPI 5 features
     (ulm: please provide said list)

3. Open bugs with Council involvement (0 minutes)
   * There are currently no open Council bugs

4. Open floor (10 minutes)


[1] http://www.gentoo.org/proj/en/council/utctolocal.html?time=1900


-- 
Fabian Groffen
Gentoo on a different level

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

[gentoo-dev-announce] Council meeting summary: Tuesday 14 August 2012, 19:00 UTC

[Fabian Groffen]

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

Apologies for sending the summary this late.


Summary of Gentoo council meeting 14th August 2012

Roll call
=========
betelgeuse
chainsaw
grobian
scarabeus
ulm
williamh

absent
------
dberkholz (receives slacker mark)


EAPI5 features
==============
Due to holidays, the list of features for EAPI5 was announced only 2
days in advance of the meeting.  This gave little time for Council
members to prepare for votes.
Therefore a vote was conducted if voting on EAPI5 features in this
meeting was deemed suitable.

The Council voted unanimously to postpone voting on EAPI5 features.

The list of features for EAPI5 were outlined by ulm in
http://thread.gmane.org/gmane.linux.gentoo.project/2101/focus=2115
Since many of these features appear not to be implemented in Portage, a
discussion on their implementation is called for by the Council.  The
Council stressed that it prefers to vote on EAPI5 features that can and
will be implemented within a short timeframe, say 1 month.


Open bugs with Council involvement
==================================
There are currently no open bugs.


Open floor
==========
scarabeus suggested the change "dev should use latest eapi when bumping"
to "dev must use latest eapi when bumping if not forbidden by eclasses".
He was asked to bring it up on the mailing lists, to get a better
definition of when what EAPI should be used.

ulm raised deprecation of EAPI 1 on request of patrick.  Arfrever argued
that backwards compatability is not an issue here, and that it can
greatly reduce code size/maintenance of eclasses when EAPI0 and EAPI1
are removed.  It was questioned whether removal of an EAPI really brings
that much benefits.  It seems eclasses can drop support for EAPIs, if
all consumers don't use them, which does not require complete removal of
the EAPI.  It appears some packages use build-systems that require
EAPI1.


Next meeting date
=================
11 September 2012, 19:00 UTC


-- 
Fabian Groffen
Gentoo on a different level

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