@frumble @thomholwerda ja, #GPLv3 hat auch wieder Probleme.

• Ideal wäre #BSD (wenn nicht sogar #0BSD) weil GPLv3 ist mit #CCSS inkompatibel und daher für alles was nicht ebenfalls #GPLv3 oder #AGPLv3 ist inkompatibel!

@obfusk @SocketSecurity well, that's why @landley created #0BSD, which merely has the 'offered as-is with no warranties whatsoever' disclaimer in it.

• I'd still attribute said code anyway because I think it's fair to at least do proper #attribution...

Also it's the closest to a #PublicDomain license (besindes #CC0) for juristictions that don't allow people to disavor #authorship but only acknowledges #LapsedCopyright|s and #License terms (i.e. #Germany)...

@gondolyr personally, I also loke #permissive licenses like #0BSD.

@libreleah thanks.

Personally, I think maintainers should choose their license wisely beforehand:

• There are reasons why I chose to put some projects under #CCBYNCSA, some #GPLv3 and some #0BSD.

• In some cases I did fork stuff under #MIT which I'd not change the license of - even if it would be compatible - because I literally changed nothing in terms of code and also didn't see any advantage in doing so to begin with.

Espechally in the case of #DuckStation this is bad because we ain't talking about the whole #GPLv2-only vs. GPLv3+ drama or #grsecurity #paywalling (which is an asshole move but legal )...

• Maybe the dev(s) - unlike #Capcom - weren't fully aware of this issue, but even big Companies (i.e. #AVM) got forced into compliance...

Lets just hope a friendly (!!!) reminder makes them realize, apologize and undo the change...

@anthropy I think that should be covered by #CodeOfConduct...

• Personally, I am a fan of #0BSD because #Germany doesn't recognize #PublicDomain (only lapsed copyrights!) and being permissively licensed goes both ways...

@marcan @fuchsiii Either way, like @landley I did the #copyleft experiment and those projects didn't see even remotely as much resonance or contribution as when I embraced #0BSD as a #PermissiveLicense (cuz #PublicDomain legally doesn't exist in #Germany: One cannot renounce #Authorship for legal reasons, otherwise #HateSpeech would be unprosecute-able, so only #Copyright lapses 70 years post-mortem of the Authors)...

• I think "#AssholeLicensing" like #SSPL is inherently unfree and #AGPLv3 is just an act of committing #AssetDenial which doesn't work.

TBH, the only way to preven #GAFAMs like Amazon from leeching #FLOSS is to either make #CCSS or offer the superior [#SaaS] solution by ticking boxes #aws can't ( i.e. due to #CloudAct, like #GDPR compliance) or inherently won't hecause it's antithetical to their business ( i.e. [airgapped] #SelfHosting & Support/Management Options for self-hosted systems)...

• #healthcare-IT based startups in the #EU pay Companies like #Telekom to host their medical data because unlike #Amazon they can and will evidently enshure their U.S. division can't leak that data to U.S. govt. agencies and if one butters them with enough money, they'll likely sign the hardest NDAs one can throw at them...

@standingpad personally, I feel similar:

#GPLv3 is great when you want to commit #AssetDenial and enshure your project can't be "tivolized".

• If you want to be real "anti-capitalist" go with #AGPLv3 so noone will use it in any commercial setting!

Tho I do think that #PermissiveLicensing like #0BSD works better long-term because #enforcement of the #GPL only backfires harder...

• But don't take my word for it, when @landley has publicly admitted that this had harmed #BusyBox to the point of trashing the projects reputation.

I chose 0BSD for #OS1337 because I want to make a #GNU-free, minimalist #Linux.

• OFC that only applies to the project and it's code: Linux is still #GPLv2-only and that's because GPLv3 is incompatible with how #licensing and #patents work and manufacturers of hardware can't bend reality to fit RMS's wishful thinking.

@Yuki 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, @landley 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

@Edent You could make a #Minus1BSD license by copying #0BSD and just adding the single provision: "You are not allowed to use this in production or anything critical and only in controlled testing envoirements"...

https://en.wikipedia.org/wiki/BSD_licenses#0-clause_license_(%22BSD_Zero_Clause_License%22)

@hexaheximal case in point:
#Copyleft doesn't work in terms of getting #contributions or actual improvements.

One can not really force people to do intellectual labour nor get them to share it!

But don't take my word for it, because @landley has been there and done that as the fmr. maintainer of #BusyBox and nowadays maintains a competing project (#toybox) licensed under #0BSD...

---

TBH I'm not against the #GPL, not even #GPLv3 because when you want to commit #AssetDenial it does that fine and I use it for that...

But sadly #FLOSS doesn't exist in a vacuum and as much as I wished #CCSS to never have existed in the first place, it sadly does and worse people often depend on that shite...

---

So I do aim to #DoBetter instead...

Another reason why "#PublicDomain" is a problem but #0BSD isn't is because not every juristiction acknowledges or accepts Public Domain.

For example in #Germany, where the head maintainer resides. there is no such thing as "Public Domain" but only "Lapsed Copyrights*".

Otherwise it would be impossible to prosecute authors of obvious #hatespeech, cuz not every place agrees with the U.S. principle of what is essentially "#ConsequenceFreeSpeech", not "#FreeSpeech"...


Again:
We don't make the rules, we've to follow them whether we like them or not!

https://www.youtube.com/watch?v=MkJkyMuBm3g&t=2107s video via @linuxfoundation feat. @landley

* which hasn't lapsed yet for #SteamboatWillie there because as per bilateral agreements, Copyrights don't lapse till 70 years past the death of the authors and that applies for U.S. works to - in return German Residents don't need to file for Copyright because that's inherently granted at creation and thus also applies in the USA!