From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Council Agenda 20100809 rev 01
Date: Sun, 8 Aug 2010 12:28:37 +0100 [thread overview]
Message-ID: <20100808122837.3922448c@snowcone> (raw)
In-Reply-To: <AANLkTinu2-oupzkb8Mv7U4QJqEUe9piY4dCUwS8Bwoc3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2179 bytes --]
On Sun, 8 Aug 2010 16:47:42 +0530
Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> > Uh, it *was* requested for a vote, and the Council decided instead
> > to vote on something else and not upon what was asked.
>
> So you ask again in the next meeting. And if it happens again, you
> file a protest. If it still happens, write a GLEP to prevent issues
> from being deferred indefinitely. Do I really need to give you ideas
> on how to stubbornly push proposals through?
When we *did* repeatedly push for GLEP 55 discussion and acceptance, we
were told that we were pushing it too hard and that it was creating too
much noise. When we scale back and only give it a minimum of attention
when related topics come up, we're told we should be pushing over and
over again and protesting.
Whichever way we go, someone's going to moan. I am glad to see,
however, that the only remaining objections to GLEP 55 are on purely
procedural matters...
> There also comes a time when repeatedly bringing up a GLEP that you
> have no interest in getting approved becomes rude and
> counterproductive.
GLEP 55 is brought up when it's the appropriate answer to a problem
someone raises. It is no longer being pushed purely on its own,
because when it was pushed on its own there were complaints that it
was being discussed too much.
As for no interest in getting it approved, that's clearly nonsense as
you know fine well. Past experience has shown that repeatedly asking
for Council discussion on it does absolutely nothing to get it
approved, so we don't do that any more.
> > It's extremely misleading of you to claim that it's the
> > responsibility of the GLEP 55 authors to push it to the Council at
> > this point. That was already tried several times, and got nowhere.
>
> It is excessively misleading of you to claim that Brian said that the
> GLEP 55 *authors* should push it to the Council. Nice strawman. He
> made a simple statement: The people who want the GLEP should either
> put it up for vote and settle it's status, or stop wasting everyone's
> time and let it die.
Been there, done that, got nowhere.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-08 11:28 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
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 [this message]
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=20100808122837.3922448c@snowcone \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-dev@lists.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