@Yuki @novenary @norm The big takeaway is to NEVER EVER sign a "#ContributionAgreement" that allows the maintainers to turn #FLOSS into #UnfreeSoftware!

I'd certainly never would out of principle...

https://infosec.space/@kkarhan/112134853241787929

Kevin Karhan :verified: (@[email protected])

@[email protected] I sincerely hope everyone's gonna fork #Redis before they changed to #AssholeLicensing with the #SSPL which is a #NonFree #AssholeLicense. This is worse than #Copyleft but just blatant *Asset Denial* because *"We WaNt AmAzOn To PaY uS!" kinda bs... If you want to make money with #FLOSS, provide some good product and make it attractive to #donate and/or #buy some support. As a matter of fact, @[email protected] did try to *crowbar* #GPLv2 [or rather started it]¹ with #BusyBox and that failed miserably, because now everyone knows BusyBox as the litigatious² folks that one should just not use code from. There's a reason I chose #0BSD ³ for @OS1337 and it's because I most of the work I do is build and repackage #toybox + #musl / #Linux and I want people to use it as a *friendly licensed* foundation for their *#IoT* and *#embedded* projects down the line. And that means that I'll also accept contributions on the same license and not expect devs to sign away code under worse terms so I can turn it into #UnfreeSoftware the way Redis and others did... ¹ https://www.youtube.com/watch?v=MkJkyMuBm3g&t=1607s ² https://www.busybox.net/license.html ³ https://en.wikipedia.org/wiki/BSD_licenses#0-clause_license_(%22BSD_Zero_Clause_License%22) ⁴ https://github.com/OS-1337/OS1337/blob/main/LICENSE.md

Infosec.Space