unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tonton <tonton@riseup.net>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Code of Conduct and Diversity Statement
Date: Sun, 13 May 2018 02:27:22 +0200	[thread overview]
Message-ID: <20180513022722.1b2349ef@merlin.browniehive.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1798 bytes --]

Hi,

I've recently been reading a lot about codes of conduct, inclusion,
diversity, and similar topics - mainly in perspective of informatics
communities and free software.

I originally thought I'd find and propose a code of conduct because I wasn't
aware Guix had one. But I did find one when I grepped the sources. This
raises the first question: 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?

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)?

The recurse center/hackerschool [manuals](https://www.recurse.com/manual)
section on "social rules" is also much recommended, the whole document is
quite good. For anyone interested in the topic.

I'd be happy to provide more resources, seeing as I've spent the better part
of a week researching this (I binge read when I find something interesting :).

Would like to say that this is probably the best informatics community I've
been part of and the reason I'm bringing it up is to make a statement that we
care, and to make it easier for outsiders and potential participants to see
that this is in fact part of our backbone. I'm so often positively surprised
by the quality of communication here.

-- 
I use gpg to sign my emails. All the symbols you may see at the bottom
of this mail is my cryptographic signature. It can be ignored, or used
to check that it really is me sending this email. Learn more by asking
me or see: https://u.fsf.org/zb or https://ssd.eff.org/

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-05-13  0:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13  0:27 Tonton [this message]
2018-05-13  3:37 ` Code of Conduct and Diversity Statement 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
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=20180513022722.1b2349ef@merlin.browniehive.net \
    --to=tonton@riseup.net \
    --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).