agg1401 {l Wrote}:How do we do the licensing business?
The easiest (and imho best) solution is to create a "CREDITS.txt" in your repo, which lists blocks of (used asset) (author) (licensing terms) and maybe an (url). For example, this is how I did it in my
CREDITS.txt (this is the bare minimum, and I haven't listed the license for each asset, because I've only used assets under CC-BY-SA). Another sample with examplary tidy info blocks
CREDITS.txt. For the records, this is exactly how STK does it too, see
CREDITS (however its file is less records like, and more like simple free-text, but all the info is there).
Some license (the GPL most notably) requires you to provide a notice in run-time too. If you're not using any GPL parts, you can skip this. But if you do,
here's how they recommend to do it.
The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different;
for a GUI interface, you would use an “about box”.
Also note that GPL is very strictly copyleft license, if any part of your game is GPL licensed, then your entire game
must be GPL licensed, meaning you can only use assets under licenses which are compatible and allow re-licensing under GPL. Despite its quirks (or perhaps because of those), GPL is still the best license to enforce FOSS.
Hope this helps,
bzt