Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-council
Navigation:
Lists: gentoo-council: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: Doug Goldstein <cardoe@g.o>
From: Ulrich Mueller <ulm@g.o>
Subject: Re: Jun 11th, 2009 Council Meeting Format
Date: Tue, 2 Jun 2009 23:15:49 +0200
>>>>> On Mon, 1 Jun 2009, Doug Goldstein wrote:

> We have all collectively failed the Gentoo Project since we have not
> been doing this for the past several weeks. I propose the following
> changes be instituted before the meeting and happen through the
> meeting:

> 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.

Ack.

> 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.

Ack for the rules, but I would leave the channel open. Keep moderation
as an option if people don't stick to the rules and if there's too
much noise.

> 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.

Ack, plus the addition proposed by Tobias.

> 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.

It's not clear to me for what you need the 48 hours here? It should be
enough if the final agenda is acknowledged before the meeting. Or make
it the meeting's first topic, as it is usual in other contexts.

I agree that they shouldn't be any last-minute changes to the agenda,
but that's covered by point 1a) above.

> 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.

Full ack.

Ulrich


References:
Jun 11th, 2009 Council Meeting Format
-- Doug Goldstein
Navigation:
Lists: gentoo-council: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [gentoo-dev] Jun 11th, 2009 Council Meeting Format
Next by thread:
Take two of the council summary for 28.05
Previous by date:
Re: [gentoo-dev] Jun 11th, 2009 Council Meeting Format
Next by date:
GLEP 54: _live or _scm?


Updated Jun 17, 2009

Summary: Archive of the gentoo-council mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.