unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Jewell <paul@teulu.org>
To: raingloom <raingloom@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: Documentation of what is appropriate for #guix?
Date: Mon, 21 Feb 2022 22:19:08 +0000	[thread overview]
Message-ID: <746FC12F-B974-4A59-83CF-8FA848795D37@teulu.org> (raw)
In-Reply-To: <20220221200908.632ddf85@riseup.net>



> On 21 Feb 2022, at 19:10, raingloom <raingloom@riseup.net> 

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

I understand that the position taken by guix is more nuanced than that. The project doesn’t seek to control what you run on your computer, but won’t support your choice to run non-free software in the official channels. 

> 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?
But you can discuss these results elsewhere.

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

I kind of agree with you here. I don’t want to obsolete perfectly viable hardware, but instead want to use it for its whole life. Next time I am in the market for new hardware, then I will have the ability to run libre-software as a pre-condition for purchase.

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

Users will find it even the way it is configured today. I don’t think it needs any sort of official recognition or promotion, as that will go against the project goals/rules (as I understand it). We should always be aware of the insidious nature of proprietary firmware/software, and work to eliminate the need for it, rather than indicating that its use is acceptable as a first choice.


Best regards,
Paul


  reply	other threads:[~2022-02-21 22:19 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 [this message]
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=746FC12F-B974-4A59-83CF-8FA848795D37@teulu.org \
    --to=paul@teulu.org \
    --cc=guix-devel@gnu.org \
    --cc=raingloom@riseup.net \
    /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).