Explore >> Select a destination
|
You are here 
|
fossa.com | ||
| | | | |
gavinhoward.com
|
|
| | | | | GitHub has made me angry again. This time, it's because they are laundering code with machine learning. To fight that, I have developed new FOSS licenses to poison their well. | |
| | | | |
blog.tidelift.com
|
|
| | | | | Learn about the importance of open source software compliance, how to navigate licensing complexities, and the unique challenges posed by AI integration. | |
| | | | |
luten.dev
|
|
| | | | | I've been putting my work online in various formats for almost 20 years now. For most of that time, I've used extremely permissive licenses such as the MIT License to distribute my work in an attempt to promote usage and adoption. Now that I'm quite a bit older and experienced (you may say curmudgeony), let me tell you why I'm changing my tune and am adopting a Copyleft approach. In the past decade or so, I've noticed a widespread adoption of the MIT license, even by those who in the past opposed Open Source Software as a concept. Why the swing and why so extreme? You'd think that those companies would slowly adopt Open Source rather than going all-in all at once. What's going on? | |
| | | | |
www.makeworld.space
|
|
| | | TL;DR: Use the Mozilla Public License (MPL 2.0). It's like the LGPL, but allows static linking. | ||
