From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1K6YKx-0004Yl-GF for garchives@archives.gentoo.org; Wed, 11 Jun 2008 21:58:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C06F1E06F7; Wed, 11 Jun 2008 21:58:33 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 828E1E06F7 for ; Wed, 11 Jun 2008 21:58:33 +0000 (UTC) Received: from gentoo.org (c-71-193-142-160.hsd1.or.comcast.net [71.193.142.160]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id C032067433 for ; Wed, 11 Jun 2008 21:58:32 +0000 (UTC) Date: Wed, 11 Jun 2008 14:58:27 -0700 From: Donnie Berkholz To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Agenda [WAS: One-Day Gentoo Council Reminder for June] Message-ID: <20080611215827.GB7074@comet> References: <20080611070618.54E4066E24@smtp.gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <20080611070618.54E4066E24@smtp.gentoo.org> User-Agent: Mutt/1.5.17 (2007-11-01) X-Archives-Salt: 4a1776c4-0102-4a52-a565-0b30608bfb3b X-Archives-Hash: 868e239918e9bf80524415d5d12e2493 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On 03:06 Wed 11 Jun , Mike Frysinger wrote: > This is your one-day friendly reminder ! The monthly Gentoo Council > meeting is tomorrow in #gentoo-council on irc.freenode.net. See the > channel topic for the exact time (but it's probably 2000 UTC). Here's the proposed agenda. I intend to get every requested topic on the agenda so there is no need for an open floor afterwards. Carefully note the Preparation sections. If they aren't completed, we will postpone the topic to the -council mailing list or the next meeting instead of waste time during the meeting doing things that should've happened in advance. Please respond with any suggestions, including suggested order of the topics by urgency (within "old topics" and "new topics"). Unfortunately not all of the topics were posted to the council meeting reminder thread, so it was hard to dig them out. More meeting optimization ------------------------- I'd like to also set a 2-hour limit on the meeting. Anything we don't hit during that timeframe will be postponed to the list or the next meeting. We can also take an idea from http://en.opensuse.org/Meetings/About and set the +zmn channel modes: * +m - Moderated - People who don't have voices (+v) can't send messages to the channel. * +n - No external messages - With this mode, no one can send messages to the channel without even being joined. * +z - Relaxed moderation - When +z is set each message that would be blocked by +m is sent to all the users who are currently operator. That will allow council members to see everything said by everyone, but non-council people will not be able to see things said by other non-council people. Then +v can be given to anyone with good contributions. What do you think? Thanks, Donnie --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="20080612-agenda.txt" Updates to last month's topics ============================== http://www.gentoo.org/proj/en/council/meeting-logs/20080508-summary.txt Document of being an active developer ------------------------------------- Requested attendees: araujo Last month: Numerous suggested improvements to info on the certificate. Preparation: araujo needs to post progress, an updated certificate and any new requests to the gentoo-council or gentoo-project list 2+ hours before the meeting. Goal: Suggest changes. This should happen on-list. No discussion expected. Slacker arches -------------- Preparation: vapier needs to send the post 2+ hours before the meeting. Goal: Suggest changes. This should happen on-list. No discussion expected. Can the council help fewer bugs get ignored by arm/sh/s390 teams? ----------------------------------------------------------------- Preparation: Someone on an undermanned arch team needs to describe their workflow on-list 2+ hours before the meeting. Goal: Suggest changes. This should happen on-list. No discussion expected. PMS: Are versions allowed to have more than 8 digits? ----------------------------------------------------- http://archives.gentoo.org/gentoo-dev/msg_db2f5c09c2c0c8b042ca3d0dcec7cdaf.xml https://bugs.gentoo.org/show_bug.cgi?id=188449 Preparation: Do the package maintainers with extremely long PVs need them? The involved packages: sys-process/fuser-bsd sys-apps/net-tools sys-apps/gradm net-im/ntame media-video/captury media-libs/libcaptury media-libs/capseo sys-block/btrace www-apache/mod_depends net-wireless/rt2500 sys-fs/unionfs Preparation: What's the impact of extending versionator.eclass? Goal: With data in hand, make a decision. How to handle appeals --------------------- Preparation: Post to the gentoo-council mailing list 2+ hours before the meeting with your opinion. Goal: Vote on an approach that was previously posted to the list. New topics ========== as-needed by default -------------------- antarus requested that we vote on whether to add it to the default LDFLAGS. Preparation: Post your opinion to the -dev thread "RFC: --as-needed to default LDFLAGS" 2+ hours before the meeting. Goal: Vote. GLEP 54 ------- Preparation: Post your opinion to the -dev thread "A few questions to our nominees" 2+ hours before the meeting. Goal: Vote. GLEP 55 ------- Preparation: Post your opinion to the -dev thread "GLEP 55" 2+ hours before the meeting. Let it attempt to come to a consensus before we vote. Goal: Vote once the discussion's no longer clearly ongoing. We can hold this vote on the -council mailing list instead of waiting for the next meeting. GLEP 56 ------- Preparation: Post your opinion to the -dev thread "[GLEP56] USE flag descriptions in metadata" 2+ hours before the meeting. Let it attempt to come to a consensus before we vote. Goal: Vote once the discussion's no longer clearly ongoing. We can hold this vote on the -council mailing list instead of waiting for the next meeting. Status of PMS ------------- ferringb said: I'd like the council to please discuss the current status of PMS, if the running of it satisfys the councils requirements of a *neutral* standard, if the proposed spec actually meets said standards, and if said spec is actually going to be approved sometimes this side of '09. Preparation: Post your opinion to the -dev thread "One-Day Gentoo Council Reminder for June" 2+ hours before the meeting. --gBBFr7Ir9EOA20Yy-- -- gentoo-dev@lists.gentoo.org mailing list