From: Tobias Scherbaum <dertobi123@gentoo.org>
To: gentoo-council@lists.gentoo.org, council@gentoo.org
Cc: gentoo-dev-announce@lists.gentoo.org
Subject: [gentoo-council] Agenda for September 14th meeting
Date: Sat, 12 Sep 2009 14:14:09 +0200 [thread overview]
Message-ID: <1252757649.6044.5.camel@homer.ob.libexec.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2345 bytes --]
Here's the agenda for our september 14th meeting (18 UTC), held on
#gentoo-council
1. Intro (10 minutes including late arrivals)
1.1. Make sure that at least a couple people are logging the meeting.
1.2. Roll call.
1.3. Any volunteers to chair this meeting?
2. 10 Years Gentoo (5 Minutes)
2.1. Update on LiveCD/DVD and other activities
3. EAPI/PMS (30 Minutes)
3.1. A process to modify PMS standard that doesn't directly involve
the EAPI process.
As requested by "Joshua Jackson" <tsunam@tsunam.org> / User relations:
Required people: tsuname, ulm
"Per bug http://bugs.gentoo.org/show_bug.cgi?id=273261 I'm requesting an
AOB for the decision that was made by the PMS team about a process or
system to modify the PMS standard that doesn't directly involve the EAPI
process currently.
I've set the hard date for them for the sept 10th meeting and this gives
them 3 weeks to work on this so it should be no issue for them to come
to this. I'm expecting them to be able to have a result by then."
3.2 EAPI / PMS comittee. If we do need/want one, vote on a structure:
Required people: ulm
3.2.1 Either we form a new committee / working group for EAPI and
PMS questions (more or less Calchan's proposal). I'd guess there
should be one or two members from the council, plus someone from
the PMS project, and a representative for each package manager.
3.2.2 In principle also the PMS project could play this role, but
with its current membership of only three devs it is too weak. So
some relevant people (see above) would have to join. OTOH, there's
already a bugzie alias (pms-bugs), a mailing list (gentoo-pms) and
an IRC channel set up.
3.2.3 Something (completely) different.
4. Establish a process to amend GLEP 39 (10 Minutes)
"discuss and initiate an all-developer vote on a process to amend
GLEP 39."
http://archives.gentoo.org/gentoo-dev-announce/msg_663d96f01e096234c601c01220126da3.xml
5. Next meeting (5 minutes)
5.1. When? (October 12th is 4 weeks ahead)
5.2. Who makes sure we have an agenda beforehand?
6. Wrap up, comments, open questions.
- Tobias
--
Praxisbuch Nagios
http://www.oreilly.de/catalog/pbnagiosger/
https://www.xing.com/profile/Tobias_Scherbaum
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-09-12 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-12 12:14 Tobias Scherbaum [this message]
2009-09-12 15:08 ` [gentoo-council] Agenda for September 14th meeting Ciaran McCreesh
2009-09-12 23:56 ` Jorge Manuel B. S. Vicetto
2009-09-13 0:05 ` Ciaran McCreesh
2009-09-13 0:16 ` Jorge Manuel B. S. Vicetto
2009-09-13 0:25 ` Jorge Manuel B. S. Vicetto
2009-09-12 16:45 ` Andrew D Kirch
2009-09-12 18:16 ` Ciaran McCreesh
2009-09-12 21:49 ` Andrew D Kirch
2009-09-12 21:58 ` Ciaran McCreesh
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=1252757649.6044.5.camel@homer.ob.libexec.de \
--to=dertobi123@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-council@lists.gentoo.org \
--cc=gentoo-dev-announce@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