From: Thomas Anderson <gentoofan23@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: [gentoo-council] Initial Council summary for 04.28's meeting
Date: Sun, 31 May 2009 07:54:22 -0400 [thread overview]
Message-ID: <20090531115422.GA27605@dodo.hsd1.nj.comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 142 bytes --]
Attached.
--
---------
Thomas Anderson
Gentoo Developer
/////////
Areas of responsibility:
AMD64, Secretary to the Gentoo Council
---------
[-- Attachment #2: councilsummary-20090528.txt --]
[-- Type: text/plain, Size: 3120 bytes --]
Roll Call:
===========
Betelgeuse: here
Cardoe: here
dertobi123: here
dev-zero: here
leio: here
lu_zero: here
tanderson(secretary): physically late, irc client logged everything
ulm: here
Topics:
===========
- Filling the empty council seat.
Donnie Berkholz resigned from the council so there is an empty spot
that needs to be filled. ssuominen and ulm were tied for the next
spot, but ssuominen relinquished his seat to ulm. To fill the spot,
ulm needed to be unanimusly voted in by the current members.
Conclusion:
Unanimously voted to fill the seat. Ulrich Mueller will fill Donnie
Berkholz's seat for the rest of the current term.
- EAPI 3 status report from Zac Medico.
No progress yet. Zac said he'd have a recent recruit of his work with
him on it.
Conclusion:
Zac will work on EAPI 3 features with the help of his recruit. He
will also blog about what features need to be done so the general
community can pitch in.
- Removal of Old Eclasses.
Jorge(jmbsvicetto) requested that the council discuss removing
eclasses from the tree that are no longer needed. The problem with
this is that old(<2.1.4) portage versions used the eclasses from the
tree to run uninstall phases. Thus, the removal of eclasses would
break users who have a portage older than 2.1.4.
Conclusion:
The council voted that to remove eclasses devs should take the
following steps:
1) Deprecate eclasses(warning)
2) Removal of all functionality relating to installing
3) After two years the eclass may be removed.
Thomas Anderson(tanderson) will write up patches for devmanual so
that this policy is documented.
- Handling EAPI Versioning in a forwards-compatible way.
Various developers have raised concerns that GLEP 55 only describes a
solution and doesn't clearly show the problems being solved(if any).
Luca(lu_zero) mentioned a few things in the "Problem" section that he
thought could be clarified, listed below:
1) For "Change the behaviour of inherit in any way", it would be
useful to include references to bugs where requested inherit
changes would require GLEP 55.
2) For "Add new global scope functions in any way", defining
'Sane'.
3) For "Extend versioning rules in an EAPI", removal of all
mentions of GLEP 54 would remove circularity. In addition,
mentioning other version format changes would be useful.
4) For "Use newer bash features", listing useful(including
in-tree) bash features not available in the bash version mandated
by PMS would be useful.
Conclusion:
The council voted on whether they recognized the problem that GLEP
55 is attempting to solve is real. The vote was unanimous in recognition
of the problem.
next reply other threads:[~2009-05-31 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-31 11:54 Thomas Anderson [this message]
2009-05-31 13:01 ` [gentoo-council] Initial Council summary for 04.28's meeting Ulrich Mueller
2009-06-01 7:13 ` Luca Barbato
2009-05-31 13:35 ` Petteri Räty
2009-06-01 3:14 ` Alec Warner
2009-06-01 3:50 ` Mike Frysinger
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=20090531115422.GA27605@dodo.hsd1.nj.comcast.net \
--to=gentoofan23@gentoo.org \
--cc=gentoo-council@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