231–240 of 1001 posts
Earlier quoted context omitted.
> (A)GPLv3 does not prevent their projects from being used. In practice, it does in many cases. Many companies have a blanket policy of avoiding these licences. But I agree that they make more sense for apps than libraries.
So they don't use Linux, bash, or GCC?
Earlier quoted context omitted.
There should not be any difference between small or large entitise in how you deal with them as an opensource maintainer. Just because someone has more money (or less), should not automatically mean you treat them with more leniency or ethics. You set up your standard, and stick to it whomever comes.
> You set up your standard, and stick to it whomever comes. Why? Most businesses don't entertain standard rates, either. It's case-by-case negotiations ("call us", "request quote"). Why should I, as a private person putting stuff out there for free, set up "my standard" and stick to it?
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.
It's also very possible they had been working on it already and wanted to compare notes, I certainly would if I were working on something internal and found a similar project, but I agree, ask them for a consultation fee. I don't see why they wouldn't pay it. Both projects also share in license, so I have less of an issue with it personally. They're both MIT licensed.
> 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…
It's as if we've learned nothing about exploitative corporation behavior for the last 20-30 years even though it's in the news EVERY other day.
> 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 released a fun personal project under GPLv3 and the first filed issue was someone saying I should change the license to something friendlier to business interests. Hell no. If they want to profit off my work, pay me. This is something I'm doing for fun, on my own terms. It’s Free for anyone to use as they want, so long as they keep it Free, too.
Give downstream how much they are willing to give upstream.
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…
> 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…
> 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…
By far the biggest risk for most projects is "nobody notices it and nobody uses it".
And if someone "takes" your project and uses it - you've usually still got it. Software is funny like that.
Earlier quoted context omitted.
Do you think this stops the fork? It’s not like they can’t read the code.
Well your license is only as good as you are able to enforce it. Even with the law there is no guarantees. I grew up thinking that people would follow the spirit of open source rather than the specific letter of the law. This is obviously not true, and probably never has been.