1 |
Am Montag, den 01.06.2009, 23:15 -0500 schrieb Doug Goldstein: |
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 |
> "The elected Gentoo Council decides on global issues and policies that |
15 |
> affect multiple projects in Gentoo." |
16 |
> |
17 |
> We have all collectively failed the Gentoo Project since we have not |
18 |
> been doing this for the past several weeks. I propose the following |
19 |
> changes be instituted before the meeting and happen through the |
20 |
> meeting: |
21 |
> |
22 |
> 1) Agenda Topics are posted to the appropriate mailing lists at a |
23 |
> MINIMUM 7 days prior to the meeting. (That means the agenda must be |
24 |
> formed by this Thursday). |
25 |
ACK |
26 |
|
27 |
> 1a) Any changes to the agenda should be ACK'd by the council members |
28 |
> (off list via the council alias). Changes can not occur less than 48 |
29 |
> hours from the meeting. |
30 |
> 2) The #gentoo-council channel become moderated as we had discussed |
31 |
> several times in the past. |
32 |
While there were some meetings where this would really have been |
33 |
appropriate I don't think it should be a general rule. |
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 |
(mostly the discussions where between council and non-council members) |
42 |
|
43 |
> 2b) Requests are made in tells and honored in turn. The moderator will |
44 |
> announce to the channel who wishes to speak and the order they are in |
45 |
> and will efficiently work through the list. If you can not remain on |
46 |
> topic, you will lose your voice. |
47 |
I don't think that this way is appropriate since there should be as less |
48 |
boundaries as possible. And establishing an environment where people get |
49 |
received in audience (like with a king) can not be the way... |
50 |
|
51 |
> 3) Once discussion on the topic has concluded, the council members |
52 |
> will vote on the actions requested by the developer body. That does |
53 |
> not mean it is time for council members to concoct an entirely new |
54 |
> plan by the seat of their pants... which leads me to the next topic. |
55 |
The goal should be to get a common conclusion without having to vote. |
56 |
Voting should be a last resort measurement in case a decision is needed |
57 |
and people can't agree. |
58 |
|
59 |
> 4) Council members will now be expected to ACK the agenda on the |
60 |
> appropriate mailing lists at least 48 hours prior to the meeting. If |
61 |
> you can't, let the council know. You should be able to do this without |
62 |
> relying on your proxy, but your proxy may do this for you as well if |
63 |
> you have an extended away. |
64 |
If you want to reorganize how things work, please remove the concept of |
65 |
"proxies" completely and rather allow council members to miss in total 4 |
66 |
meetings with two of them without announcement. (numbers are examples) |
67 |
The reason is that proxies will never be as well prepared as council |
68 |
members (or as council members should be), etc. |
69 |
|
70 |
> 4a) Failure to ACK the agenda will be noted on the meeting minutes. |
71 |
Failure to ACK will be counted as missing a meeting since it has to be |
72 |
assumed that the given council member is unprepared. |
73 |
And, after all, being a council member doesn't only involve the presency |
74 |
at the meeting but also some sort of involvement or understanding of the |
75 |
topics. |
76 |
|
77 |
> 4b) Council members will be expected to formulate their thoughts in |
78 |
> reply to the agenda items and to research the discussion they wish to |
79 |
> have on the mailing list PRIOR to the meeting and not fly by the seat |
80 |
> of their pants. |
81 |
But there must still be some room for discussions. |
82 |
|
83 |
> 4c) "The first I heard of this and I need 4 weeks to research this." |
84 |
> or any variation of the quoted statement is no longer a valid |
85 |
> statement. The point of the meeting is to weigh and debate the items |
86 |
> before us now. Do your research PRIOR to the meeting, not during. |
87 |
Full ACK. |
88 |
|
89 |
> |
90 |
> I know this is a sharp pill to swallow and a firm deviation from the |
91 |
> past 2 or 3 months of council meetings but this is something the |
92 |
> council toyed with before and it was successful until we started to |
93 |
> let it slip to the situation we have today. |
94 |
> |
95 |
> I look forward to the current council members ack'ing this e-mail |
96 |
> (whether it be in parts or in whole) and I look forward to our Gentoo |
97 |
> developer body ack'ing this e-mail to show support that they want a |
98 |
> "goal oriented action taking" council and not a "delay and talk" |
99 |
> council. This council has only a few short weeks remaining and now is |
100 |
> the time to start reviewing candidates and seeing if they will do for |
101 |
> you in the coming year what you expect a council to do. |
102 |
> |
103 |
> If people like this, great. If people don't, then I can feel comforted |
104 |
> that I spoke my piece about what I want to see the council become and |
105 |
> people don't share the same vision as me. |
106 |
|
107 |
|
108 |
|
109 |
-- |
110 |
Tiziano Müller |
111 |
Gentoo Linux Developer, Council Member |
112 |
Areas of responsibility: |
113 |
Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor |
114 |
E-Mail : dev-zero@g.o |
115 |
GnuPG FP : F327 283A E769 2E36 18D5 4DE2 1B05 6A63 AE9C 1E30 |