From: Kei Kebreau <kkebreau@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Code of Conduct and Diversity Statement
Date: Sun, 13 May 2018 20:21:19 -0400 [thread overview]
Message-ID: <87a7t3ulxc.fsf@posteo.net> (raw)
In-Reply-To: <87k1s7jkdp.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 13 May 2018 23:50:10 +0200")
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
>
> 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’.
I'm also in favor of the move to version 1.4.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-05-14 6:11 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 [this message]
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=87a7t3ulxc.fsf@posteo.net \
--to=kkebreau@posteo.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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).