From: raingloom <raingloom@riseup.net>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: guix-devel@gnu.org
Subject: Re: Documentation of what is appropriate for #guix?
Date: Mon, 21 Feb 2022 20:09:08 +0100 [thread overview]
Message-ID: <20220221200908.632ddf85@riseup.net> (raw)
In-Reply-To: <923d6980-75a1-a33c-8883-ba8ff52bd245@yasuaki.com>
On Sun, 20 Feb 2022 11:41:23 +0900
Yasuaki Kudo <yasu@yasuaki.com> wrote:
> 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
>
Something like that already exists for The Channel That May Not Be
Named.
By the way, I think it's kind of silly that that is completely banned
from discussion. When I wanted help on getting my GPU to work, I
mentioned for reference purposes that I tried the proprietary driver
from The Forbidden Channel - and was subsequently warned that I must
not do that. Which I find ridiculous. You can't even discuss results
obtained by running closed source drivers and firmware, so how do you
debug the libre firmwares and drivers, when you have nothing to compare
against?
Also, I think people who want to overwhelmingly use free software but
need proprietary drivers for their computer to function should be
offered better help than "buy a new computer". Currently I'm a mostly
happy user of an AMDGPU based desktop, which lets me create creative
commons artwork in Blender, that I would not be able to do without
proprietary firmware.
I think The Forbidden Channel should be raised to a status similar to
the AUR: it's recognized and its existence is documented, but all
responsibility is very explicitly disclaimed and support is relegated
to special channels.
next prev parent reply other threads:[~2022-02-21 19:09 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 [this message]
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=20220221200908.632ddf85@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@gnu.org \
--cc=yasu@yasuaki.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 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).