Gentoo Archives: gentoo-council

From: "Petteri Räty" <betelgeuse@g.o>
To: gentoo-dev@l.g.o
Cc: gentoo-council@l.g.o
Subject: [gentoo-council] Re: [gentoo-dev] Jun 11th, 2009 Council Meeting Format
Date: Tue, 02 Jun 2009 19:00:09
Message-Id: 4A257699.4040808@gentoo.org
In Reply to: [gentoo-council] Jun 11th, 2009 Council Meeting Format by Doug Goldstein
1 Doug Goldstein wrote:
2 > All,
3 >
4 > The current council meetings have gotten completely out of hand for
5 > weeks meetings have become nothing more then a continuation of the
6 > senseless bicker-fest that have become the e-mail threads on GLEP54,
7 > GLEP55, and EAPI-3 without any real progress or sense coming of them.
8 > It's taken me a little bit to step up and put a stop to it but I fully
9 > intend on putting a stop to it. The point of the council meetings is
10 > to bring up a topic and decide on its merits whether it should be
11 > brought into the Gentoo Project or not. I quote from the first line of
12 > the Gentoo Council website:
13 >
14
15 Well EAPI-3 not progressing is due to lack of people implementing features.
16
17 >
18 > 1) Agenda Topics are posted to the appropriate mailing lists at a
19 > MINIMUM 7 days prior to the meeting. (That means the agenda must be
20 > formed by this Thursday).
21
22 ack
23
24 > 1a) Any changes to the agenda should be ACK'd by the council members
25 > (off list via the council alias). Changes can not occur less than 48
26 > hours from the meeting.
27
28 ack
29
30 > 2) The #gentoo-council channel become moderated as we had discussed
31 > several times in the past.
32
33 We can use this if we can't control the discussion otherwise.
34
35 > 2a) Topics will be brought up and people wishing to address the
36 > council and the developer body at large should speak to the day's
37 > appointed moderator. We can take turns or I can do it (maybe it'll
38 > keep my head from banging against the keyboard as it has in the past
39 > watching the various non-council members argue completely non-agenda
40 > items back and forth).
41 > 2b) Requests are made in tells and honored in turn. The moderator will
42 > announce to the channel who wishes to speak and the order they are in
43 > and will efficiently work through the list. If you can not remain on
44 > topic, you will lose your voice.
45 > 3) Once discussion on the topic has concluded, the council members
46 > will vote on the actions requested by the developer body. That does
47 > not mean it is time for council members to concoct an entirely new
48 > plan by the seat of their pants... which leads me to the next topic.
49 > 4) Council members will now be expected to ACK the agenda on the
50 > appropriate mailing lists at least 48 hours prior to the meeting. If
51 > you can't, let the council know. You should be able to do this without
52 > relying on your proxy, but your proxy may do this for you as well if
53 > you have an extended away.
54 > 4a) Failure to ACK the agenda will be noted on the meeting minutes.
55 > 4b) Council members will be expected to formulate their thoughts in
56 > reply to the agenda items and to research the discussion they wish to
57 > have on the mailing list PRIOR to the meeting and not fly by the seat
58 > of their pants.
59 > 4c) "The first I heard of this and I need 4 weeks to research this."
60 > or any variation of the quoted statement is no longer a valid
61 > statement. The point of the meeting is to weigh and debate the items
62 > before us now. Do your research PRIOR to the meeting, not during.
63
64 ok
65
66 Regards,
67 Petteri
68
69 PS. Let's try to keep threads on a single mailing list.

Attachments

File name MIME type
signature.asc application/pgp-signature