From: Yasuaki Kudo <yasu@yasuaki.com>
To: guix-devel@gnu.org
Subject: Re: Documentation of what is appropriate for #guix?
Date: Sun, 20 Feb 2022 11:41:23 +0900 [thread overview]
Message-ID: <923d6980-75a1-a33c-8883-ba8ff52bd245@yasuaki.com> (raw)
In-Reply-To: <87tucujmgk.fsf@contorta>
Or even better, create an alternative community of practitioners who
don't give a damn (for their purposes)... Let me know if other people
also want to create a corruption-admitted-community as well 😁. We can
work together. -Yasu
On 2/20/22 11:33, Vagrant Cascadian 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 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
next prev parent reply other threads:[~2022-02-20 2:41 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 [this message]
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
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=923d6980-75a1-a33c-8883-ba8ff52bd245@yasuaki.com \
--to=yasu@yasuaki.com \
--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 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).