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 1MED73-0000LE-26 for garchives@archives.gentoo.org; Wed, 10 Jun 2009 02:00:25 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D9B9F1C00C; Wed, 10 Jun 2009 02:00:23 +0000 (UTC) Received: from mail-fx0-f219.google.com (mail-fx0-f219.google.com [209.85.220.219]) by pigeon.gentoo.org (Postfix) with ESMTP id 9FF841C012 for ; Wed, 10 Jun 2009 02:00:23 +0000 (UTC) Received: by fxm19 with SMTP id 19so378313fxm.34 for ; Tue, 09 Jun 2009 19:00:23 -0700 (PDT) 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 Sender: cardoe@cardoe.com Received: by 10.204.103.209 with SMTP id l17mr734902bko.152.1244599222968; Tue, 09 Jun 2009 19:00:22 -0700 (PDT) In-Reply-To: <1244154362.11496.172.camel@localhost> References: <1244154362.11496.172.camel@localhost> Date: Tue, 9 Jun 2009 21:00:22 -0500 X-Google-Sender-Auth: 729f574c6dc9793f Message-ID: Subject: Re: [gentoo-dev] Gentoo Council Reminder for June 11 From: Doug Goldstein To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: e7a194ee-4c61-4761-8b19-17a40175d8da X-Archives-Hash: 131e22d851c8299a007f060390d6f639 On Thu, Jun 4, 2009 at 5:26 PM, Tiziano M=C3=BCller wr= ote: > This is your friendly reminder! Same bat time (typically the 2nd & 4th > Thursdays at 2000 UTC / 1600 EST), same bat channel (#gentoo-council @ > irc.freenode.net) ! > > 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. > > For more info on the Gentoo Council, feel free to browse our homepage: > http://www.gentoo.org/proj/en/council/ > > > Following is the preliminary meeting agenda. > > > EAPI 3: Short discussion of the progress > ---------------------------------------- > > zmedico will provide an update on the progress of the implementation. Sho= rt > discussion of problems and implementation decisions if needed. I'd say let's involve all the package manager maintainer groups. Each packager manager can have a rep speak on their behalf and we can plow through this topic fairly quickly. > > > Default ACCEPT_LICENSE > ---------------------- > Goal: A possible default value for ACCEPT_LICENSE has been proposed. Deci= de > whether that's ok. What happens to the X11 license files (one for each ap= p)? In virtually all situations MIT has been used for the X11 license, which should be sufficient enough for us. The previously proposed defaults for ACCEPT_LICENSE all looked reasonable to me. > > > Bash-4 in EAPI-3 > ---------------- > Goal: A request has been made to allow bash-4.0 features in EAPI-3. Decid= e > first whether or not to open the EAPI-3 feature list at all. No. bash-4 has seen some regressions and some oddities. 24 patches in and its starting to seem remotely sane, except the problem is it does not have wide scale adoption yet. I expect to see a lot of patches coming. Additionally, EAPI-3 has been an ongoing thing long enough. The more we keep pushing this off the more items should be shuffled in. We decided what EAPI-3 was a long time back. Stick with that. EAPI-4 can be the bases of bash-4 support. > > > Define EAPI development/deployment cycles > ----------------------------------------- > > Goal: Start discussion about EAPI development/deployment. For example: > Collect problems of eapi introductions in the past, like reverting > ebuilds to former eapis to get them stable, not waiting for the pm > support a certain eapi before requesting stable keywords for ebuilds > using the new eapi, .... Collect problems of EAPI development like > feature-freeze, late feature removals (due to implementation problems). > Eventually develop a lightweight EAPI development model. This is still something being discussed on the mailing lists and belongs there. Not in a council meeting. If I am AFK during the council meeting due to being in a skiff, I have designated tanderson/gentoofan23 as my proxy. --=20 Doug Goldstein