public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chrissy Fullam" <musikc@gentoo.org>
To: "'gentoo-council'" <gentoo-council@lists.gentoo.org>
Subject: RE: [gentoo-council] Extent of Code of Conduct enforcement
Date: Tue, 15 Jul 2008 19:39:21 -0700	[thread overview]
Message-ID: <2c6d01c8e6ed$2d1dbb60$87593220$@org> (raw)
In-Reply-To: <20080714063554.GB5982@comet>

> Can people be entirely banned from Gentoo?

By technical merit I'd not say that anything is entirely outside of
technical ability if one has that ability to circumvent the system. Doesn't
mean we should throw the towel in and just sit back to take abuse though.

> - 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;
>   - Contribute to gentoo (hence my corner case of a security fix) except
>     perhaps through a proxy;

Mailing list rights and bugzilla rights for that email address would be
revoked; the argument is if they subscribed with a different email address
what then? If they are confirmed to be the original person User Rel should
talk to them and quite possibly extend the ban to the new accounts - not my
decision just an idea; argument being when do we stop because they could
keep trying with new accounts? My response is situational, likely I'd
consider continuing doing it so long as it was verified to be that person
but that is my opinion. Changing your name doesn't make you less of an ass,
only you can make yourself less of an ass.
Regarding IRC, we should only remove their nick from #gentoo-dev as other
channels are moderated and operated by the relevant team. I for one would
remove anyone from #gentoo-devrel, but that is my right to do so.
Contributions... I'd vote to only accept via a proxy so long as said proxy
understands they are vouching 100% for the quality of the code as well. This
should be common practice today I suspect.

> - Why would we do it?

Because we do our developers and users a disservice to allow such repeat
offenders the luxury of participating in such a manner while ruining the
experience for others. Simply put people quit and drop Gentoo solely as a
result of one or several vocal negative and abusive influences. Let's do our
jobs and do something about it.

> - Under whose authority would it happen?

Dev Rel would have removed such a person from being a developer in which
case this round of elimination would fall upon User Rel, whom Dev Rel would
gladly assist if assistance were requested.

> - Would it be reversible? What conditions would cause this?
> 
>   Since the banned person couldn't participate in Gentoo, we'd never
>   know whether anything changed.

Life happens, people change. No ban should be 100% forever so let's be
realistic here. If User Rel banned someone from participating they could
follow the same rule set that Dev Rel uses: a forcibly removed developer may
return upon approval of the current Dev Rel lead. That said, if a forcibly
removed contributor/participator wanted to come back that person would need
to convince the User Rel lead of a darn good reason and such re-joining
should be done under a probationary period subject to review.

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

Appeal a ban, no. I think if someone is being considered for the ban there
should be an exchange of dialog. That said, no person eligible for such an
extreme course of action could honestly say they were surprised and caught
off guard. Such a person would have a repeated history of conflicts and
discussions warning them that they are out of line, be it in a bug or via
emails.

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

Nope, just make it less likely to happen as hopefully we'd be able to show
people that we are taking this seriously and it must stop or the
consequences continue to get more severe. Much like the legal system fmccor
references, a jury or judge is less sympathetic to the protests of a repeat
offender.


Kind regards,
Christina Fullam
Gentoo Developer Relations Lead | Gentoo Public Relations 




-- 
gentoo-council@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-07-16  2:39 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 [this message]
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='2c6d01c8e6ed$2d1dbb60$87593220$@org' \
    --to=musikc@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