all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: HiPhish <hiphish@posteo.de>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Stop it. Formerly - Re: Promoting the GNU Kind Communication Guidelines?
Date: Tue, 06 Nov 2018 18:41:42 +0100	[thread overview]
Message-ID: <2768755.l9fGuyXQlC@aleksandar-ixtreme-m5740> (raw)
In-Reply-To: <87lg66p1b7.fsf@fastmail.com>

I think you are focusing too much on the "pledge" part. Submitting a patch is 
an informal process and I doubt anyone is going to hold it up against you in a 
court. This is just an instance of using fancy words to sound important. 

People's real grievances with the CC are that it polices people outside the 
project as well (simply abiding by the rules on the mailing list and IRC is 
not enough, according to the terms of the CC), its focus on punishment, 
presumption of malice and of course the author of the CC and the surrounding 
culture. Getting hung up on details like the word "pledge" is just going to 
burn people out, but will not resolve anything.

On Tuesday, 6 November 2018 18:23:40 CET Marius Bakke wrote:
> Mark H Weaver <mhw@netris.org> writes:
> > While I generally agree with the policies outlined in our CoC, and I
> > support the practice of enforcing those policies through our control
> > over our infrastructure and communications channels, I strongly oppose
> > requiring or presuming that all participants "agree" with our policies,
> > which I take to mean "declaring that they share the same opinions and
> > goals".
> > 
> > Some participants may disagree with our policies, and that's okay.
> > We don't need their agreement to enforce our policies.
> > 
> > Forcing people to declare their agreement with our policies as a
> > prerequisite for participation, or worse, _presuming_ that they agree
> > based on their having sent a patch or posted a message, is needlessly
> > alienating to those who don't share our views.
> 
> Thank you Mark for succinctly pointing out these flaws in our current
> CoC.  I agree that the language is overreaching, and think that these
> discussions will continue to crop up as long as this wording is
> included.
> 
> Our usage of the Contributor Covenant have deterred at least three
> contributors.  I hope it has attracted and retained more than that; in
> any case I think we can do better.
> 
> Also thanks to Thorsten for filing
> <https://github.com/ContributorCovenant/contributor_covenant/issues/624>.
> Getting this fixed upstream will benefit much more than the Guix project.

  reply	other threads:[~2018-11-06 17:42 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28 11:58 Promoting the GNU Kind Communication Guidelines? 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 23:54         ` OF-TOPIC: " Tonton
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 15:41                 ` Stop it. Formerly - " Pjotr Prins
2018-10-31 17:51                   ` Leo Famulari
2018-11-01 14:40                     ` Ludovic Courtès
2018-11-01 15:11                       ` Alex Griffin
2018-11-02  2:04                       ` Mark H Weaver
2018-11-04  9:15                         ` Mark H Weaver
2018-11-04 14:30                           ` HiPhish
2018-11-04 21:01                           ` Thorsten Wilms
2018-11-06 12:55                         ` Ludovic Courtès
2018-11-06 17:23                         ` Marius Bakke
2018-11-06 17:41                           ` HiPhish [this message]
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 11:37 ` Promoting the GNU Kind Communication Guidelines? (-> convivenza) Nils Gillmann
2018-10-29 11:45   ` Nils Gillmann
2018-10-29 12:01   ` Alex Sassmannshausen
2018-10-29 12:48 ` Promoting the GNU Kind Communication Guidelines? Giovanni Biscuolo
     [not found]   ` <9066320.aHiQMI0tiE@aleksandar-ixtreme-m5740>
2018-10-29 18:49     ` HiPhish
  -- strict thread matches above, loose matches on Subject: below --
2018-11-06  1:19 Stop it. Formerly - " Jeremiah

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=2768755.l9fGuyXQlC@aleksandar-ixtreme-m5740 \
    --to=hiphish@posteo.de \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.