DuckStation recently changed to a source-available license that prohibits distributing modified versions of the software and prohibits commercial use. Before, it was GPLv3.
Also OpenOffice, Emby, Audacity, Android (AOSP) (soft forked to LineageOS and GrapheneOS, but no hard fork)
Soft forks try to maintain code compatible so changes can apply to both code bases. Normally done when there’s hope of a future merging of the code lines. They rarely work, as eventually thing get hard.
DuckStation recently changed to a source-available license that prohibits distributing modified versions of the software and prohibits commercial use. Before, it was GPLv3.
DuckStation is an emulator for some Sony PlayStation console. PS2, I thinkThanks to FangedWeyvern42@lemmy.world I know that it was a PS1 emulator. This software used to be given to users under the GPLv3 license, which grants freedoms such as distribution of the source code of the software (DuckStation) for no extra cost (well, DuckStation also costs no money! …so, you get to eat the cake and learn its recipe too, for free!).
…Now they’ve switched to a license which allows you to see the source code, but does not grant you rights over the source code that GPLv3 did (which is essentially ANYTHING as long as you publicize everything you make with the source code, under the GPLv3 license also - changes to the code, new software that uses any portion of the code, anything you make with it).
OpenOffice, Emby, Audacity, and Android (the “Android Open-Source Project”) have also done this in the past.
Knowing this stuff on Free, Libre, and Open-Source (“FLOSS”) platforms like Lemmy is almost necessary given that they’re built on these principles. Please get acquainted with them.
DuckStation recently changed to a source-available license that prohibits distributing modified versions of the software and prohibits commercial use. Before, it was GPLv3.
Also OpenOffice, Emby, Audacity, Android (AOSP) (soft forked to LineageOS and GrapheneOS, but no hard fork)
What’s the difference between a soft fork and a hard fork, besides being careful with your teeth?
Soft forks try to maintain code compatible so changes can apply to both code bases. Normally done when there’s hope of a future merging of the code lines. They rarely work, as eventually thing get hard.
Sorry, I couldn’t understand your comment. Could you please explain it better?
DuckStation is an emulator for some Sony PlayStation console.
PS2, I thinkThanks to FangedWeyvern42@lemmy.world I know that it was a PS1 emulator. This software used to be given to users under the GPLv3 license, which grants freedoms such as distribution of the source code of the software (DuckStation) for no extra cost (well, DuckStation also costs no money! …so, you get to eat the cake and learn its recipe too, for free!).…Now they’ve switched to a license which allows you to see the source code, but does not grant you rights over the source code that GPLv3 did (which is essentially ANYTHING as long as you publicize everything you make with the source code, under the GPLv3 license also - changes to the code, new software that uses any portion of the code, anything you make with it).
OpenOffice, Emby, Audacity, and Android (the “Android Open-Source Project”) have also done this in the past.
Knowing this stuff on Free, Libre, and Open-Source (“FLOSS”) platforms like Lemmy is almost necessary given that they’re built on these principles. Please get acquainted with them.
Thank you very much, this helps me.
Funnily enough, Libre Office is another great example of this, being forked from Open Office (and also way better).
It was a PS1 emulator and one of the best ones. Shame about the developer.
rip audacity
fuck muse group