With VMware finally announcing its plans to remove the non-complying #GPL code, Hellwig decides not to appeal. The VMware case wraps up:
Android community control is just an illusion and all developers knows this (even when they don’t like to say it): https://gbl08ma.com/developing-for-android-is-like-being-a-demonetized-youtuber/
@aral TIL that if a #Google engineer remove your name from a #GPL codebase you contributed to for 6 months and when called to account coordinates the `git rebase` to remove you from the #history of the project (a @conservancy member) but accidentally squash some of your patches in anyway, drawing obvious conclusions about the people involved and their motivations is... #PARANOIA ! ! !
Don't forget this.
Don't be #paranoic!
They shall do no #Evil! :-D
Thinking about changing my little todo list project to #GPL instead of #MIT , but it's hard to jump. The GPL is long, hard to understand, and using a TL;DR explanation is kind of like trusting that they created an accurate summary of the GPL without actually analyzing it yourself.
I like the MIT license because it's brief, I'm not liable for damage, and I don't have a lot of time to go into deep analysis of a long license like GPL, but I'm eager to move to GPL.
licenses Show more
Close. I think you mean "release some parts under GPL and thus force everyone else _releasing the same parts with changes_ to publish the source".
GPL only applies for releasing software. If you never release the software, you don't need to release the sources along it. A modified GPL web server doesn't need to have its source released if you put said server on your domain.
AGPL exists due this.
licenses Show more
@tfb But if the company is the copyright holder, it may dual-license their software: make some parts published under GPL, and thus force everyone else publish the sources, but keep the exclusive right to include it into their own proprietary s/w.
Or am I not understanding the terms of #GPL correctly?
And the second part basically means that "open-source" is simply a catch to get free labor?
Then that's yet another reason why the developers should not contribute to such a software.
Oh, I did not know an EUPL existed. Interesting: https://en.wikipedia.org/wiki/European_Union_Public_Licence
> EUPL is the first open source licence to be released by an international governing body.
Uhm... I think you are a bit confused (if you are not trying to troll me 🤣).
Permissive licenses set the whole work they "protect" under the threat of being taken and closed by evil companies.
It's not donating software to the commons, it's throwing it at the world like if it was #garbage.
Who even goes to the Epic Store?
GOG has a differentiator at least, DRM-free. What does Epic have?
"We're Epic and we can do this because we have billions in cash at hand. what u gonna do about it"?
It's funny how cancerous corporations infecting everything are, but some of them then have the balls to call the #GPL cancer. 😞
i think my computer has a fever.... it's all bloated and tired... oh wait that's just windows bloatware!!!!!! #FOSS #FLOSS #LibreSoftware #FourEssentialFreedoms #RMS #Windows #Microsoft #Zune #FreeBSD #NetBSD #OpenBSD #Linux #HURD #OS2Warp #Haiku #TempleOS #FuckGoogle #Google #SurveillanceCapitalism #women #MastoAdmins #GPL #AGPL #LGPL #BSD2Clause #BSD3Clause #OpenSource #CathedralAndTheBazaar #DunkingOnWindows #EFF #GNU #Privacy #RightToRepair #WhenYouPayForADeviceRunningWindows10HomeYouArePayingMicrosoftToGiveYouAnIntentionallyRestrictedProduct #Hashtags #WindowsTen #GNUSlashLinux #FamilyGuyFunnyMoments #LegalMonopoly #FuckCapitalism #ButItsWhatIveAlwaysUsed #ButINeedToPlayBethesdaGames #ButIDontWantToTypeCommands #MoreLikeShitdows #LynneTeachesTech
The situation in NZGOAL Software Edition is somewhat better. Public service agencies are advised to license any modifications to an existing codebase under the license the upstream codebase uses, even when they're not legally obliged to (ie a non-copyleft license). When licensing new software, they're advised to use either #GPL (v3+) or "#MIT", and to consider #LGPL or #AGPL where appropriate.
That's why I wrote the #HackingLicense license but I'm considering some changes so read it carefully, I'm not a lawyer, not your lawyer: you really need to use your own brain and take full responsibility for it (as with every other license, but people often overlook this).
This is a good question.
Several lawyers all over the world have read the #HackingLicense and provided useful feedbacks that I incorporated in it.
However none of them was MY lawyer: they were either friends or collaborators that gave it a read for free.
According to most, it's as viable as any other license, but it's incompatible with #GPL and in some jurisdiction it might be equivalent to a NC despite it doesn't forbids commercial usage.