all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Tonton <tonton@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] website: Add section section and links to code of conduct
Date: Thu, 17 May 2018 13:43:17 +0200	[thread overview]
Message-ID: <87k1s21p9m.fsf@gnu.org> (raw)
In-Reply-To: <20180516022954.4809d80d@merlin.browniehive.net> (tonton@riseup.net's message of "Wed, 16 May 2018 02:29:54 +0200")

Hello,

Tonton <tonton@riseup.net> skribis:

> First this something we would like - to have the
> CoC as a section just like we have the section Building from Git
> (https://www.gnu.org/software/guix/manual/html_node/Building-from-Git.html#Building-from-Git)?
> I could also add it as a subsection of contributing, making it part of the
> landing. But it seemed better to me to have it separately, maybe.

I’m unsure about adding a complete copy of the Code in the manual; I’d
prefer keep the URL and a reference to the ‘CODE-OF-CONDUCT’ file.

Thoughts?

Also, to be clear, I wanted to leave a few days before updating to
version 1.4 of the Contributor Covenant so that people have a chance to
speak (a few days have passed already so it looks like we’re on the
right track :-)), and to have Ricardo’s agreement as well as
co-maintainer.

Thanks,
Ludo’.

  parent reply	other threads:[~2018-05-17 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 23:36 [PATCH] website: Add section section and links to code of conduct Tonton
2018-05-16  0:29 ` Tonton
2018-05-16 15:14   ` Nils Gillmann
2018-05-16 16:17     ` Tonton
2018-05-17 11:43   ` Ludovic Courtès [this message]
2018-05-17 13:13     ` Tonton
2018-05-17 21:28     ` Ricardo Wurmus
2018-05-16 15:06 ` Fwd: " rain1
2018-05-16 16:05   ` Tonton
2018-05-17 11:48     ` Ludovic Courtès

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=87k1s21p9m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=tonton@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.