unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Griffin <a@ajgrf.com>
To: Tonton <tonton@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Sun, 28 Oct 2018 14:50:54 -0500	[thread overview]
Message-ID: <20181028195054.GA10708@antares.lan> (raw)
In-Reply-To: <20181028194258.773fa475@merlin.browniehive.net>

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 
down).

-- 
Alex Griffin

  reply	other threads:[~2018-10-28 19:51 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-23 11:15 Promoting the GNU Kind Communication Guidelines? Mathieu Lirzin
2018-10-23 13:38 ` Tobias Geerinckx-Rice
2018-10-23 14:39   ` Mathieu Lirzin
2018-10-24  1:06 ` Alex Griffin
2018-10-24  3:02   ` Jack Hill
2018-10-24 10:02     ` Ludovic Courtès
2018-10-24 14:21       ` Alex Griffin
2018-10-26 21:36         ` Tonton
2018-10-26 22:37           ` Alex Griffin
2018-10-28 18:42             ` Tonton
2018-10-28 19:50               ` Alex Griffin [this message]
2018-10-28 20:25                 ` Alex Griffin
2018-10-28 21:12                 ` Thorsten Wilms
2018-10-28 21:26                 ` Alex Griffin
2018-10-29  8:59                 ` Björn Höfling
2018-10-29 10:49                   ` Thorsten Wilms
2018-10-29 13:43                     ` Alex Griffin
2018-10-29 17:48                     ` Christopher Lemmer Webber
2018-10-30  7:48                       ` Patch submission should not imply agreement to policy (was Re: Promoting the GNU Kind Communication Guidelines?) Mark H Weaver
2018-10-30 13:28                         ` Christopher Lemmer Webber
2018-10-30 19:39                           ` Thorsten Wilms
2018-10-31  8:58                             ` Alex Sassmannshausen
2018-10-31 12:17                               ` Thorsten Wilms
2018-10-31 12:48                                 ` Alex Sassmannshausen
2018-10-31 11:17                           ` Mark H Weaver
2018-11-01  3:47                             ` Mark H Weaver
2018-10-31 20:51                         ` Thorsten Wilms
2018-10-29 22:58                 ` Promoting the GNU Kind Communication Guidelines? Tonton
2018-10-29 18:16             ` Cook, Malcolm
2018-10-24 10:23 ` Ludovic Courtès
2018-10-24 16:06   ` Mathieu Lirzin
2018-10-25 10:23   ` Ricardo Wurmus
2018-10-25 15:25     ` Mathieu Lirzin
2018-10-25 23:03     ` George Clemmer
2018-10-26  2:43       ` Gábor Boskovits
2018-10-26 21:25         ` Alex Griffin
  -- strict thread matches above, loose matches on Subject: below --
2018-10-28 11:58 HiPhish
2018-10-28 12:33 ` Gábor Boskovits
2018-10-28 16:14   ` Alex Griffin
2018-10-28 20:55   ` Thorsten Wilms
2018-10-29 11:27     ` Alex Sassmannshausen
2018-10-29 17:00       ` Thorsten Wilms
2018-10-29 17:50         ` Ricardo Wurmus
2018-10-29 11:29   ` Alex Sassmannshausen
2018-10-29  8:23 ` Björn Höfling
2018-10-29 10:10   ` Thorsten Wilms
2018-10-29 11:13     ` Alex Sassmannshausen
2018-10-29 17:15       ` Thorsten Wilms
2018-10-29 17:43         ` Ricardo Wurmus
2018-10-29 20:44     ` Björn Höfling
2018-10-29 11:08 ` Alex Sassmannshausen
2018-10-29 18:50   ` HiPhish
2018-10-29 23:54     ` Tonton
2018-10-30  0:38       ` HiPhish
2018-10-30  5:13         ` Nils Gillmann
2018-10-31  9:27     ` Alex Sassmannshausen
2018-10-31 12:29       ` HiPhish
2018-10-31 12:46         ` Alex Sassmannshausen
2018-10-31 13:23           ` HiPhish
2018-10-31 14:14             ` Jelle Licht
2018-10-31 14:55               ` HiPhish
2018-10-31 12:30       ` HiPhish
2018-10-31 13:48         ` Jelle Licht
2018-10-31 14:55           ` HiPhish
2018-10-31 17:17             ` Thorsten Wilms
2018-11-01 10:35             ` Mark H Weaver
2018-10-31 13:48         ` Thomas Danckaert
2018-10-31 14:06           ` Alex Griffin
2018-10-31 14:55           ` HiPhish
2018-10-31 16:41             ` Thorsten Wilms
2018-11-01  2:58             ` Mark H Weaver
2018-11-01  9:14         ` Mark H Weaver
2018-11-01  8:40       ` Steffen Schulz
2018-10-29 12:48 ` Giovanni Biscuolo
     [not found]   ` <9066320.aHiQMI0tiE@aleksandar-ixtreme-m5740>
2018-10-29 18:49     ` HiPhish
2018-10-28 23:37 HiPhish
2018-10-30  0:46 Alex Griffin
2018-10-30  2:09 ` Alex Griffin

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181028195054.GA10708@antares.lan \
    --to=a@ajgrf.com \
    --cc=guix-devel@gnu.org \
    --cc=tonton@riseup.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).