unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, HiPhish <hiphish@posteo.de>
Subject: Re: Stop it. Formerly - Re: Promoting the GNU Kind Communication Guidelines?
Date: Thu, 01 Nov 2018 22:04:30 -0400	[thread overview]
Message-ID: <87muqsmdyu.fsf@netris.org> (raw)
In-Reply-To: <87wopwuah2.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Thu, 01 Nov 2018 15:40:57 +0100")

Hi Ludovic,

ludo@gnu.org (Ludovic Courtès) writes:

> Leo Famulari <leo@famulari.name> skribis:
>
>> On Wed, Oct 31, 2018 at 04:41:53PM +0100, Pjotr Prins wrote:
>>> I suggest to end this thread. HiPhish, come and discuss your points at
>>> FOSDEM. We'll set up a working group for those who care about these
>>> things.
>>
>> I agree. The subject has been discussed ad nauseam across the internet,
>> and even offline, and we are not going to achieve a breakthrough here on
>> the Guix mailing list.
>
> +1.

I'm unable to travel to FOSDEM this year, so moving the discussion there
would effectively exclude me from participating in it.

> Furthermore, this project, like any other, has its license, its rules,
> etc.  Of course we can discuss these things together, it’s what makes a
> project healthy.

Agreed.

> However, when joining the project, one agrees to follow these rules

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.

I'm still waiting for someone to explain why it's important for us to
obtain "agreement" with our policies from all participants.

It would be like a restaurant asking every customer to sign an agreement
before entering, forcing them to agree in advance to a list of rules,
e.g. that they won't harass the other customers.  There's no need for
it, and it's needlessly alienating.  It's more than enough to simply
have a list of rules posted in public view, and to enforce the rules as
the need arises.

      Mark

  parent reply	other threads:[~2018-11-02  2:05 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 [this message]
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
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

  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=87muqsmdyu.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=hiphish@posteo.de \
    --cc=ludo@gnu.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.
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).