this post was submitted on 30 Jul 2025
105 points (97.3% liked)
Emulation
4260 readers
1 users here now
Community to talk about emulation & roms.
RULES:
1.) No bigotry
LINKS:
-
Emulation Wiki - Your source for everything emulation :)
-
[WIP] Emulation Links Wiki - My personal wiki for emulation links, please help contribute!
-
r/Roms Megathread - Megathread of Roms
-
RetroArch - RetroArch is the popular front-end to libretro which is a simple API that allows for the creation of games and emulators.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This comment by woelkchen on the original thread adds some context worth reading imo.
This developer appears to have accepted contributions from over 100 other people prior to having a change of heart about the GPL and ~~unilaterally~~ switching the project to a non-free license (CC Attribution-NonCommercial-NoDerivatives).
~~Somehow I doubt that all of the other contributors actually agreed to that license change ๐ค~~
Bonus ๐คก-points for making a bunch of unrelated changes to source code in the "Misc: Update copyright headers" commit.
edit: i stand corrected, thanks to @LiveLM@lemmy.zip i see the developer wrote:
It's odd they didn't mention that in the commit where they changed the license.
๐ฅ to whoever carries on development of the last GPL version, and/or develops other free software emulators. and ๐ค to people continuing to contribute to this one after it became non-free.
It seems he did in fact get their permission, and rewrote code he couldn't relicense
heh, i've seen almost exactly this break a dev before. it was the ion3 dev, tuomo valkonnen. he was probably never entirely OK, but eventually he ragequit opensource, installed windows, deleted all his opensource projects and went incommunicado.
what pushed him over the edge was distros shipping packages of somewhat older versions of his windowmanager (so, not updating their packages as soon as he released a new stable version) and then users filing bugreports for bugs he'd already fixed.
I totally get the frustration of getting pointless bug reports.
I've seen many repos with a "you must reproduce your issue on the version we release here to report" policy, I wonder if that could be a solution.
Maybe together with a GitHub bot to scan logs posted on the issues and inform the reporter about that...
he had the policy, he just couldnt deal with the idiots who refused to read it
Much appreciated. The author's comment for that commit does not paint the full picture.
The comment about analogies is so good.