unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Code of Conduct and Diversity Statement
Date: Sun, 13 May 2018 23:50:10 +0200	[thread overview]
Message-ID: <87k1s7jkdp.fsf@gnu.org> (raw)
In-Reply-To: <87lgcody3t.fsf@gmail.com> (Chris Marusich's message of "Sat, 12 May 2018 20:37:58 -0700")

Hello!

Chris Marusich <cmmarusich@gmail.com> skribis:

> Tonton <tonton@riseup.net> writes:
>
>> Should we make the CoC more prominent or somehow inform about it
>> better? For example by putting it or a link to it in the topic of the
>> IRC channel, as it's own page on the website, if possible as part of
>> the welcome message to the mailing lists, others?
>
> I think those are good ideas.  I'd be curious to hear what Ludo and
> Ricardo think.
>
> We mention the Code of Conduct in the manual (see: "(guix)
> Contributing").  However, you're right that it seems we don't
> prominently mention it on the website.

Sure, perhaps we should mention it at the top of
<https://www.gnu.org/software/guix/contribute/> and/or link to
<https://www.gnu.org/software/guix/manual/html_node/Contributing.html>?

> While we wait for Ludo and Ricardo to reply, perhaps you could submit a
> patch that implements the changes you're suggesting?

That’d be great!

>> A second question is, the contributor covenant has evolved, should we upgrade
>> ours from 1.3.0 to the current
>> [1.4.0](https://www.contributor-covenant.org/version/1/4/code-of-conduct)?
>
> To help people understand what has changed going from 1.3.0 to 1.4, here
> is a handy command you can use to get a visual diff of the versions:
>
>   wdiff -n -w $'\033[30;41m' -x $'\033[0m' -y $'\033[30;42m' -z $'\033[0m' \
>   <(curl https://www.contributor-covenant.org/version/1/3/0/code-of-conduct.txt) \
>   <(curl https://www.contributor-covenant.org/version/1/4/code-of-conduct.txt) \
>   | less -R

As I see it, the new version is more clearly structured, clarifies the
wording in some places, and introduces a distinction between “project
team” and “project maintainers”.  Perhaps we’d need to clarify what the
“project team” is in our case (?).

Apart from this, I think 1.4 follows the spirit of 1.3.0 and its
clarifications are welcome, so I’d be in favor of “upgrading”.

What do people think?

Thanks for sharing your thoughts, Tonton!

Ludo’.

  parent reply	other threads:[~2018-05-13 22:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13  0:27 Code of Conduct and Diversity Statement Tonton
2018-05-13  3:37 ` Chris Marusich
2018-05-13 12:47   ` Resources around inclusion, diversity, conduct and harrasment (was Re: Code of Conduct and Diversity Statement) Tonton
2018-05-13 21:50   ` Ludovic Courtès [this message]
2018-05-14  0:21     ` Code of Conduct and Diversity Statement Kei Kebreau
2018-05-14  8:25     ` Clément Lassieur
2018-05-17  6:26   ` Chris Marusich
2018-05-24 16:31     ` Leo Famulari
2018-05-24 17:13       ` Tobias Geerinckx-Rice
2018-05-29 16:32         ` Ludovic Courtès
2018-05-30  7:09           ` Ricardo Wurmus
2018-05-13  7:22 ` swedebugia
2018-05-13  7:35   ` Nils Gillmann
2018-05-13 20:29   ` Chris Marusich
2018-05-13  8:08 ` Pierre Neidhardt

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=87k1s7jkdp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@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).