From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 35234@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: [bug#35234] [PATCH] gnu: Add the-dark-mod.
Date: Sun, 21 Apr 2019 18:18:15 +0200 [thread overview]
Message-ID: <87pnpf72ns.fsf@gnu.org> (raw)
In-Reply-To: <87ef5v78f8.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 21 Apr 2019 16:13:47 +0200")
Hi Ricardo,
Ricardo Wurmus <rekado@elephly.net> skribis:
> Pierre Neidhardt <mail@ambrevar.xyz> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
> […]
>>> First: what game engines do we provide that can only be used with
>>> proprietary game data?
>>
>> OpenMW, Arx Libertatis, OpenRCT2, off the top of my head.
>
> Hmm, that’s not good then. I think we should take a closer look at them
> to decide whether they should be removed.
>
> The description of Arx Libertatis says this:
>
> Arx Libertatis is a cross-platform, open source port of Arx Fatalis,
> a 2002 first-person role-playing game / dungeon crawler developed by
> Arkane Studios. This port however does not include the game data, so
> you need to obtain a copy of the original Arx Fatalis or its demo to
> play Arx Libertatis.[…]
>
> Aside from the “open source” mention I don’t think it’s right for us to
> recommend that users obtain a copy of a proprietary game.
The “you need to obtain a copy…” bit is problematic because it refers to
non-free software.
However, I believe it’s really talking about “non-functional data” in
FSDG terms:
https://gnu.org/distros/free-system-distribution-guidelines.html#non-functional-data
So, rephrased to suggest obtaining the non-free _data_, the sentence may
be OK per the FSDG. The problem is that it’s maybe not that simple to
obtain the data without the non-free game…
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.
Ludo’.
next prev parent reply other threads:[~2019-04-21 16:19 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 [this message]
2019-04-22 9:02 ` Pierre Neidhardt
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=87pnpf72ns.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35234@debbugs.gnu.org \
--cc=mail@ambrevar.xyz \
--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).