From: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
To: "alírio eyng" <alirioeyng@gmail.com>
Cc: guix-devel@gnu.org, gnu-linux-libre@nongnu.org
Subject: Re: MAME emulator is giving incentive to use non-free software
Date: Tue, 5 Apr 2016 17:59:11 +0200 [thread overview]
Message-ID: <20160405175911.0307cc6d@top-laptop> (raw)
In-Reply-To: <CALkz57F-T1E+veEONCwkW9uRNgTD49HNpC1NUQDx2kBkm51vMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2885 bytes --]
On Sat, 2 Apr 2016 08:48:58 +0000
alírio eyng <alirioeyng@gmail.com> wrote:
> On 4/2/16, Denis 'GNUtoo' Carikli <GNUtoo@no-log.org> wrote:
> > Why not just requiring some documentation along the emulator that
> > documents at least one fully free software that can run on it.
> this is missing some complexity:
> we don't want something better done natively (we exclude
> ndiswrapper)[1] but we still want to allow introducing free software
> on nonfree platforms[2]
My point was that documentation (and packaging as you point it) can
steer users towards free software.
The goal of the software may even be altered this way, if it cannot
be used fully free with its regular uses cases.
The former case might be faster to do, but getting it right would be
difficult since the user would have to be aware of that documentation.
Which one to do would then depend on the context.
For instance with qemu and libvirt, the software was modified not to
steer users towards running non-free GNU/Linux distributions.
While unrelated, the case of debootstrap is also interesting, since, on
parabola, it by default debootstraps free software distributions.
References and configuration related to non-100%-free distributions
were removed.
> i think packaging is better than documenting, shouldn't be much more
> effort
Right, I assumed documenting was way faster. I was probably wrong.
> but this doesn't address the problem of discernment
> example: i can go to [3] and see there are four games, i know they are
> free because they are inside a free distro frontier
> if users need to exit the free distro frontier, they probably will
> find nonfree and free games and don't see much difference
> the ideal would be to have a comprehensive set of games packaged
> inside the free distro frontier
The documentation would have had to take that into account.
I was thinking of something along the lines of HOWTO that you find in
the documentation of the distributions. Such as list of commands that
would explain how to do it, while making sure that freedom is preserved.
But as you pointed out, packaging might be faster and easier.
> hiding the emulator executable/package
I don't understand what it means.
> would warn when they are exiting the free distro frontier and poke
> them to add free games to the distro (suggesting to developers or
> sending patches)
That is very similar to documentation for me.
We might also want to do that on the parabola wiki, trying to implicate
people who might want to use such emulators.
Example: Why is <foo emulator> not in Parabola
|-> <Explanation suggesting to send patches>
> alternatively, forking all emulators and creating a
> free community around them would also provide a freedom frontier
That is nice too. Uzebox seem in the right direction with that.
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-05 15:59 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 16:31 MAME emulator is giving incentive to use non-free software alírio eyng
2016-03-30 22:30 ` Isaac David
2016-04-02 3:17 ` Denis 'GNUtoo' Carikli
2016-03-31 22:50 ` alírio eyng
2016-04-01 6:23 ` Ricardo Wurmus
2016-04-01 12:15 ` alírio eyng
2016-04-01 20:03 ` alírio eyng
2016-04-02 2:19 ` Denis 'GNUtoo' Carikli
2016-04-02 8:48 ` [GNU-linux-libre] " alírio eyng
2016-04-03 14:20 ` alírio eyng
2016-04-03 18:36 ` alírio eyng
2016-04-03 19:39 ` Felipe Sanches
2016-04-03 21:02 ` alírio eyng
2016-04-03 21:22 ` Felipe Sanches
2016-04-04 3:26 ` alírio eyng
2016-04-04 11:19 ` Felipe Sanches
2016-04-04 22:23 ` alírio eyng
2016-04-04 22:47 ` [GNU-linux-libre] " Felipe Sanches
2016-04-04 22:58 ` Felipe Sanches
2016-04-04 22:59 ` Felipe Sanches
2016-04-05 2:29 ` alírio eyng
2016-04-09 9:00 ` Denis 'GNUtoo' Carikli
2016-04-09 19:43 ` alírio eyng
2016-04-27 0:31 ` [GNU-linux-libre] " alírio eyng
2016-04-05 15:59 ` Denis 'GNUtoo' Carikli [this message]
2016-04-06 11:02 ` alírio eyng
-- strict thread matches above, loose matches on Subject: below --
2016-03-30 4:10 IngeGNUe
2016-03-30 16:11 ` Mark H Weaver
2016-03-30 21:26 ` IngeGNUe
2016-03-29 14:01 Jean Louis
2016-03-29 14:46 ` Nils Gillmann
2016-03-28 21:55 Jean Louis
2016-03-29 0:26 ` Jookia
2016-03-29 4:42 ` Jean Louis
2016-03-29 6:27 ` Jookia
2016-03-29 7:30 ` Jean Louis
2016-03-29 8:25 ` Jookia
2016-03-29 11:35 ` rain1
2016-03-29 12:00 ` Jean Louis
2016-03-29 12:48 ` Nils Gillmann
2016-03-29 14:23 ` Mathieu Lirzin
2016-03-29 14:52 ` Jean Louis
2016-03-29 16:15 ` Ludovic Courtès
2016-03-29 17:29 ` Jean Louis
2016-03-29 17:47 ` Jean Louis
2016-03-29 12:41 ` Nils Gillmann
2016-03-29 1:44 ` Mark H Weaver
2016-03-29 13:03 ` Ludovic Courtès
2016-03-29 17:30 ` Christopher Allan Webber
2016-03-29 17:32 ` Thompson, David
2016-03-29 17:37 ` Eric Bavier
2016-03-30 20:25 ` Ludovic Courtès
2016-03-29 8:58 ` Taylan Ulrich Bayırlı/Kammer
2016-03-29 10:12 ` Jean Louis
2016-03-29 13:14 ` Ludovic Courtès
2016-03-29 13:51 ` Jean Louis
2016-03-29 16:09 ` 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=20160405175911.0307cc6d@top-laptop \
--to=gnutoo@no-log.org \
--cc=alirioeyng@gmail.com \
--cc=gnu-linux-libre@nongnu.org \
--cc=guix-devel@gnu.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).