1 |
Doug Goldstein wrote: |
2 |
> On Wed, Jul 1, 2009 at 9:33 PM, Ned Ludd<solar@g.o> wrote: |
3 |
>> Meetings will likely go back to one time per month and be +m with +v be |
4 |
>> handed out per request with open chat pre/post meetings. The reason for |
5 |
>> this is to keep the meetings on-track. I won't engage in endless |
6 |
>> discussions. Facts can be presented. They will be reviewed on merit, |
7 |
>> technical and social. |
8 |
> |
9 |
> Thank you again. I tried the +m/+v thing a year ago and received a few |
10 |
> pieces of hate e-mail from mostly non-developer people. |
11 |
|
12 |
Please do go to +m. I usually just read council summaries - when I've |
13 |
tried to read the actual logs it is a COMPLETE mess. |
14 |
|
15 |
In most organizational board-like bodies the board meeting is NOT the |
16 |
place to have open discussion on topics. The open discussion happens |
17 |
everywhere BUT the board meeting. It happens on the phone, on mailing |
18 |
lists, in newspapers, on TV, on talk radio, etc. During the board |
19 |
meeting people who want to make a statement can do so within a limited |
20 |
amount of time, and then the board casts its vote. 95% of the time the |
21 |
way the vote will go is known before the meeting happens. The meeting |
22 |
is just a formality. |
23 |
|
24 |
If there is to be a 300 line argument over proposal-A vs proposal-B, do |
25 |
it on the mailing lists, or on IRC. Council votes should be |
26 |
straightforward matters. |
27 |
|
28 |
If we want to have more interaction - how about this idea: Formal |
29 |
council meetings happen once per month, and they are the ONLY place |
30 |
votes take place. However, the council will try to meet more often for |
31 |
less formal discussion. +m/+v may be imposed at any time if there is a |
32 |
large turnout just to keep things somewhat orderly. Attendance is not |
33 |
mandatory for these meetings, but is encouraged. You could also |
34 |
schedule them at a variety of times - again, you're not missing any |
35 |
votes so if only 1/3rd of the council makes any particular meeting it |
36 |
isn't a big deal. |
37 |
|
38 |
As far as having two council members temporarily approve items goes - it |
39 |
isn't a bad thing to have in general, but it should really only be used |
40 |
in emergency situations. I'm not sure if we even need it - I suspect |
41 |
that groups like infra will "do the right thing" most of the time if |
42 |
there is an emergency (dev starts committing "rm -rf /*" scripts all |
43 |
over the portage tree - infra suspends cvs access first and finds devrel |
44 |
later). |
45 |
|
46 |
Maybe a quick way to assess developer opinions on issues would be forum |
47 |
polls? The votify system is potentially good as well, but I'm not sure |
48 |
how much work it requires on the part of infra to gather/tally the |
49 |
votes. We really don't need the full rigor of votify for most issues |
50 |
(though it probably should be used if there are true referendums on |
51 |
serious matters). And, of course, there is always the "measure the |
52 |
noise on the mailing list" approach, but I'm not a big fan of that |
53 |
(though I am a fan of lists in general). |