Hello, I haven't been able to attend a council meeting for a bit since it occurs at ~2:30 am my time, but for what it's worth:
On Mon, 2009-06-01 at 23:15 -0500, Doug Goldstein wrote: [...] > 1) Agenda Topics are posted to the appropriate mailing lists at a > MINIMUM 7 days prior to the meeting. (That means the agenda must be > formed by this Thursday). > 1a) Any changes to the agenda should be ACK'd by the council members > (off list via the council alias). Changes can not occur less than 48 > hours from the meeting. Subject to common-sense w.r.t. making exceptions (which I presume will be few and far-apart), ++. > 2) The #gentoo-council channel become moderated as we had discussed > several times in the past. > 2a) Topics will be brought up and people wishing to address the > council and the developer body at large should speak to the day's > appointed moderator. We can take turns or I can do it (maybe it'll > keep my head from banging against the keyboard as it has in the past > watching the various non-council members argue completely non-agenda > items back and forth). > 2b) Requests are made in tells and honored in turn. The moderator will > announce to the channel who wishes to speak and the order they are in > and will efficiently work through the list. If you can not remain on > topic, you will lose your voice. I thought the intention was to have this as the policy whenever things got out of hand. Am I wrong, or is it just that this not been enforced? I'm all for this as a discretionary measure. > 3) Once discussion on the topic has concluded, the council members > will vote on the actions requested by the developer body. That does > not mean it is time for council members to concoct an entirely new > plan by the seat of their pants... which leads me to the next topic. ++ > 4) Council members will now be expected to ACK the agenda on the > appropriate mailing lists at least 48 hours prior to the meeting. If > you can't, let the council know. You should be able to do this without > relying on your proxy, but your proxy may do this for you as well if > you have an extended away. > 4a) Failure to ACK the agenda will be noted on the meeting minutes. I don't really see this as being strictly necessary. If we find ourselves having to use this measure often, there's definitely something wrong with the system. > 4b) Council members will be expected to formulate their thoughts in > reply to the agenda items and to research the discussion they wish to > have on the mailing list PRIOR to the meeting and not fly by the seat > of their pants. ++ > 4c) "The first I heard of this and I need 4 weeks to research this." > or any variation of the quoted statement is no longer a valid > statement. The point of the meeting is to weigh and debate the items > before us now. Do your research PRIOR to the meeting, not during. I guess 4 (c) can be made - if enough members of the council require more time to grok the issue, then just postpone the item? At one of the earlier meetings that I had attended, the modus operandi was to allocate some amount of time to discussion of the topic, and then either (a) make a decision (if things are reasonably clear), (b) defer till the next meeting (if they're not) Keeping things time-bound might sound a bit overboard, but for the more contentious topics, it's a good way to make sure that you don't just end up running around in circles. -- Arun
signature.asc
Description: This is a digitally signed message part
