LibrePlanet discussion list archive (unofficial mirror)
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Dennis Payne <dulsi@identicalsoftware.com>
Cc: kreyren@rixotstudio.cz, discussion@lists.fsfe.org,
	discusion@fsfla.org, committee@freesoftware.org.au,
	libreplanet-discuss@libreplanet.org
Subject: Re: LibreJam - FSF* should host a Libre Game development tournament!
Date: Wed, 29 Dec 2021 23:28:36 -0500	[thread overview]
Message-ID: <E1n2n3M-0004qF-QS@fencepost.gnu.org> (raw)
In-Reply-To: <3e87540d4c1abdffe5bf838a80e5ca81faa3cc32.camel@identicalsoftware.com> (message from Dennis Payne on Wed, 29 Dec 2021 12:30:24 -0500)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > In a lot of ways I think the bigger problem for free software games is
  > discoverability. Have you played Smalltrek? How about Witch's Blast?
  > OpenAlchemist? Diver Down? Mindcrosser? Hijinx: A Christmas Capper?
  > Seahorse Adventures? Shattered Pixel Dungeon? Anagramarama? Ardentryst?

We can do something to help with that.  The first step is to add entries
in directory.fsf.org for them.

Then we could make another page with a list of these free games
and put it on gnu.org/software.  It could have 5-10 lines of description
of each game.

WDYT?

  > Non-free game engines I agree with. I think non-free tools is not
  > enforceable. If the developer uses free content from opengameart.org or
  > other sites, they may have no idea how the content was created. It
  > makes sense to not allow non-free tools to build the game.

I agree that there is nothing to be gained by making rules about how
the files _were_ written or tested.  Or about what tools a participant
privately uses.  If you prefer to use a non-free text editor, that has
no effect on anyone else, so we have no reason to bother you about
that.  We don't even need to ask what you actually use.

The rules that make sense are about what the release program allows
developers to do to develop it further.  So every file should be suitable
for editing with a free editor, and compiling with a free compiler, etc.


Side issue.  May I suggest not using the word "content" to describe
works of authorship or art?  That term subtly denigrates _all_ of them.

See https://gnu.org/philosophy/words-to-avoid.html.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)



_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss

  parent reply	other threads:[~2021-12-30  4:30 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  6:07 LibreJam - FSF* should host a Libre Game development tournament! Jacob Hrbek
2021-12-29 17:30 ` Dennis Payne
2021-12-29 18:07   ` Jacob Hrbek
2021-12-30  4:28   ` Richard Stallman [this message]
2021-12-30  7:13     ` Jacob Hrbek
2021-12-30 16:53       ` Dennis Payne
2021-12-31  4:26         ` Richard Stallman
2021-12-31  5:32           ` Jacob Hrbek
2022-01-02  6:59             ` Richard Stallman
2022-01-02  7:32               ` Jacob Hrbek
2022-01-03 16:39                 ` Michael McMahon
2022-01-04  8:43                   ` Jacob Hrbek
2022-01-05  3:54                     ` Richard Stallman
2022-01-05  5:06                       ` Michael McMahon
2022-01-05  5:56                         ` Jean Louis
2022-01-05  9:21                         ` Paul Sutton via libreplanet-discuss
2022-01-07  4:21                         ` Richard Stallman
2022-01-07  9:49                           ` Florian Snow
2022-01-07  9:53                           ` [FSFLA] " Ismael Luceno
2022-01-07 23:23                             ` Dennis Payne
2022-01-09 19:11                               ` Jean Louis
2022-01-14 15:26                               ` Ismael Luceno
2022-01-18 23:03                                 ` Dennis Payne
2022-01-19 13:27                                   ` Ismael Luceno
2022-01-20  3:12                                     ` Sebastian Silva
2022-02-14 16:11                                       ` Michael McMahon
2022-01-07 10:32                           ` Paul Sutton via libreplanet-discuss
2022-01-05 10:38                       ` [FSFLA] " Ismael Luceno
2022-01-05 14:37                         ` Jacob Hrbek
2022-01-05 15:10                           ` Ismael Luceno
2022-01-05 19:48                             ` Dennis Payne
2022-01-06 15:11                               ` Paul Sutton via libreplanet-discuss
2022-01-06 17:22                               ` Ismael Luceno
2022-01-04  3:01                 ` Dennis Payne
2022-01-04  8:45                   ` Jacob Hrbek
2021-12-31  5:33           ` Theodore Somers
2022-01-01  4:47             ` Richard Stallman
2022-01-01  9:07               ` Paul Sutton via libreplanet-discuss
2022-01-01 16:14                 ` Jacob Hrbek
2022-01-01 16:18             ` Jacob Hrbek
2021-12-30  8:34     ` Yasuaki Kudo
2021-12-30  9:33       ` Paul Sutton via libreplanet-discuss
2021-12-30 23:35         ` John Sullivan
2021-12-31  1:14           ` Dennis Payne
2021-12-30  9:00     ` Félicien Pillot
2021-12-31  4:26       ` Richard Stallman

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://lists.gnu.org/mailman/listinfo/libreplanet-discuss

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

  git send-email \
    --in-reply-to=E1n2n3M-0004qF-QS@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=committee@freesoftware.org.au \
    --cc=discusion@fsfla.org \
    --cc=discussion@lists.fsfe.org \
    --cc=dulsi@identicalsoftware.com \
    --cc=kreyren@rixotstudio.cz \
    --cc=libreplanet-discuss@libreplanet.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.
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).