From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MBWUF-00015j-Nw for garchives@archives.gentoo.org; Tue, 02 Jun 2009 16:05:15 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 28886E0324; Tue, 2 Jun 2009 16:05:14 +0000 (UTC) Received: from mail.libexec.de (omega.libexec.de [85.214.68.240]) by pigeon.gentoo.org (Postfix) with ESMTP id BACEFE0324; Tue, 2 Jun 2009 16:05:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.libexec.de (Postfix) with ESMTP id AA914400E; Tue, 2 Jun 2009 18:05:12 +0200 (CEST) X-Virus-Scanned: amavisd-new at libexec.de Received: from mail.libexec.de ([127.0.0.1]) by localhost (omega.libexec.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m2lDFmydjeqD; Tue, 2 Jun 2009 18:05:09 +0200 (CEST) Received: from [192.168.0.60] (dslb-084-063-198-245.pools.arcor-ip.net [84.63.198.245]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: tobias) by mail.libexec.de (Postfix) with ESMTPSA id 258253FF5; Tue, 2 Jun 2009 18:05:09 +0200 (CEST) Subject: [gentoo-council] Re: [gentoo-dev] Jun 11th, 2009 Council Meeting Format From: Tobias Scherbaum To: gentoo-dev@lists.gentoo.org Cc: gentoo-council@lists.gentoo.org In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-oaSEUViBW9vckauDa7y5" Date: Tue, 02 Jun 2009 18:05:08 +0200 Message-Id: <1243958708.6227.13.camel@homer.ob.libexec.de> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-council@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.24.5 X-Archives-Salt: 03b14c46-f6c0-45ce-a9ea-3ae6fed5ed7c X-Archives-Hash: cd1871f53ca9c8d18b7004384c607c2b --=-oaSEUViBW9vckauDa7y5 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Heya, thanks for bringing this up! Doug Goldstein wrote: > All, >=20 > The current council meetings have gotten completely out of hand for > weeks meetings have become nothing more then a continuation of the > senseless bicker-fest that have become the e-mail threads on GLEP54, > GLEP55, and EAPI-3 without any real progress or sense coming of them. > It's taken me a little bit to step up and put a stop to it but I fully > intend on putting a stop to it. Remove EAPI-3 from that list (as we got that off our desk for now, but the whole process could've been much easier, yeah ...), but in general: the neverending GLEP54/55 stuff isn't fun and i don't see us getting any further on that anytime soon. > 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. The "experiment" do keep meetings unmoderated was quite successful in the beginning nearly a year ago, i'd like to get back to the beginn of our experiment instead of just +m. If it proves not to work ... well we still have +m. > 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. See above, looks good to me and would help in making meetings more productive, just marking the channel +m is something we can do if "real" moderation doesn't work.=20 > 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. Add: Things to vote upon must be clear and precise worded. Discussing for half an hour of what's been voted upon and changing votes for several times is a huge waste of time (like we had 2 1/2 weeks ago). > 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. > 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. ... and ack. wkr, Tobias --=-oaSEUViBW9vckauDa7y5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEABECAAYFAkolTbQACgkQX2bdwDDA8AU9cQCfUMQDPChPVOzx+VIBfz7I29Rj PE4AnA3XYICgJ6So1P9JxfQtMBSKyBTN =vTXp -----END PGP SIGNATURE----- --=-oaSEUViBW9vckauDa7y5--