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 1KGVDl-0007Jn-Nj for garchives@archives.gentoo.org; Wed, 09 Jul 2008 08:40:18 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3DAD8E0238; Wed, 9 Jul 2008 08:40:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id ECB1FE0238 for ; Wed, 9 Jul 2008 08:40:15 +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-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 5C69D6664E for ; Wed, 9 Jul 2008 08:40:15 +0000 (UTC) Date: Wed, 9 Jul 2008 01:40:13 -0700 From: Donnie Berkholz To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Monthly Gentoo Council Reminder for July Message-ID: <20080709084013.GC684@comet> References: <20080701093002.CFAB6670F5@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/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="a2FkP9tdjPU2nyhF" Content-Disposition: inline In-Reply-To: <20080701093002.CFAB6670F5@smtp.gentoo.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-Archives-Salt: ccb4ce1c-4909-4302-a7f5-ba13a4677647 X-Archives-Hash: bb3a3a0c1b0acb771a263294a67b722e --a2FkP9tdjPU2nyhF Content-Type: multipart/mixed; boundary="6zdv2QT/q3FMhpsV" Content-Disposition: inline --6zdv2QT/q3FMhpsV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05:30 Tue 01 Jul , Mike Frysinger wrote: > If you have something you'd wish for us to chat about, maybe even > vote on, let us know ! Simply reply to this e-mail for the whole > Gentoo dev list to see. Here's the proposed agenda. Please respond if I forgot something, it's=20 unclear, or you have another suggestion. As before, since we have an=20 agenda in advance we won't be holding an open floor. --=20 Thanks, Donnie Donnie Berkholz Developer, Gentoo Linux Blog: http://dberkholz.wordpress.com --6zdv2QT/q3FMhpsV Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="20080710-agenda.txt" Content-Transfer-Encoding: quoted-printable People who need to take action =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Non-council members who need to do something. araujo [Document of being an active developer] vapier [Slacker arches] antarus [as-needed by default] cardoe [GLEP 56] fmccor [Extent of Code of Conduct enforcement] Updates to last month's topics =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D http://www.gentoo.org/proj/en/council/meeting-logs/20080612-summary.txt Document of being an active developer ------------------------------------- Requested attendees: araujo Preparation: araujo needs to post progress, an updated certificate and=20 any new requests to the gentoo-council or gentoo-project list 4+ hours=20 before the meeting. Goal: Suggest changes. This should happen on-list. No discussion=20 expected. Slacker arches -------------- Preparation: vapier needs to send the post 4+ hours before the meeting.=20 (Mike, is this ever going to happen?) Goal: Suggest changes. This should happen on-list. No discussion=20 expected. Can the council help fewer bugs get ignored by arm/sh/s390 teams?=20 -----------------------------------------------------------------=20 Preparation: Someone on an undermanned arch team needs to describe their=20 workflow on-list 4+ hours before the meeting. Any volunteers? Goal: Suggest changes. This should happen on-list. No discussion=20 expected. New topics =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Appeals of spb, rbrown, & philantrop ------------------------------------ Preparation: Reach decisions. Goal: Announce decisions no later than July 10 via personal emails and=20 on-list to avoid disrupting the meeting. Meeting frequency & time ------------------------ Do we want biweekly meetings that last one hour each? Here are the time slots we found using whenisgood.net: 2000-2100 UTC Thursday 1600-1800 UTC Sunday (conflicts: flameeyes, jokey) Preparation: Respond to the ongoing thread regarding your opinion on=20 biweekly meetings. Goal: Vote on time & frequency on the council alias no later than July=20 10. as-needed by default -------------------- antarus requested that we vote on whether to add it to the default=20 LDFLAGS. Preparation: Antarus will post a deployment plan to -dev for discussion.=20 We can vote on it on -council as soon as it solidifies. (Alec, please do=20 this by July 17.) Goal: Status check with antarus. GLEP 54 ------- Preparation: Preparation: Post your opinion to the -dev thread "A few=20 questions to our nominees" 4+ hours before the meeting. Last month:=20 dberkholz: http://archives.gentoo.org/gentoo-dev/msg_c6e4ba8293f50c1e0444e= 67d59cf85ea.xml lu_zero: http://archives.gentoo.org/gentoo-dev/msg_05614741b3942bfdfb21fd8= ebb7955e0.xml Goal: Status check at meeting to see who's ready to vote. Vote on-list=20 no later than July 17. GLEP 55 ------- Preparation: Post your opinion to the -dev thread "GLEP 55" 4+ hours=20 before the meeting. Last month: dberkholz: http://archives.gentoo.org/gentoo-dev/msg_c6e4ba8293f50c1e0444e= 67d59cf85ea.xml Goal: Status check at meeting to see who's ready to vote. Vote on-list=20 once we're ready. GLEP 56 ------- Preparation: Post your opinion to the -dev thread "[GLEP56] USE flag=20 descriptions in metadata" 4+ hours before the meeting. (Cardoe: Did the=20 requested updates ever get made?) Last month: dberkholz: http://archives.gentoo.org/gentoo-dev/msg_54ee20d2b1d8122370afd= d4b3d7aafc9.xml Goal: Status check at meeting to see who's ready to vote. Vote on-list=20 no later than July 17, if requested changes are made. User Relations authority ------------------------ Ferris asks: Does userrel have the authority to enforce the Code of=20 Conduct on users in the same way devrel does for developers? Preparation: Donnie will start a thread on the -council list. Post your=20 opinion there. If everyone's posted in advance of the meeting, status=20 check at meeting to see who's ready to vote. Goal: Reach a decision on-list no later than July 17. Extent of Code of Conduct enforcement=20 ------------------------------------- Ferris asks: Can people be entirely banned from Gentoo (mailing lists,=20 IRC channels, etc.)? Who can do it, how's it work, under whose=20 authority? Are there any prerequisites? He cites the corner case of=20 refusal to accept a security patch. Ferris, I couldn't make enough sense out of your long email to council@=20 to summarize any more of it reasonably, sorry. Please send a response to=20 this that succinctly clarifies any part of your agenda proposals that I=20 got wrong. Preparation: Clarification from Ferris. After that, Donnie will start a=20 thread on the -council list. Post your opinion there. Goal: Reach a decision on-list no later than July 17. --6zdv2QT/q3FMhpsV-- --a2FkP9tdjPU2nyhF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEABECAAYFAkh0eW0ACgkQXVaO67S1rtu4hACfThZ/RwmBeIP+ncfdM4eq8XBF 5HoAoMVgIshopIFXmxv707Rwmvo7QHZg =ZZ+F -----END PGP SIGNATURE----- --a2FkP9tdjPU2nyhF-- -- gentoo-dev@lists.gentoo.org mailing list