The great license-washing has begun
Uncategorized
1
Posts
1
Posters
0
Views
-
The great license-washing has begun
In the world of open source, relicensing is notoriously difficult. It usually requires the unanimous consent of every person who has ever contributed a line of code, a feat nearly impossible for legacy projects. chardet, a Python character encoding detector used by requests and many others, has sat in that tension for years: as a port of Mozilla’s C++ code it was bou
https://www.osnews.com/story/144547/the-great-license-washing-has-begun/
-
undefined riffraff@mastodon.social shared this topic on
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@thatgiga bellissimo!
mi ricordo i manuali dell'ingegnere
-
@Smithsonianmag @smartnews-Smithsonianmag this is cool.
-
@bouletcorp2 Susan ! <333
-
oh god that's quite the jump up https://dustycloud.org/tmp/org_diet_results.html
I haven't been eating as well the last few days due to stress
gotta stick with it tho
-
GNU Terry Pratchett
-
This would mean I'm the only person allowed to sell a work based on my own GPL code on Steam. And also that if I merge any pull-request from someone else I'd loose that right, unless I get permission from each contributor.
But they also say "The author [can] decide that what the Steamworks SDK does is just a communication with a service that does not invoke the copyleft requirement of the GPL".
And then I'm wondering if this really only applies to "the author" or to anyone?
-
About the Steam case in particular:
"Generally, any license that has a so-called “copyleft” element will be problematic when combining code with the Steamworks SDK. The best-known example is GPL."
https://partner.steamgames.com/doc/sdk/uploading/distributing_opensourceHowever, the copyright holder of the code does not have to respect the license, and they also say it:
"This can happen if the author of the code that is GPL-licensed has given the permission to do so."
-
@stefano ok, first things first, how someone became "expert" in vibe coding?
