From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: peper@gentoo.org, council@gentoo.org
Subject: Re: [gentoo-dev] Re: Council Agenda 20100809 rev 01
Date: Sat, 7 Aug 2010 15:48:32 -0500 [thread overview]
Message-ID: <20100807204832.GA21345@linux1> (raw)
In-Reply-To: <20100807131630.GJ12708@hrair.al.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
On Sat, Aug 07, 2010 at 06:16:30AM -0700, Brian Harring wrote:
> On Fri, Aug 06, 2010 at 09:26:46PM +0200, Tommmmm Chvvvtal wrote:
> > Hi,
> > since I am this meetings girl for everything here is first pass on our
> > agenda.
> >
> > I am adding this mail only to g-dev and g-dev-announce to see if
> > everyone notice, sorry if it slip your radar. Also if you have something
> > to say on this mail please reply to gentoo-dev, or you will render me
> > quite sad about thread breaking.
> >
> > Without much ado here goes THE PLAN:
> >
> > 1) allow all members to show up (5 min)
> > 2) voting
> > 2a) we have nothing to vote this time, nobody wanted anything YAY :)
> > 3) discussion
> > 3a) from last council meeting: the mailing list situation
> > 3b) from last council meeting: eclass API changes
> > 3c) EAPI 4 status (jmbsvicetto nominate this so we actualy do something new)
> > 4) Bugs assigned to council@ in bugzilla and their progress
> > 5) select the chair for following meeting
> > 6) open floor: community/developers can smash us here :)
> > Z) buy some cookies (30 min)
>
> I suspect we may not wind up being able to get to it in the coming
> meeting, but I'd like g55 sorted.
>
> Specifically, if the authors of it (cc'd) want it to move forward,
> request the council vote on it. If you don't want it voted on, mark
> it moribund.
>
> The purpose behind this is to put to end this discussion rather than
> having it flare up and make a mess every few months.
>
> Simply put, it's nothing but divisive noise at this point with no real
> new technical discourse occuring- meaning it's realistically time for
> a decision (either push it to a vote or put it to bed).
Regardless of my personal opinions about the technical issues on this
glep, I agree with the above statement. I am personally tired of seeing
the discussion flare up every few months and go nowhere.
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-07 20:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 19:26 [gentoo-dev] Council Agenda 20100809 rev 01 Tomáš Chvátal
2010-08-06 21:49 ` "Paweł Hajdan, Jr."
2010-08-06 22:36 ` Alex Legler
2010-08-07 4:27 ` "Paweł Hajdan, Jr."
2010-08-07 7:53 ` Thomas Sachau
2010-08-07 16:16 ` "Paweł Hajdan, Jr."
2010-08-07 20:30 ` Nirbheek Chauhan
2010-08-07 13:16 ` [gentoo-dev] " Brian Harring
2010-08-07 20:48 ` William Hubbs [this message]
2010-08-08 7:46 ` Ciaran McCreesh
2010-08-08 8:55 ` Brian Harring
2010-08-08 9:10 ` Ciaran McCreesh
2010-08-08 10:05 ` Brian Harring
2010-08-08 10:15 ` Tomáš Chvátal
2010-08-08 10:18 ` Ciaran McCreesh
2010-08-08 11:11 ` Brian Harring
2010-08-08 11:17 ` Nirbheek Chauhan
2010-08-08 11:28 ` Ciaran McCreesh
2010-08-08 11:37 ` Jorge Manuel B. S. Vicetto
2010-08-12 12:24 ` Piotr Jaroszyński
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100807204832.GA21345@linux1 \
--to=williamh@gentoo.org \
--cc=council@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=peper@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox