From: Chris Marusich <cmmarusich@gmail.com>
To: Tonton <tonton@riseup.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Code of Conduct and Diversity Statement
Date: Wed, 16 May 2018 23:26:07 -0700 [thread overview]
Message-ID: <87a7sydchs.fsf@gmail.com> (raw)
In-Reply-To: <87lgcody3t.fsf@gmail.com> (Chris Marusich's message of "Sat, 12 May 2018 20:37:58 -0700")
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
Chris Marusich <cmmarusich@gmail.com> writes:
>> 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
From my reading of the diff, these are the main changes:
* Make the code more inclusive (e.g., change "sexual orientation" to
"sexual identity and orientation").
* Clarify that the code applies not only to the "project" but also to
the larger "community" surrounding it.
* Add multiple "examples of behavior that contributes to creating a
positive environment," such as "gracefully accepting constructive
criticism."
* Explicitly state that "project maintainers are responsible for
clarifying the standards of acceptable behavior".
* Add "examples of representing a project or community", such as "using
an official project e-mail address".
* Explicitly title each section to clarify the document structure.
* Instead of just the "maintainers", the "project team" as a whole is
now also "obligated to maintain confidentiality with regard to the
reporter of an incident."
These all seem like good improvements to me. I think we should upgrade
to 1.4!
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-05-17 6:26 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 ` Code of Conduct and Diversity Statement Ludovic Courtès
2018-05-14 0:21 ` Kei Kebreau
2018-05-14 8:25 ` Clément Lassieur
2018-05-17 6:26 ` Chris Marusich [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7sydchs.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=tonton@riseup.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 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.