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/
Getting forked by Microsoft
831–840 of 1001 posts
Re: Getting forked by Microsoft
#832Earlier quoted context omitted.
> 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/
As someone commented above, commercial use is an issue. Creative commons is good, but the non-commercial clause prevents it being useful in this case. It seems to be that the crucial issue here is the duplication of the project by forking. 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 p…
Re: Getting forked by Microsoft
#833Earlier quoted context omitted.
> I think community source should be accessible and usable outside the community. A community license should have a provision for paid use by corporations. If Microsoft wants to use it that is fine - if they pay. That violates the first clause of the open source definition: https://opensource.org/osd It probably violates 5 and 6 too. > But if Microsoft wants to fork things, to me that is predatory. If I can't fork wi…
the OSCL turned 18 years old a month ago. maybe things have changed enough since then to validate revisiting it. OSI is too busy trying to come up with an equally mid (at best) OSAID for another thing thing that corporations already don't and won't care about following, so I don't expect them to prioritize it even if it got raised
Re: Getting forked by Microsoft
#834Earlier quoted context omitted.
> Don't use one of the most permissive licenses in existence Does it matter what license you use if they actively ignore the terms in the license you did chose? MIT requires attribution, but they didn't. Why would any other terms be different? You surely could have put "You must license your project the same as the one you forked from" and they still would have ignored it, not sure what the difference would have been…
> Does it matter what license you use if they actively ignore the terms in the license you did chose? If they're breaking the license, go talk to a lawyer. You might start by approaching the SFLC [1] (although I haven't heard much from them recently). [1] https://softwarefreedom.org/
Re: Getting forked by Microsoft
#835Don't use one of the most permissive licenses in existence and certainly not one that doesn't provide copyleft. This is all very well established at this point and yet somehow the GPL seems to have gone out of vogue.
> Don't use one of the most permissive licenses in existence Does it matter what license you use if they actively ignore the terms in the license you did chose? MIT requires attribution, but they didn't. Why would any other terms be different? You surely could have put "You must license your project the same as the one you forked from" and they still would have ignored it, not sure what the difference would have been…
Re: Getting forked by Microsoft
#836Earlier quoted context omitted.
Everywhere I've worked for the past 10+ years treats open source like a candy store to benefit from and wouldn't allow contributing code back
https://web.archive.org/web/20120620103603/http://zedshaw.co... > Why I (A/L)GPL > I want people to appreciate the work I’ve done and the value of what I’ve made. > Not pass on by waving “sucker” as they drive their fancy cars. Always choose AGPLv3 no matter what it is you're doing. If they want it, AGPLv3 gives you the leverage to negotiate a licensing deal. You sell them permission to violate it. I even emailed Sta…
Re: Getting forked by Microsoft
#837Earlier quoted context omitted.
Maybe as a show of good faith you could send the original creator 10 or 20k usd as a thank you. Talk is cheap
This sounds like a good idea but getting the checkbook out at a company like Microsoft probably takes 3-5 meetings, and saying you want to donate because you accidentally stole their code and put the company at (theoretical) risk of a lawsuit seems like a bad conversation starter with management. I like the thought though
Re: Getting forked by Microsoft
#838Earlier quoted context omitted.
Whenever I see AGPL project, I close the page, and I believe many others would do the same.
Why?
There’s no reason to worry about the AGPL unless you plan to conceal code from its users. Most software businesses take this approach because it’s hard to sell information that is publicly available, and code is just information. Some businesses make money operating software for others. AWS pays on-call engineers to keep RabbitMQ highly available.
Free Software protects the user from the developer. Permissive licenses protect the developer from the author.
A lot of professional software engineers get confused and think of themselves as the “user” when they’re actually more of a middle man.
Re: Getting forked by Microsoft
#839My 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…
Re: Getting forked by Microsoft
#840Earlier quoted context omitted.
https://web.archive.org/web/20120620103603/http://zedshaw.co... > Why I (A/L)GPL > I want people to appreciate the work I’ve done and the value of what I’ve made. > Not pass on by waving “sucker” as they drive their fancy cars. Always choose AGPLv3 no matter what it is you're doing. If they want it, AGPLv3 gives you the leverage to negotiate a licensing deal. You sell them permission to violate it. I even emailed Sta…
Depends on the terms of the deal, I would want to at minimum get back any modifications they are making.