1 |
>>>>> On Mon, 1 Jun 2009, Doug Goldstein wrote: |
2 |
|
3 |
> We have all collectively failed the Gentoo Project since we have not |
4 |
> been doing this for the past several weeks. I propose the following |
5 |
> changes be instituted before the meeting and happen through the |
6 |
> meeting: |
7 |
|
8 |
> 1) Agenda Topics are posted to the appropriate mailing lists at a |
9 |
> MINIMUM 7 days prior to the meeting. (That means the agenda must be |
10 |
> formed by this Thursday). |
11 |
> 1a) Any changes to the agenda should be ACK'd by the council members |
12 |
> (off list via the council alias). Changes can not occur less than 48 |
13 |
> hours from the meeting. |
14 |
|
15 |
Ack. |
16 |
|
17 |
> 2) The #gentoo-council channel become moderated as we had discussed |
18 |
> several times in the past. |
19 |
> 2a) Topics will be brought up and people wishing to address the |
20 |
> council and the developer body at large should speak to the day's |
21 |
> appointed moderator. We can take turns or I can do it (maybe it'll |
22 |
> keep my head from banging against the keyboard as it has in the past |
23 |
> watching the various non-council members argue completely non-agenda |
24 |
> items back and forth). |
25 |
> 2b) Requests are made in tells and honored in turn. The moderator will |
26 |
> announce to the channel who wishes to speak and the order they are in |
27 |
> and will efficiently work through the list. If you can not remain on |
28 |
> topic, you will lose your voice. |
29 |
|
30 |
Ack for the rules, but I would leave the channel open. Keep moderation |
31 |
as an option if people don't stick to the rules and if there's too |
32 |
much noise. |
33 |
|
34 |
> 3) Once discussion on the topic has concluded, the council members |
35 |
> will vote on the actions requested by the developer body. That does |
36 |
> not mean it is time for council members to concoct an entirely new |
37 |
> plan by the seat of their pants... which leads me to the next topic. |
38 |
|
39 |
Ack, plus the addition proposed by Tobias. |
40 |
|
41 |
> 4) Council members will now be expected to ACK the agenda on the |
42 |
> appropriate mailing lists at least 48 hours prior to the meeting. If |
43 |
> you can't, let the council know. You should be able to do this without |
44 |
> relying on your proxy, but your proxy may do this for you as well if |
45 |
> you have an extended away. |
46 |
> 4a) Failure to ACK the agenda will be noted on the meeting minutes. |
47 |
|
48 |
It's not clear to me for what you need the 48 hours here? It should be |
49 |
enough if the final agenda is acknowledged before the meeting. Or make |
50 |
it the meeting's first topic, as it is usual in other contexts. |
51 |
|
52 |
I agree that they shouldn't be any last-minute changes to the agenda, |
53 |
but that's covered by point 1a) above. |
54 |
|
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 |
Full ack. |
65 |
|
66 |
Ulrich |