From: Chris Marusich <cmmarusich@gmail.com>
To: swedebugia <swedebugia@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Code of Conduct and Diversity Statement
Date: Sun, 13 May 2018 13:29:56 -0700 [thread overview]
Message-ID: <87zi13nvsr.fsf@gmail.com> (raw)
In-Reply-To: <6A4B9D18-8276-4B3F-B9A9-EADBA72990A7@riseup.net> (swedebugia@riseup.net's message of "Sun, 13 May 2018 09:22:06 +0200")
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
swedebugia <swedebugia@riseup.net> writes:
> 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)
GNU Guix does have some maintainers. Currently, they are Ludovic
Courtès and Ricardo Wurmus. This is mentioned here:
https://www.gnu.org/software/guix/about/
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-05-13 22:37 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
2018-05-13 20:29 ` Chris Marusich [this message]
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=87zi13nvsr.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--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 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.