all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Subject: Documentation of what is appropriate for #guix?
Date: Sat, 19 Feb 2022 18:33:47 -0800	[thread overview]
Message-ID: <87tucujmgk.fsf@contorta> (raw)

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

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 figured maybe it is referenced in the code of conduct, but then I see
no reference to the code of conduct on https://guix.gnu.org, although it
is in the toplevel directory of guix.git as "CODE-OF-CONDUCT".

Still, the CODE-OF-CONDUCT doesn't really say anything about what is
on-topic for #guix on irc...

It would be helpful to have a link to be able to point to more easily
whenever either subjects come up in the irc channel, ideally somewhere a
little easier to find. :)


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

             reply	other threads:[~2022-02-20  2:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20  2:33 Vagrant Cascadian [this message]
2022-02-20  2:41 ` Documentation of what is appropriate for #guix? 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

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