unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>, "Ricardo Wurmus" <rekado@elephly.net>
Cc: 35234@debbugs.gnu.org
Subject: [bug#35234] [PATCH] gnu: Add the-dark-mod.
Date: Mon, 22 Apr 2019 11:02:02 +0200	[thread overview]
Message-ID: <87k1fm9zw5.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87pnpf72ns.fsf@gnu.org>

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

Ludovic Courtès <ludo@gnu.org> writes:

> Thoughts?
>
> Now, I would hope that the free game engine could serve as the basis for
> a free game, with free game data as well.

Absolutely.  Technically all those engines can be re-used for
fully-free game development.

There is a blurred line however between the means and the ends here.
For instance, lots of packages we have in Guix can be used to deal with
some proprietary data, from web browsers to video players, you name it.

My take at this issue is that free game engines are a first step towards
liberating the video game industry further.  If we don't allow the
opportunity for free game engines in the first place, free game data
will never be worked on.

Guix stands mostly (but not only) for free software.  Game data is a
whole different battle though, and I'm not sure it's the role of Guix to
fight this one.  If we can encourage freedom, however, by supporting the
first step towards "free game data," then it's a win for freedom in my
opinion.  The reverse could be more damaging to the users' freedom in
the long run than protecting it.

The Dark Mod is fully free, the game data is under some CC, so I'll
commit the package if there is no objection.

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2019-04-22  9:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 18:16 [bug#35234] [PATCH] gnu: Add the-dark-mod Pierre Neidhardt
2019-04-11 19:40 ` Ricardo Wurmus
2019-04-12  9:39   ` Pierre Neidhardt
2019-04-12 11:22     ` Ricardo Wurmus
2019-04-12 12:02       ` Pierre Neidhardt
2019-04-21 14:13         ` Ricardo Wurmus
2019-04-21 16:18           ` Ludovic Courtès
2019-04-22  9:02             ` Pierre Neidhardt [this message]
2019-04-22  9:19               ` Ricardo Wurmus
2019-04-22  9:42                 ` Pierre Neidhardt
2019-04-22 16:50                 ` Ludovic Courtès
2019-04-22 17:42                   ` Pierre Neidhardt
2019-04-22 10:01             ` Adonay Felipe Nogueira
2019-04-22  9:40           ` Adonay Felipe Nogueira
2019-04-22 11:56             ` Ricardo Wurmus

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=87k1fm9zw5.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=35234@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.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).