From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Cc: gentoo-dev-announce <gentoo-dev-announce@gentoo.org>
Subject: [gentoo-project] Council meeting: Tuesday 8th May 2012, 19:00 UTC
Date: Wed, 02 May 2012 02:02:54 +0000 [thread overview]
Message-ID: <4FA095CE.3070701@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello fellow developers and community,
the next council meeting will be on Tuesday 8th May 2012 at 19:00 UTC
[1] in the #gentoo-council channel on Freenode.
Proposed agenda:
1. Introduction and roll call (5 minutes)
2. EAPI specification in ebuilds [2] (20 minutes)
1. Vote on final PMS wording [3] (discussion [4])
2. Vote to change the status of GLEP55 [5]
3. Separate /usr partition vote of last meeting (20 minutes)
Following the vote about Gentoo supporting separate /usr
installations in the last meeting, the mls became active
about the meaning and consequences of such vote.
William made a direct request to the council to review the
vote [6].
4. Review of the council term (10 minutes)
Roy suggested [7] the council members do a review of their
mandate in the last meeting before the election.
5. Open floor
[1] - http://www.gentoo.org/proj/en/council/utctolocal.html?time=1900
[2] -
http://archives.gentoo.org/gentoo-project/msg_e6eafd6be25794ca503e0ac9d6968cd3.xml
[3] -
http://archives.gentoo.org/gentoo-pms/msg_3a441be5e49cc06689ecab00da461278.xml
[4] -
http://archives.gentoo.org/gentoo-pms/msg_ef7635aa655913f2386e64e385f5a6ae.xml
[5] - http://www.gentoo.org/proj/en/glep/glep-0055.html
[6] -
http://archives.gentoo.org/gentoo-project/msg_5a3e7a62abc3f6f529cbb18d85f2fbcf.xml
[7] -
http://archives.gentoo.org/gentoo-project/msg_0e09e374488d2393c6cf794e349dc614.xml
- --
Regards,
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPoJXOAAoJEC8ZTXQF1qEPDmQP/RwgLkq1VSOtGK/bE1jA8Gqq
Q0CYsNuO5wGNUb5faauNcobuJNqTmrruv4ChoXRs+zKMnBRztILVzPkUqG3m0KXN
+w6w8Hgi48L6MZBhpq9pj73ePYbWGIe9EWs1BOTM72T9t7pp9op4lAGhfLLsD4vH
KQdBU5WOfO2zMz8kU2aM9NkZb2JfnUprxyIsPrZ0JnLw4HMt8WY9jVkvyx9htbYI
k+DrHyV6M6suFW7SVEukCdxcmW/4LUBf29Ue8d9ZSIL/aWQvH4UjqzoER1BWKoHK
xzU3Oqx2+77piwaXuONjiSDxJNW4Qcwrhn0kvDc3pkA4IC2fTt2P0BJXFDH0kXka
ZGbBFjGdgpj1MkyPOg6LydywSaXNIoaZbw5GxzpnxGTexJ5uwGBUvLswiH6hVThe
+IQJQ8Ph7ynW/oRnfoQzSlstQNCr/vXrG5ix3+PZmS43vItHZa5uIsdjMZrHqTrx
yl6tTj/u2jNgBmDF3RKE7AK/huHa9WHDvKEVmoZRFjxNQ6HRUPHUV5hrmOb53dvZ
GV/17U9bUsonnDKGg9vzhfD+YfihDB2NzDKBEPd1kjzRzeRku9PzZlJLv3UANMti
ADHdsA5O5inXceR5CIzLHPnC/a5j8ym2a7OTIUFEI5JlVs+UsLZnon4LX4hCOZFl
BER2n1/IzSE/xp33i2LE
=TuSz
-----END PGP SIGNATURE-----
next reply other threads:[~2012-05-02 3:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 2:02 Jorge Manuel B. S. Vicetto [this message]
2012-05-04 23:06 ` [gentoo-project] Council meeting: Tuesday 8th May 2012, 19:00 UTC William Hubbs
2012-05-05 0:46 ` Mike Frysinger
2012-05-05 2:41 ` William Hubbs
2012-05-05 3:25 ` William Hubbs
2012-05-05 5:32 ` William Hubbs
2012-05-05 8:32 ` Fabian Groffen
2012-05-05 15:56 ` William Hubbs
2012-05-07 17:48 ` Donnie Berkholz
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=4FA095CE.3070701@gentoo.org \
--to=jmbsvicetto@gentoo.org \
--cc=gentoo-dev-announce@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