unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Lirzin <mthl@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Thu, 25 Oct 2018 17:25:01 +0200	[thread overview]
Message-ID: <8736suvyk2.fsf@gnu.org> (raw)
In-Reply-To: <87va5q5nq7.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 25 Oct 2018 12:23:28 +0200")

Hello Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

>> Mathieu Lirzin <mthl@gnu.org> skribis:
>>
>>> Following the announcement made by RMS regarding the new GNU Kind
>>> Communication Guidelines (GKCG) [1], I would like to know if the Guix
>>> developpers in particular its maintainers would agree to adopt it in
>>> place of the current Code of Conduct (CoC)?
>>
>> Speaking for myself: no.  I think the GKCG fails to address important
>> issues, such as defining what’s acceptable and what’s not as well as
>> clear processes to address this.
>
> [Apologies for the delay; I’m currently traveling.]

No need to apology, your response is still prompt. :-)

> Adding to what Ludovic wrote, I also would not want to replace the
> current proven Contributor Covenant with the recently emerged GKCG.
> Using *both* of them would not be useful, I think, as I find our current
> CoC to be sufficient; using *only* the GKCG and dropping the existing
> CoC would be a mistake in my opinion, as our CoC describes a process
> which the GKCG does not.

AIUI the GKCG is an attempt to reconcile people of the GNU hackers
community which is has been fragmented by the CoC debate.

In order to reconcile, each “camp” has to make some tradeoffs.  Since
you are a CoC proponent, it is normal that you feel that the GKCG is not
as “good” as the CoC.  However I would really appreciate if you (and
Ludo) could seriously consider the GKCG “downsides” as an acceptable
tradeoff to help uniting GNU Hackers and move the GNU project as a whole
(not just the Guix project) towards what you consider the “right”
direction in the “harassment free” path.

>>> Adopting the GKCG instead of a CoC would help attracting people
>>> (like me) who agree to use a welcoming and respectful language which
>>> encourages everyone to contribute but are reluctant in contributing
>>> to any project following a CoC due to its punitive nature and the
>>> politics of its authors [2][3].
>
> To me the politics of the author(s) of the original or current version
> of the Contributor Covenant don’t play much of a role in prefering it as
> a practical guiding document for this community.  (I don’t know the
> author.)

Have you consider that it doesn't play a role because you basically
share similar political ideas as the author(s) without knowing/caring?
This is not intended as a critic, but just as an opportunity for you to
consider that your own political bias (which we humans all have) is not
universal and that maybe other “respectable” persons might not share it.

> I think I see how it could be seen as “punitive”, but I don’t share this
> assessment.  We all want what’s best for the project and the people who
> currently work on or consider working on it — to me the emergence of the
> GKCG is more evidence that this is true.  I hope that seeing these
> similarities in intent more than the differences in implementation will
> allow you to overcome your feeling of reluctance to contribute to Guix
> (and other projects that have decided to adopt a CoC).

As explain above, I don't think the CoC and GKCG has the same intent.
If it were the case that Guix choose to ignore this opportunity to
reconcile, I am sorry to say that my reluctance to contribute to Guix
would not diminish.

Thanks for you answer.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

  reply	other threads:[~2018-10-25 15:25 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
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 [this message]
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=8736suvyk2.fsf@gnu.org \
    --to=mthl@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.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).