From: Nils Gillmann <ng0@n0.is>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Code of Conduct and Diversity Statement
Date: Sun, 13 May 2018 07:35:41 +0000 [thread overview]
Message-ID: <20180513073541.zja6iy3rsagexndl@abyayala> (raw)
In-Reply-To: <6A4B9D18-8276-4B3F-B9A9-EADBA72990A7@riseup.net>
swedebugia transcribed 1.7K bytes:
> Hi
>
> On May 13, 2018 2:27:22 AM GMT+02:00, Tonton <tonton@riseup.net> wrote:
> >Hi,
> >
> ...
> > 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?
>
> Yes I think so. I like you proposals. I knew we had one and found it via the manual.
>
> >
> >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)?
>
> This community does not really have any maintainers or formal leadership to my knowledge.
> How to handle reporting in our case could be handled by here by vote appointing a person to handle such issues (for example as a mediator like in https://www.noisebridge.net/wiki/Conflict_Resolution)
Here's another group working on "Guidelines for Moderators of Coexistence".
Their document is well-written and now translated in 3 languages:
https://structure.pages.de/convivenza.en
> >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 agree. Conflicts here seem rare and to my knowledge well handled when they do.
>
> Cheers
> Swedebugia
next prev parent reply other threads:[~2018-05-13 7:35 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
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 [this message]
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=20180513073541.zja6iy3rsagexndl@abyayala \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=swedebugia@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 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).