From: Bengt Richter <bokr@bokr.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: How would packaging Steam-proton games be received?
Date: Sat, 9 Jan 2021 10:47:17 +0100 [thread overview]
Message-ID: <20210109094717.GA19276@LionPure> (raw)
In-Reply-To: <X+4sNJ3n+BTyRmCg@jasmine.lan>
O Ye of little Faith, please read:
https://puri.sm/posts/the-future-of-software-supply-chain-security/
(It really is worth a read ;)
On +2020-12-31 14:53:24 -0500, Leo Famulari wrote:
> Hi Josh,
>
> I'm replying off-list, because this subject has been discussed soooo
> many times without reaching a different conclusion, and because I worry
> about starting a flamewar on the mailing list.
>
> On Thu, Dec 31, 2020 at 02:12:16PM -0500, Josh Marshall wrote:
> > So a separate channel would work for non-free software? I know the stuff
> > is fundamentally gross. I'd still like to have a better way to get out of
> > an ecosystem that is basically entirely all non-free software and a
> > transition to fully free becomes possible.
>
> If we think about free software in terms of the "4 freedoms" [0],
> channels are a fully-supported way to help people take advantage of the
> "zero-eth freedom", which is the freedom to use the software (Guix) as
> one sees fit.
>
> Personally, I think that ensuring an operating system is 100% free
> software (and with no DRM support) hampers the success of the free
> software movement by driving away users.
>
> If we lived in a world with free software support for common hardware
> (ahem, WiFi, Bluetooth, LTE) and for popular software use cases (popular
> games and apps, commercial and educational software), then offering a
> totally free system would be a viable approach.
>
> But, that world doesn't exist. Even though some people who are happy to
> use 10+ year old computers for very limited use cases might think it
> does... many of them don't even use mobile phones... they don't
> understand contemporary computing at all, from a practical perspective.
>
> Nevertheless, the GNU Guix project has made a commitment to working
> within the FSDG, and we are basically stuck with it barring some
> cataclysmic change.
>
> I think that maintaining a harmonious atmosphere within Guix will help
> it continue to grow, and channels can satisfy the need for things that
> don't fit the FSDG. If Guix becomes large enough, it could be
> transformative for the free software movement.
>
> [0]
> https://www.gnu.org/philosophy/free-sw.en.html
--
Regards,
Bengt Richter
next prev parent reply other threads:[~2021-01-09 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 18:09 How would packaging Steam-proton games be received? Josh Marshall
2020-12-31 18:54 ` Christopher Baines
2020-12-31 18:56 ` Leo Famulari
2020-12-31 19:12 ` Josh Marshall
2020-12-31 19:53 ` Leo Famulari
2020-12-31 21:07 ` Leo Famulari
2021-01-09 9:47 ` Bengt Richter [this message]
2020-12-31 19:55 ` Leo Famulari
2020-12-31 20:36 ` Josh Marshall
2020-12-31 20:50 ` Ryan Prior
2020-12-31 20:55 ` Josh Marshall
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=20210109094717.GA19276@LionPure \
--to=bokr@bokr.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).