all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Documentation of what is appropriate for #guix?
Date: Mon, 28 Feb 2022 14:10:35 +0100	[thread overview]
Message-ID: <87bkyrdtmc.fsf@gnu.org> (raw)
In-Reply-To: <87zgmlpeq9.fsf@contorta> (Vagrant Cascadian's message of "Sun, 20 Feb 2022 10:36:30 -0800")

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

Hello!

Vagrant Cascadian <vagrant@debian.org> skribis:

> On 2022-02-19, matt@excalamus.com wrote:
>>  ---- On Sat, 19 Feb 2022 21:33:47 -0500 Vagrant Cascadian <vagrant@debian.org> wrote ----
>>  > Every now and then someone stumbles into #guix and ask questions that
>>  > I've gleaned over time are off-topic (e.g. non-free software). While I
>>  > have a pretty good idea what is appropriate for the channel, it is not
>>  > clear to me where that is documentated.
>>
>> I see the following when I connect to #guix:
>>
>> -ChanServ- [#guix] Welcome to #guix, home of the GNU Guix project! | Be kind
>>            to everyone. Ground rules:
>>            <https://git.savannah.gnu.org/cgit/guix.git/tree/CODE-OF-CONDUCT> |
>>            Non-free software is off-topic:
>>            <https://www.gnu.org/distros/free-system-distribution-guidelines.html>
>>            | Leave messages with sneek: /msg sneek help
>
> I admittedly forget to check the messages from chanserv for channels I
> frequent regularly, having personally grown accustomed to the norms of
> the channel...

[...]

> Maybe it is now my job to propose something concrete, but I was
> curious what others thought before diving into details. :)

Yes, please propose!  :-)

For the record, the code of conduct is mentioned at
<https://guix.gnu.org/en/contribute/> but not at
<https://guix.gnu.org/en/contact/>.  As a first step, I propose to
address that with the patch below.

Thoughts?

Thanks,
Ludo’.


[-- Attachment #2: Type: text/x-patch, Size: 1284 bytes --]

diff --git a/website/apps/base/templates/contact.scm b/website/apps/base/templates/contact.scm
index 7ecd354..49d8393 100644
--- a/website/apps/base/templates/contact.scm
+++ b/website/apps/base/templates/contact.scm
@@ -35,6 +35,26 @@ channels|Bug reports|Help") #\|)
       (@ (class "page centered-block limit-width"))
       ,(G_ `(h2 "Contact"))
 
+      ,(G_
+        `(p
+          "We want to provide a warm, friendly, and harassment-free environment,
+           so that anyone can contribute to the best of their abilities.  To
+           this end our project uses a “Contributor Covenant”, which was adapted
+           from "
+          ,(G_ ((lambda (url)
+                  `(a (@ (href ,url)) ,url))
+                "https://contributor-covenant.org/"))
+          ".  You can find the full pledge in the "
+          ,(G_
+            `(a (@ (href "//git.savannah.gnu.org/cgit/guix.git/tree/CODE-OF-CONDUCT")
+                   (class "mono"))
+                "CODE-OF-CONDUCT"))
+          " file."))
+
+      ,(G_
+        `(p "Participation to the project communication channels listed below
+            is subject to this code of conduct."))
+
       ,@(map
 	 contact->shtml
 	 (context-datum context "contact-media"))))))

      parent reply	other threads:[~2022-02-28 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20  2:33 Documentation of what is appropriate for #guix? Vagrant Cascadian
2022-02-20  2:41 ` Yasuaki Kudo
2022-02-21 19:09   ` raingloom
2022-02-21 22:19     ` Paul Jewell
2022-02-22 11:47       ` Yasuaki Kudo
2022-02-22 17:39         ` elais
2022-02-20  3:35 ` Matt
2022-02-20 18:36   ` Vagrant Cascadian
2022-02-20 21:39     ` Matt
2022-02-28 13:10     ` Ludovic Courtès [this message]

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