From: Mathieu Lirzin <mthl@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: NEWS for 0.10.0
Date: Sun, 27 Mar 2016 23:38:04 +0200 [thread overview]
Message-ID: <87twjrvbyb.fsf@gnu.org> (raw)
In-Reply-To: <87h9fryfub.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 27 Mar 2016 19:45:48 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> diff --git a/NEWS b/NEWS
> index ec92990..0e907ba 100644
> --- a/NEWS
> +++ b/NEWS
[...]
> -* Changes in 0.9.1 (since 0.9.0)
> +* Changes in 0.10.0 (since 0.9.0)
> +
> +GNU Guix adopted a contributor code of conduct, see ‘CODE-OF-CONDUCT’ in the
> +source tree.
I think it would be reasonable to integrate this news in the current
scheme by not making it top level. What about moving this news in a
category "Contribution" or "Community"?
While speaking about code of conducts I have found sometimes ago an
alternative version which achieves the same expected effect as the
current one but in a more consensual way:
https://wiki.gnome.org/action/show/Foundation/CodeOfConduct?action=show&redirect=CodeOfConduct
Even if I know I belong to the minority who disagree with the
“Contributor Covenant” ideas, I think GNOME code of conduct would fit
better in Guix because it will not associate GNU with a movement using
the term “Open Source” and promoting Github usage.
WDYT?
Thanks,
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-03-27 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 17:45 NEWS for 0.10.0 Ludovic Courtès
2016-03-27 21:38 ` Mathieu Lirzin [this message]
2016-03-28 16:36 ` Ludovic Courtès
2016-03-30 2:01 ` Rastus Vernon
2016-03-30 2:39 ` Jookia
2016-03-30 8:52 ` Taylan Ulrich Bayırlı/Kammer
2016-03-30 11:02 ` Tobias Geerinckx-Rice
2016-03-30 17:28 ` John Darrington
2016-03-30 20:17 ` Taylan Ulrich Bayırlı/Kammer
2016-03-30 21:22 ` Ludovic Courtès
2016-03-27 21:41 ` Leo Famulari
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=87twjrvbyb.fsf@gnu.org \
--to=mthl@gnu.org \
--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).