public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ferris McCormick <fmccor@gentoo.org>
To: gentoo-council <gentoo-council@lists.gentoo.org>
Cc: Ferris McCormick <ferris@fmccor.us>
Subject: Re: [gentoo-council] Extent of Code of Conduct enforcement
Date: Tue, 22 Jul 2008 13:33:54 +0000	[thread overview]
Message-ID: <1216733634.1979.159.camel@liasis.inforead.com> (raw)
In-Reply-To: <20080722063428.GB23164@aerie.halcy0n.com>

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


On Tue, 2008-07-22 at 02:34 -0400, Mark Loeser wrote:
> Donnie Berkholz <dberkholz@gentoo.org> said:
> > Can people be entirely banned from Gentoo?
> 
> It would be ideal, but not technically feasible.
> 
> > - 
 ....................... <snip
> ..........................................
> 
> > - Why would we do it?
> 
> Because they are damaging the community and driving possible
> contributors aways.
> 
Let me respond to this specifically.  I have pretty strong views on
this, and I suspect they might reflect a minority opinion.

I'm going to divide this into two cases, because I think the first one
is easy.  First case is developers who leave or threaten to leave giving
the reason that "XXX (a developer or user) drove them away because
of ...".  Second case is a sponsor who threatens to withdraw support
"unless something is done about XXX."

In the first case, my reaction is absolute.  The developer who threatens
to leave because of someone else is (1) making the judgment call that we
care if he leaves; (2) Is resorting to extortion to get rid of someone
else (or reign someone else in or whatever).  At that point, I'd wish
him well in his future endeavors and start retirement process.  I view
giving in to such a threat as at least as harmful as whatever or whoever
triggered it in the first place.  This is based on my own background and
experiences, and others no doubt react differently.

Now, there is a variation on this:  The developer who resigns, citing
abuse as the reason.  Here, the process has broken down.  Believe it or
not, devrel and userrel will work with problems like this if we know
there are such problems to address.  For example, if you want me
involved, best is to contact me personally or open a bug assigned to me.
If you want someone else, do whatever that person prefers.  It's a
matter of posture --- we should all be prepared to help work out
conflicts, but we should not give in to "He goes or I go." 

The second case is more delicate.  It is still a form of extortion, but
conceivably with merit.  I think the resolution requires negotiation
with the sponsor and the "problem child".  If we can reach no agreement,
I suppose we have to do what seems best for the community.  That will
always be a decision depending on each circumstance.

Probably nothing new here, but I wanted to clarify my opinion a bit.
Regards,
Ferris
-- 
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Devrel, Sparc, Userrel, Trustees)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-07-22 13:33 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
2008-07-22 12:26   ` Ferris McCormick
2008-07-22 13:33   ` Ferris McCormick [this message]
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=1216733634.1979.159.camel@liasis.inforead.com \
    --to=fmccor@gentoo.org \
    --cc=ferris@fmccor.us \
    --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