From: Dennis Payne <dulsi@identicalsoftware.com>
To: Jacob Hrbek <kreyren@rixotstudio.cz>,
discussion@lists.fsfe.org, rms@gnu.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 12:30:24 -0500 [thread overview]
Message-ID: <3e87540d4c1abdffe5bf838a80e5ca81faa3cc32.camel@identicalsoftware.com> (raw)
In-Reply-To: <c37c9b47-12ff-bd2c-3c71-02cbf8015246@rixotstudio.cz>
I don't think a game jam will cause a sudden influx of quality free
software games. I don't think it is a bad idea to have one but I doubt
it will be a great source of quality free software games. Jam games are
not typically developed further beyond the jam.
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?
> 3. Ban any non-free game engines and any non-free tools e.g. to
require using GNU GIMP instead of AS Photoshop.
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 using itch.io for the jam would be easiest but I don't
think the site is free software. Many of the tools they create are such
as the itch.io app and butler.
--
Dennis Payne
dulsi@identicalsoftware.com
https://mastodon.gamedev.place/@dulsi
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2021-12-29 19:29 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 [this message]
2021-12-29 18:07 ` Jacob Hrbek
2021-12-30 4:28 ` Richard Stallman
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=3e87540d4c1abdffe5bf838a80e5ca81faa3cc32.camel@identicalsoftware.com \
--to=dulsi@identicalsoftware.com \
--cc=committee@freesoftware.org.au \
--cc=discusion@fsfla.org \
--cc=discussion@lists.fsfe.org \
--cc=kreyren@rixotstudio.cz \
--cc=libreplanet-discuss@libreplanet.org \
--cc=rms@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.
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).