public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] On the way Devrel is constituted
Date: Thu, 20 Jun 2013 22:07:25 +0200	[thread overview]
Message-ID: <51C360FD.30408@gentoo.org> (raw)
In-Reply-To: <20130620190330.GA23427@linux1>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

William Hubbs schrieb:
> Here are some thoughts I have wrt this situation:
> 
> 1. The QA and Devrel projects are directly accountable to the council. 
> This protects against abuse of power since the council can remove
> people from these projects if they determine that power is being
> abused.
> 
> 2. The leads of these projects should be selected by the projects like 
> any other project, but confirmed by the council.
> 
> 3. Since the leads are confirmed by the council, I don't think it is 
> necessary for them to go back to the council for approval for actions 
> they take.
> 
> 4. Both of these projects require unique skill sets that most
> developers may not have, so I don't think electing members of these
> projects is a good idea.
> 
> 5. Any actions these projects take can be appealed to the council (This 
> follows from point 1).
> 
> Thoughts?

These rules sound all ok, but which real problem are they intended to solve?

Is there an actual documented instance where QA or devrel abused their
power, and which could have been prevented by council confirmation? I am
aware of wltjr's case, but even from his perspective it sounded more like
bullying than abuse of power.

If not, what indication exists that makes such abuse of power appear likely
in the future?

If such a thing has never occured, and there is nothing which indicates
that it is going to occur, then I think we can drop the rule #2 as it
introduces only unnecessary bureaucracy. If we start seeing actual abuse of
power then requiring approval of Council for QA/devrel leads or actions can
be reconsidered.


Best regards,
Chí-Thanh Christopher Nguyễn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/

iEYEARECAAYFAlHDYP0ACgkQ+gvH2voEPRA7hgCdFopvXWhx4jJ0rFwJzm9TLalw
DvEAn1jFOOQ00O2sm6GD90w+P0P5W1ZH
=116z
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2013-06-20 20:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 20:18 [gentoo-project] On the way Devrel is constituted hasufell
2013-06-19 20:43 ` Petteri Räty
2013-06-19 21:41   ` hasufell
2013-06-19 22:19     ` William Hubbs
2013-06-20  0:50 ` Alexis Ballier
2013-06-20  2:00   ` Rich Freeman
2013-06-20  3:17     ` Alexis Ballier
2013-06-20 10:44       ` Sean Amoss
2013-06-20 10:50         ` Markos Chandras
2013-06-20 11:25           ` Douglas Dunn
2013-06-20 11:30             ` Douglas Dunn
2013-06-20 19:03             ` William Hubbs
2013-06-20 19:32               ` Alexis Ballier
2013-06-20 19:33               ` Rich Freeman
2013-06-20 20:07               ` Chí-Thanh Christopher Nguyễn [this message]
2013-06-20 20:20                 ` William Hubbs
2013-06-20 11:03         ` hasufell
2013-06-20  2:03   ` Rich Freeman
2013-06-20  5:19     ` Samuli Suominen
2013-06-20  7:33       ` Thomas Raschbacher (Gentoo)
2013-06-20 10:41       ` Anthony G. Basile
2013-06-20  8:52   ` Roy Bamford
2013-06-20 11:59 ` Michał Górny

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=51C360FD.30408@gentoo.org \
    --to=chithanh@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