[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Promoting the GNU Kind Communication Guidelines?

From: Alex Griffin
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Sun, 28 Oct 2018 14:50:54 -0500

On Sun, Oct 28, 2018, at 1:42 PM, Tonton wrote:
> It seems to me you are making punishment way bigger than it actually is.

The CoC actually says that maintainers have a responsibility to remove 
offenders or risk being removed themselves. In contrast the Debian Code 
of Conduct says:

> While this code of conduct should be adhered to by participants, we 
> recognize that sometimes people may have a bad day, or be unaware of 
> some of the guidelines in this code of conduct. When that happens, you 
> may reply to them and point out this code of conduct. Such messages 
> may be in public or in private, whatever is most appropriate. However, 
> regardless of whether the message is public or not, it should still 
> adhere to the relevant parts of this code of conduct; in particular, 
> it should not be abusive or disrespectful. Assume good faith; it is 
> more likely that participants are unaware of their bad behaviour than 
> that they intentionally try to degrade the quality of the discussion.

The difference is like night and day.

> Remember the CoC is only true for some communities/cultures, it does not
> influence your legal entity outside of your interactions with the community

To enter into a covenant, or agree to be bound by a code, means to stake 
your word on it. The words themselves actually carry weight, and not 
just as rules to follow, which is why the tiniest details of these 
documents receive so much scrutiny.

>From sentence 1 of the Contributor Covenant:
> In the interest of fostering an open and welcoming environment, we as 
> contributors and maintainers pledge to [...]

This snippet right here is a problem even before we get to the meat and 
potatoes. I don't appreciate the presumption that my mere participation 
indicates my agreement with this document. It rubs me the wrong way even 
when I'm only reporting a bug (which does fall under its scope, because 
'issues', as found in an issue tracker, are explicitly mentioned further 

Alex Griffin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]