From: "Alec Warner" <antarus@gentoo.org>
To: "Donnie Berkholz" <dberkholz@gentoo.org>
Cc: gentoo-council <gentoo-council@lists.gentoo.org>
Subject: Re: [gentoo-council] Extent of Code of Conduct enforcement
Date: Mon, 14 Jul 2008 08:23:59 +0000 [thread overview]
Message-ID: <b41005390807140123j3bb79784naaf0e899cecd0743@mail.gmail.com> (raw)
In-Reply-To: <20080714063554.GB5982@comet>
On Mon, Jul 14, 2008 at 6:35 AM, Donnie Berkholz <dberkholz@gentoo.org> wrote:
> Can people be entirely banned from Gentoo?
no
>
> - What would such a ban include? Some ideas -- the person could not:
> - Post to any gentoo mailing list;
technically feasible
> - Post to gentoo bugzilla;
technically feasible
> - Participate in #gentoo- IRC channels;
technically infeasible. Also a hard sell; traditionally gentoo-*
channels that are not #gentoo-dev and #gentoo are owned and operated
by gentoo subprojects with the permission of the gentoo reps.
Enforcing a ban in all channels would be difficult.
> - Contribute to gentoo (hence my corner case of a security fix) except
> perhaps through a proxy;
nothing stops them from contributing to the community; it is not as if
Gentoo controls all outlets anyway.
>
> - Why would we do it?
To prevent gentoo from being messed with by people who have routinely
proven that they are unfit to assist the distribution.
>
> - Under whose authority would it happen?
Userrel.
>
> - Would it be reversible? What conditions would cause this?
I assume the person would ask to return or have someone vouch for them.
>
> Since the banned person couldn't participate in Gentoo, we'd never
> know whether anything changed.
I would think that if the person wanted to come back they would:
Make an effort to contact Gentoo; It is not as if developers would
not talk to this individual.
Gentoo itself would take this person back provisionally to ensure
things were different. This is
a case by case deal and I think is difficult to pin down.
>
> - How would one appeal this? Would there be a chance to respond before
> the ban?
Since the ban would require some amount of history I don't see any
particular reason not to solicit feedback from said person.
>
> - Would moderating the gentoo-dev mailing list obsolete this concept?
If moderating gentoo-dev obsoletes this concept then I think the
concept itself is flawed (gentoo is more than gentoo-dev)
>
> --
> Thanks,
> Donnie
>
> Donnie Berkholz
> Developer, Gentoo Linux
> Blog: http://dberkholz.wordpress.com
>
--
gentoo-council@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-07-14 8:24 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 [this message]
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
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=b41005390807140123j3bb79784naaf0e899cecd0743@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=dberkholz@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