From: Paul Sutton via libreplanet-discuss <libreplanet-discuss@libreplanet.org>
To: libreplanet-discuss@libreplanet.org
Subject: Re: LibreJam - FSF* should host a Libre Game development tournament!
Date: Fri, 7 Jan 2022 10:32:09 +0000 [thread overview]
Message-ID: <aa0afba9-a55c-0ee5-d196-990608dce5bc@disroot.org> (raw)
In-Reply-To: <E1n5gkY-0003P4-J5@fencepost.gnu.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 2911 bytes --]
On 07/01/2022 04:21, Richard Stallman wrote:
> [[[ 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. ]]]
>
> It sounds like game jams have value for education in programming, but
> do they have value for the free software movement, enough for free
> software activists to dedicate time to them for the sake of that?
>
> Can the people who want to do a game jam for free software think up a way
> to make it educate about free software as well as about programming?
>
> I don't have answers for those questions, but I think they are the
> crucial questions to pose.
>
I would guess just using free software to make the games is a start,
we can then have discussions about software licensing generally but
include the four freedoms within that discussion.
Also have discussions as to what happens if we need a component that is
non free, how doing that ends up tying us in to a situation where if
that component changes, our game may no longer compile or work
properly. So this gives a practical example of the problems people
face. How do we work round that, make games that interact with say the
free software drivers/firmware, so we may sacrifice some game features
but we can enhance other features.
How can we write games to make money if they are written under a free
software license could be a question we get.?
Another example could be that software is available on wider hardware
due to the source code being available, and the fact we have the freedom
to port (which probably requires modification before recompiling)
Raspberry Pi is available to lots of people, so while some parts may be
non free, lets get people in that way too, work around the issues and
campaign - support truly free hardware - which brings me on to:-
Also with the rise of RiscV and other open processors ( I am not very
good with the vocabulary here, sorry) isn't there a chance we may
actually get some truly RYF hardware? We are going to need developers
for that at some point, Core/Libreboot will probably form oart of any
systems using those CPUs so again those projects need developers.
What about games for pinephones, pine tablets and the pinebooks, it
seems there are several operating systems and programs are not ported to
all of them, example the Mastodon apps.
If we want to build a game for free software systems, how can we target
as many systems as possible easily?
So writing games, will teach people skills they can use elsewhere too.
Lets do more brainstorming on this.
Paul
--
--
Paul Sutton, Cert Cont Sci (Open)
https://personaljournal.ca/paulsutton/
Pronoun : him/his/he
OpenPGP : 4350 91C4 C8FB 681B 23A6 7944 8EA9 1B51 E27E 3D99
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]
[-- Attachment #2: Type: text/plain, Size: 184 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2022-01-07 10:36 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
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 [this message]
2022-01-05 10:38 ` 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=aa0afba9-a55c-0ee5-d196-990608dce5bc@disroot.org \
--to=libreplanet-discuss@libreplanet.org \
--cc=paulsutton@disroot.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).