all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: elais@fastmail.com
To: Paul Jewell <paul@teulu.org>, Yasuaki Kudo <yasu@yasuaki.com>
Cc: guix-devel@gnu.org
Subject: Re: Documentation of what is appropriate for #guix?
Date: Tue, 22 Feb 2022 10:39:01 -0700	[thread overview]
Message-ID: <16c89886-effa-4426-bb86-59055d4f8d6a@Spark> (raw)
In-Reply-To: <3DE50B35-F5C5-4BC9-8908-1B220181AE93@yasuaki.com>

[-- Attachment #1: Type: text/plain, Size: 4415 bytes --]

> If we were to set up a separate relaxed Guix
> community that accommodates all forms of corruption, one problem would be the impediments that would exist in communication, especially if the original Guix takes hostile and non-compromising attitude, I think.

The discussion at hand is about clarifying what is on topic new channel users, not relaxing a commitment to not promote non free software. A few seconds of searching will almost definitely turn up alternatives if that’s what you’re looking for. That being said I think it would be helpful to add a few sentences to the chat on irc page[1] that clearly state that discussion of non free software is off topic and discouraged in the Channel. I think it will also help if we add the same message to the contacts page[2] as well.

1. https://guix.gnu.org/en/contact/irc/
2. https://guix.gnu.org/contact/


-- Elais Player

On Feb 22, 2022, 04:48 -0700, Yasuaki Kudo <yasu@yasuaki.com>, wrote:
> If we were to set up a separate relaxed Guix community that accommodates all forms of corruption, one problem would be the impediments that would exist in communication, especially if the original Guix takes hostile and non-compromising attitude, I think.
>
> If a question arises from that downgraded community how to do this and that, precisely to accommodate some unaccountable  binary black box software, the chances of getting helpful answers may not be so high from the original Guix community. 😅
>
> It is a difficult question - even in the real world the similarities abound.   While it is easy to ignore and isolate North Korea, a country that offers no useful commodity for export (or maybe it does, but let's say, for the sake of argument), countries like Japan have no problem importing Saudi Arabian oil. Ethics and human rights are thrown out the window - oil is considered far more important.
>
> I tend to take the position of strategically 'not caring'  (e.g. https://youtu.be/Blz_Eu00Kbw )
>
> Maybe someone like me is called a Libertarian?  I am not sure... (for the record, my political philosophy seems to be called Anarcho-Syndicalism 😄)
>
> But I still think a parallel community might be in order 😄
>
> -Yasu
>
>
> > On Feb 22, 2022, at 07:36, Paul Jewell <paul@teulu.org> wrote:
> >
> >
> >
> > > 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

[-- Attachment #2: Type: text/html, Size: 6862 bytes --]

  reply	other threads:[~2022-02-22 17:52 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16c89886-effa-4426-bb86-59055d4f8d6a@Spark \
    --to=elais@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=paul@teulu.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 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.