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] Council manifesto of sping
Date: Tue, 22 Jun 2010 10:43:42 +0530	[thread overview]
Message-ID: <AANLkTilkN7w0rz5628wtVPyI3HYTmRB_sAMylCnNdhu9@mail.gmail.com> (raw)
In-Reply-To: <4C1FDB72.3020609@gentoo.org>

On 22 June 2010 03:06, Sebastian Pipping <sping@gentoo.org> wrote:
> Arun,
>
>
> On 06/21/10 21:25, Arun Raghavan wrote:
>>> My manifesto up here now:
>>> http://dev.gentoo.org/~sping/council-manifesto-2010-sping.txt
>>
>> For all your points where you do not have a concrete proposal of how
>> you intend to tackle the problem, could you please elaborate?
>
> please take your time to formulate concrete questions.

On reading again, you do have suggestions on how you would deal with
most of what you've spoken. The only one that I think could use more
details (other than all the references to "tone" which I think we
should let rest for a while) is "Opening up documentation" - do you
have any ideas for this process that might help with this while
maintaining the quality the docs team has maintained thus far?

As a follow up question, for documentation, PR, the website redesign,
and templates, do you feel that these are tasks that need to be
addressed by council members? Is there anything preventing you from
taking the ball and running with it if you don't get elected into the
council?

And another one for "More direct democracy":

a) How would you decide what questions go up for public vote and which
ones stay with the council?

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?

c) For questions like "- Should developer X be banned?", would you be
willing to do this if it meant a lot of washing of dirty linen in
public, or protracted flamewars (and other reasons why we have a bunch
of level-headed people in place to deal with this calmly and quietly)?
If no, where would you draw the line? If yes, how would you deal with
the fallout?

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



  parent reply	other threads:[~2010-06-22  5:14 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 [this message]
2010-06-22 10:02         ` [gentoo-dev] " Duncan
2010-06-22 10:24           ` Arun Raghavan
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=AANLkTilkN7w0rz5628wtVPyI3HYTmRB_sAMylCnNdhu9@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