From: Vagrant Cascadian <vagrant@debian.org>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Documentation of what is appropriate for #guix?
Date: Sun, 20 Feb 2022 10:36:30 -0800 [thread overview]
Message-ID: <87zgmlpeq9.fsf@contorta> (raw)
In-Reply-To: <17f1532c56f.117a0ef0f577876.7300060614750291105@excalamus.com>
[-- Attachment #1: Type: text/plain, Size: 2792 bytes --]
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...
So yes, linking to the Free System Distribution Guidelines implies what
is off-topic, though is still maybe not targeted towards online
communications; it more appears to be written with the audience of
someone making a free software distribution or auditing one. It seems
like the most relevent passage is:
"A free system distribution must not steer users towards obtaining any
nonfree information for practical use, or encourage them to do so. The
system should have no repositories for nonfree software and no
specific recipes for installation of particular nonfree programs. Nor
should the distribution refer to third-party repositories that are not
committed to only including free software; even if they only have free
software today, that may not be true tomorrow. Programs in the system
should not suggest installing nonfree plugins, documentation, and so
on."
People often miss the part about not indirectly referring to non-free
software. Even if pointed to the FSDG, it is admittedly a bit hard to
grasp at times just what exactly constitutes "steer users towards
obtaining any nonfree information for practical use" or how it applies
to, say IRC. Individuals in IRC are not "the distribution", though the
new and long-time community members obviously make up perhaps the most
imporant part of the distribution.
I only bring this up because I regularly see this come up in the IRC
channel, and if an issue frequently comes up, usually that is a sign
that something could be improved in documentation, website, tooling,
etc. ... and when asked for one, I didn't have a good summary to point
to in my toolbox.
Maybe it is now my job to propose something concrete, but I was
curious what others thought before diving into details. :)
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-02-20 18:37 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 [this message]
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=87zgmlpeq9.fsf@contorta \
--to=vagrant@debian.org \
--cc=guix-devel@gnu.org \
--cc=matt@excalamus.com \
/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.