201–210 of 1001 posts
It's not a new practice, and it's not exclusive to Microsoft either, it's something every developer should be acutely aware of, in case they're interested in avoiding it.
> As a sole maintainer of an open source project, I was enthused when Microsoft reached out to set up a meeting to talk about Spegel. The meeting went well, and I felt there was going to be a path forward ripe with cooperation and hopefully a place where I could onboard new maintainers. Seems it isn't the first time Microsoft leads open source maintainers on, trying to extract information about their projects so they…
Edit: apparently Google did not use the author's codebase, instead using an Apache 2.0 licensed codebase [1] explained here [2].
[1]: https://github.com/kubernetes-sigs/gcp-filestore-csi-driver
Earlier quoted context omitted.
If a megacorp wants your help to explain ANYTHING to them, you better be paid handsomely per hour. Wtf are people doing charity for trillion dollar empires.
I think that worldview leads to a much poorer world. Normal people aren't constantly engaging in a fight for survival in every aspect of their lives, and I don't think it's a good thing to ask them to. We should expect the people we deal with to be acting in good faith. I think it would be bad actually if I had to consider if you're going to make money off of my idea when talking to you. Asking everybody to be consta…
like what? continue to use (pay) for their products and wait for regulations coming from lobbyist countries? /s
> I default to using the MIT license as it is simple and permissive What's good about being "permissive"? I keep hearing this argument, but I still don't understand, what's the incentive for authors of one-man projects to choose anything "permissive". Do you enjoy your project getting forked, walled off and exploited for profit by someone who has never done you any good? AGPLv3 still allows forking, still allows maki…
My personal thought is that we need a new kind of license: community open source. No corporations, just community. The problem this addresses is not that Microsoft forked this project. The problem is that when a corporation like Microsoft does this, they harm our community[0]. Open source thrives because a bunch of individuals and groups collaborate. Microsoft, is built around the concept of profit for stock owners a…
> My personal thought is that we need a new kind of license: community open source. No corporations, just community. It exists: https://creativecommons.org/licenses/by-nc-sa/4.0/
I am unclear of where the boundaries could and should be, but in essence we want money to flow into community source projects. Corporations and commercial entities can and should pay a fair amount. If they don't want to pay, they should not be able to profit from the work of the community.
> I default to using the MIT license as it is simple and permissive What's good about being "permissive"? I keep hearing this argument, but I still don't understand, what's the incentive for authors of one-man projects to choose anything "permissive". Do you enjoy your project getting forked, walled off and exploited for profit by someone who has never done you any good? AGPLv3 still allows forking, still allows maki…
I always choose permissive licenses for personal project, and I often avoid depending on other projects that aren't permissive. If I want to know that, if I need to, I can grab the code and change something. And I want others to be able to remix what I make as needed. The more limitations added on a license, the less open it is.
It's unintuitive, but permissive licenses are not the best way to acheive this. GPL's "limitations" are designed to maintain the right and abilty to remix code for the end user. So if say Microsoft forks your library and its fork becomes more popular, they can't make it proprietary after capturing the market and effectively stop people from remixing what you made.
Earlier quoted context omitted.
The commit histories for the LICENSE files in the two repositories are rather interesting. The original author placed a single copyright notice in that file. Microsoft on the other hand published it with their copyright notice and a Apache 2.0 license in place of the original copyright notice and MIT license. They also put copyright Microsoft and license apache 2.0 headers on all files. They then changed the Apache 2…
> chore: change to MIT license What does "chore" mean in this context? Is the license just leftover from some MS open source template? If so there is perhaps some leeway, and the author maybe just didn't realize he needed to use the original MIT license file including the notices and not just a template one grabbed from the internet. Any other explanation for such a "relicensing" would be extremely worrisome.
> I default to using the MIT license as it is simple and permissive What's good about being "permissive"? I keep hearing this argument, but I still don't understand, what's the incentive for authors of one-man projects to choose anything "permissive". Do you enjoy your project getting forked, walled off and exploited for profit by someone who has never done you any good? AGPLv3 still allows forking, still allows maki…
> I default to using the MIT license as it is simple and permissive What's good about being "permissive"? I keep hearing this argument, but I still don't understand, what's the incentive for authors of one-man projects to choose anything "permissive". Do you enjoy your project getting forked, walled off and exploited for profit by someone who has never done you any good? AGPLv3 still allows forking, still allows maki…
I’ve released some utility libraries under permissive libraries. I like it when they get used. Even when it’s part of a large company’s closed-source app. Many people don’t like that, and that’s perfectly fine, that’s why there are different choices available. What I’ll never understand is people who release their project with a permissive license and then get upset when a big company distributes their own version of…
> I default to using the MIT license as it is simple and permissive What's good about being "permissive"? I keep hearing this argument, but I still don't understand, what's the incentive for authors of one-man projects to choose anything "permissive". Do you enjoy your project getting forked, walled off and exploited for profit by someone who has never done you any good? AGPLv3 still allows forking, still allows maki…
I’ve released some utility libraries under permissive libraries. I like it when they get used. Even when it’s part of a large company’s closed-source app. Many people don’t like that, and that’s perfectly fine, that’s why there are different choices available. What I’ll never understand is people who release their project with a permissive license and then get upset when a big company distributes their own version of…