From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] On the way Devrel is constituted
Date: Thu, 20 Jun 2013 15:32:21 -0400 [thread overview]
Message-ID: <20130620153221.0ca1653c@gentoo.org> (raw)
In-Reply-To: <20130620190330.GA23427@linux1>
On Thu, 20 Jun 2013 14:03:30 -0500
William Hubbs <williamh@gentoo.org> wrote:
> On Thu, Jun 20, 2013 at 07:25:55AM -0400, Douglas Dunn wrote:
> > In my opinion the devrel project lead or perhaps have 3 leads but
> > should at least be confirmed by the council, if that can happen and
> > the lead and or leads can make sure that the other devrel members
> > are upholding the intent of the coc. It doesn't take a law degree
> > to enforce the coc, maybe give individual devrel members the
> > authority to give temporary punishments, but i think anything
> > permanent should go to the council to at least confirm devrels
> > suggestion of a permanent punishment.
>
> If the council has to approve a major action devrel takes against a
> developer, there is no point in that developer appealing to the
> council.
>
> > But imo if the lead of devrel needs confirmed by the council, and
> > the council has the power to remove the lead, and the final appeal
> > goes to the council, i dont see much room for the possibility of
> > abuse by devrel.
>
> I don't see why the council couldn't remove the devrel lead if they
> felt it necessary.
>
> 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?
+1
next prev parent reply other threads:[~2013-06-20 19:32 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 [this message]
2013-06-20 19:33 ` Rich Freeman
2013-06-20 20:07 ` Chí-Thanh Christopher Nguyễn
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=20130620153221.0ca1653c@gentoo.org \
--to=aballier@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