all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matt <matt@excalamus.com>
To: "Vagrant Cascadian" <vagrant@debian.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Documentation of what is appropriate for #guix?
Date: Sat, 19 Feb 2022 22:35:23 -0500	[thread overview]
Message-ID: <17f1532c56f.117a0ef0f577876.7300060614750291105@excalamus.com> (raw)
In-Reply-To: <87tucujmgk.fsf@contorta>


 ---- 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



  parent reply	other threads:[~2022-02-20  3:36 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 [this message]
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=17f1532c56f.117a0ef0f577876.7300060614750291105@excalamus.com \
    --to=matt@excalamus.com \
    --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.