public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Gentoo as a team effort
Date: Sat, 15 Jun 2013 16:14:17 -0400	[thread overview]
Message-ID: <CAGfcS_kX47zUBmmOvStb5YEKZGGcywW1VfDodJpuJmomWxVBzA@mail.gmail.com> (raw)
In-Reply-To: <20130615200047.GA7798@linux1>

On Sat, Jun 15, 2013 at 4:00 PM, William Hubbs <williamh@gentoo.org> wrote:
> This is a tough one. If the council does start to become more proactive,
> there would need to be a way to guard against the council stepping into
> a project and dictating how that project will do things without fully
> understanding the implications of their decision.
>

Honestly, I think the solution to this is to make sure that the
council is staffed with individuals who can be trusted not to do this.

However, there really is no difference between a council that needs to
have matters brought before it, and one which can act proactively.  If
ANYBODY can bring a matter to the council, then it will one way or
another end up looking into anything it wants to.

I think that issues are best solved by individuals first and foremost.
 However, it doesn't make sense to have battles going on for months
where there simply isn't agreement.  There are many situations where
almost any decision is better than no decision (an example comes to
mind but I won't bring it up as a distraction).

However, as I've mentioned elsewhere, I do think the council should be
a little more active.  If council members have an opinion they can
state it on the lists, and allow themselves to be engaged a little on
it.  Likewise, the council doesn't HAVE to wait until a meeting to
make a decision, though if a matter can afford to wait doing so might
be wise.  Getting involved in discussion early isn't about fanning
flames/etc, but it is about letting everybody know where they stand,
and also letting arguments mature to a reasonable level before making
a decision (rather than putting them on hold for a few weeks, and then
restarting them when there is a request for more info).  Also, council
members can use their position to try to influence direction absent a
formal decision, and that need not be on-list.

One other thing - I don't intend to suggest that I'm not sympathetic
to the concerns of individuals as well.  I really hate that the online
thing often tends to depersonalize everything.  I just don't think we
can operate in a state of perpetual paralysis either - we'll never
reach 100% consensus on any decision.  There isn't a single Gentoo
developer I don't have respect for - all have given of their time and
energy and we're all better for it.

Rich


  reply	other threads:[~2013-06-15 20:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 11:50 [gentoo-project] Gentoo as a team effort Andreas K. Huettel
2013-06-15 11:54 ` Fabian Groffen
2013-06-15 12:15   ` Andreas K. Huettel
2013-06-15 21:43     ` Michael Weber
2013-06-16  4:20     ` "Paweł Hajdan, Jr."
2013-06-16  6:31     ` Sergey Popov
2013-06-16  9:33       ` Douglas Dunn
2013-06-15 12:08 ` Rich Freeman
2013-06-15 12:42   ` Johannes Huber
2013-06-15 13:44     ` Tom Wijsman
2013-06-15 14:19       ` Johannes Huber
2013-06-15 16:08         ` Tom Wijsman
2013-06-15 13:30 ` Markos Chandras
2013-06-15 16:08   ` Roy Bamford
2013-06-15 20:00     ` William Hubbs
2013-06-15 20:14       ` Rich Freeman [this message]
2013-06-17 16:15 ` Chí-Thanh Christopher Nguyễn
2013-06-17 17:02   ` Rick "Zero_Chaos" Farina
2013-06-17 18:24     ` Chí-Thanh Christopher Nguyễn

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=CAGfcS_kX47zUBmmOvStb5YEKZGGcywW1VfDodJpuJmomWxVBzA@mail.gmail.com \
    --to=rich0@gentoo.org \
    --cc=gentoo-project@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