From: Mathieu Lirzin <mthl@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Promoting the GNU Kind Communication Guidelines?
Date: Wed, 24 Oct 2018 18:06:45 +0200 [thread overview]
Message-ID: <87zhv39vmy.fsf@gnu.org> (raw)
In-Reply-To: <8736sv7iex.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 24 Oct 2018 12:23:02 +0200")
Hello Ludo,
ludo@gnu.org (Ludovic Courtès) 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.
I am sad that you feels that the GKCG is not sufficient for defining the
acceptable behavior of the members of a Free Software community.
>> 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].
>
> Codes of conduct codify acceptable behavior and formalize processes:
> what can I do as a contributor if I’m a victim bad behavior or
> harassment? What are the group communication rules? What if I
> knowingly break those rules?
>
> By adopting the code of conduct, we maintainers committed to spend our
> time as needed to so your experience contributing to Guix won’t be a
> source of stress or worse, as is too often the case in on-line
> communities.
>
> The GKCG do not do that. Problems will be dealt with in an ad hoc
> fashion (as they already are in groups that have not codified rules), if
> they are addressed at all.
>
> I hope this answers your question.
Yes it does perfectly.
I personnaly think dealing with such issues in an ad hoc fashion is the
right approach when acceptable behaviors are the norm, which IME has
been the case.
Anyway I still hope that the Guix community will eventually accept the
GKCG as an acceptable tradeoff in the CoC debate.
Thanks.
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
next prev parent reply other threads:[~2018-10-24 16:19 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 [this message]
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=87zhv39vmy.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=guix-devel@gnu.org \
--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).