unofficial mirror of guix-devel@gnu.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: Sun, 20 Feb 2022 16:39:13 -0500	[thread overview]
Message-ID: <17f19130f0e.b18e371c614957.2840578072764301740@excalamus.com> (raw)
In-Reply-To: <87zgmlpeq9.fsf@contorta>


 ---- On Sun, 20 Feb 2022 13:36:30 -0500 Vagrant Cascadian <vagrant@debian.org> wrote ----

 > I admittedly forget to check the messages from chanserv for channels I
 > frequent regularly, having personally grown accustomed to the norms of
 > the channel...
 
In my opinion, it's easy to miss.  I had to actively look for it.  I use Emacs erc.  When I start that program and log in, I'm in a buffer for "Libera.Chat". I then do /join #guix. This opens a new buffer, hiding the "Libera.Chat" buffer and showing a new "#guix@Libera.Chat"   buffer. The ChanServ message is printed to the buried "Libera.Chat" buffer.  The "#guix@Libera.Chat" buffer on connect has a giant wall of text showing who's in the chat.  It causes the buffer to scroll to the bottom, hiding anything printed to the top.  Scrolling up, I see some links to various topics. I see no rules or guidelines there.
 
 > 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 agree, it's hard to miss within the FSDG. Aside from linked (and not on a main screen), it's several sections down within the FSDG. 

 > 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. :)

I think your observation matches what I've seen and I think your suggestion to address the problem makes sense.  If you know how to and where to do this, great. I wish I could be of more help.  I'm only able to cheer you on and give opinions.


  reply	other threads:[~2022-02-20 21:39 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 [this message]
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=17f19130f0e.b18e371c614957.2840578072764301740@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 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).