public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arun Raghavan <ford_prefect@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Council manifesto of sping
Date: Tue, 22 Jun 2010 15:54:24 +0530	[thread overview]
Message-ID: <AANLkTimQr__39f1bmfIknlXVayPvh76C3P1qcY22VpC0@mail.gmail.com> (raw)
In-Reply-To: <pan.2010.06.22.10.02.12@cox.net>

On 22 June 2010 15:32, Duncan <1i5t5.duncan@cox.net> wrote:
> Arun Raghavan posted on Tue, 22 Jun 2010 10:43:42 +0530 as excerpted:
>
>> b) For questions like "- Should Python 3.x be stable?", isn't that for
>> team leads to decide? And for the council to resolve in case of
>> conflicts?
>
> Wouldn't the point for specifically pointing out python 3.x as an example,
> that there is in fact quite some conflict on it, as demonstrated by the
> threads discussing it right here?  If I'm not mistaken, sping has in fact
> mentioned that as an example in his "tone" thread, as well.  If I read him
> correctly, the implication is that before it got to the level it did,
> council should have voted on it, thus providing a final answer, as an
> alternative to the simmering level of discontent that's not quite at the
> boiling over point, that we seem to have with the situation now.  He does,
> after all, make a strong statement in favor of an "activist" council.

I did say questions like this one, not only this one.

Also, the context of that quote was from the bit of the manifesto that
advocates putting such questions to a global vote, which is what I was
enquiring about.

Cheers,
-- 
Arun Raghavan
http://arunraghavan.net/
(Ford_Prefect | Gentoo) & (arunsr | GNOME)



  reply	other threads:[~2010-06-22 10:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-19 19:56 [gentoo-dev] Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-19 21:06 ` [gentoo-dev] Manifesto for council election Tony "Chainsaw" Vroon
2010-06-20 11:19 ` [gentoo-dev] My Council manifest Petteri Räty
2010-06-20 13:47 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting Roy Bamford
2010-06-21 16:33 ` [gentoo-dev] Council manifesto of sping Sebastian Pipping
2010-06-21 18:20   ` Petteri Räty
2010-06-21 21:07     ` Sebastian Pipping
2010-06-21 19:25   ` Arun Raghavan
2010-06-21 21:36     ` Sebastian Pipping
2010-06-22  1:46       ` Brian Harring
2010-06-22  2:37         ` Sebastian Pipping
2010-06-22  5:13       ` Arun Raghavan
2010-06-22 10:02         ` [gentoo-dev] " Duncan
2010-06-22 10:24           ` Arun Raghavan [this message]
2010-06-30  0:45         ` [gentoo-dev] " Sebastian Pipping
2010-07-02 14:23           ` Arun Raghavan
2010-07-02 15:50             ` Sebastian Pipping
2010-07-02 17:30               ` Nirbheek Chauhan
2010-06-22  5:15       ` Arun Raghavan
2010-06-22  2:37   ` Alec Warner
2010-06-21 19:10 ` [gentoo-dev] My council manifesto Mark Loeser
2010-06-21 19:15   ` Arun Raghavan
2010-06-21 19:27     ` Mark Loeser
2010-06-21 19:30       ` Arun Raghavan
2010-06-21 21:19 ` [gentoo-dev] Gentoo Council 2010/2011 - Voting Mike Frysinger
2010-07-02 22:32 ` [gentoo-dev] Re: Gentoo Council 2010/2011 - Voting - Reminder Roy Bamford

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=AANLkTimQr__39f1bmfIknlXVayPvh76C3P1qcY22VpC0@mail.gmail.com \
    --to=ford_prefect@gentoo.org \
    --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