public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Loeser <halcy0n@gentoo.org>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Extent of Code of Conduct enforcement
Date: Tue, 22 Jul 2008 02:34:28 -0400	[thread overview]
Message-ID: <20080722063428.GB23164@aerie.halcy0n.com> (raw)
In-Reply-To: <20080714063554.GB5982@comet>

[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]

Donnie Berkholz <dberkholz@gentoo.org> said:
> Can people be entirely banned from Gentoo?

It would be ideal, but not technically feasible.

> - What would such a ban include? Some ideas -- the person could not:
>   - Post to any gentoo mailing list;
>   - Post to gentoo bugzilla;
>   - Participate in #gentoo- IRC channels; 

All of these seem to be possible to an extent and would be valid if we
would like to limit the damage an individual does to the community.

>   - Contribute to gentoo (hence my corner case of a security fix) except 
>     perhaps through a proxy;

This would be difficult to control, and I don't think we should care in
this case.  If they are contributing through a proxy (say Linus), should
we reject their fix?

> - Why would we do it?

Because they are damaging the community and driving possible
contributors aways.

> - Under whose authority would it happen?

Devrel and/or userrel

> - Would it be reversible? What conditions would cause this?

This would be something I would like to hear opinions from userrel and
devrel on.  Do they think someone that we would want to ban permanently
would turn around enough to unban?

>   Since the banned person couldn't participate in Gentoo, we'd never 
>   know whether anything changed.

Refer to my comment above.

> - How would one appeal this? Would there be a chance to respond before
>   the ban?

If it got to the point of us considering a permanent ban, I don't think
there is any reason to even consider listening to an appeal at that
point.  With that being said, I would expect a permanent ban to be a
majority vote from devrel or userrel to put such a ban in place.

> - Would moderating the gentoo-dev mailing list obsolete this concept?

I don't think so.


-- 
Mark Loeser
email         -   halcy0n AT gentoo DOT org
email         -   mark AT halcy0n DOT com
web           -   http://www.halcy0n.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-07-22  6:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  6:35 [gentoo-council] Extent of Code of Conduct enforcement Donnie Berkholz
2008-07-14  8:23 ` Alec Warner
2008-07-14 14:48   ` Ferris McCormick
2008-07-14 18:23 ` Roy Bamford
2008-07-14 19:20 ` Tobias Scherbaum
2008-07-14 19:54   ` Ferris McCormick
2008-07-16  2:39 ` Chrissy Fullam
2008-07-16  2:54   ` Mike Doty
2008-07-16  3:07     ` Chrissy Fullam
2008-07-22  6:34 ` Mark Loeser [this message]
2008-07-22 12:26   ` Ferris McCormick
2008-07-22 13:33   ` Ferris McCormick
2008-07-22 14:21     ` Chrissy Fullam
2008-07-22 13:51   ` Chrissy Fullam
  -- strict thread matches above, loose matches on Subject: below --
2008-07-25 13:24 Ferris McCormick
2008-08-14  9:51 ` Donnie Berkholz

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=20080722063428.GB23164@aerie.halcy0n.com \
    --to=halcy0n@gentoo.org \
    --cc=gentoo-council@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