Re: [gentoo-dev] Why I don't think the CoC is a good idea

[Kevin F. Quinn]

On Thu, 15 Mar 2007 00:06:28 +0100
Alexandre Buisse <nattfodd@g.o> wrote:

> [...] But then, why do we need a Code of Conduct at all? There
> is nothing in it that people don't already know and if they choose to
> still commit the offense, it's either that they don't think it's one
> or that they choose to ignore the consequences and commit it anyway.
> In both cases, having a written code won't change a thing.

This is a good point; effectiveness is key, and in designing a CoC one
should be crystal clear what the document is expected to achieve.
In the defense of having a CoC, it does provide a document we can point
to when asking people who don't realise their behaviour is disruptive,
to moderate that behaviour.

Before we commit ourselves to a CoC, we should agree what the CoC
precisely is _for_ - setting out the document scope should be the
first priority.  Here are some examples of what I mean by setting a
document scope first:

"The aim of the CoC is to encourage developers to work together
productively in a positive atmosphere."

"The aim of the CoC is to provide a point of reference for developers
and users alike to decide if their behaviour is acceptable."

"The aim of the CoC is to ensure Gentoo presents a professional image."

"The aim of the CoC is to define what behaviour is acceptable for
Gentoo developers and users."

"The aim of the CoC is to force all developers to adhere to an
Anglo-Saxon work ethic."

Just some examples; I'm not suggesting any are right, and some are
deliberately tongue-in-cheek.  What I'm trying to do, is highlight the
point that having a well-defined scope makes it easy to critically
and objectively examine what should and should not be in the CoC.

The scope can be decided in broad discussion - after which the CoC can
be drafted off-line and then presented for review against the scope
before final sign-off.

-- 
Kevin F. Quinn