> The MIT License (MIT)
> Copyright (c) Microsoft Corporation
Incredible!
https://github.com/Microsoft/ChakraCore/blob/master/LICENSE....
> The MIT License (MIT)
> Copyright (c) Microsoft Corporation
Incredible!
https://github.com/Microsoft/ChakraCore/blob/master/LICENSE....
This announcement is probably timed to coincide with NDC. There were lots of similar open source announcements at a previous MS conference I was at. Although it was a bit weird due to the time difference on the embargo.
MS is being open because it makes sense to, and it's the only way to maintain mindshare in the near future. Azure's a decent enough offering, but AWS and GCE are right there as well, each with advantages over the others. I actually like windows (mostly), but need it far less, as I can do what I like with OSX and Linux and do daily.
As a developer/user it's nice to see the changes.
I'm not going to pretend that MS "got it" at the time. "Share Source" was an insult to everyone. However, internally you could see light bulbs going off in people's heads. People who worked on the shared source version were proud of what they were doing and were really eager to have people look at it. The fact that "shared source" essentially crippled it to the point that it would be useless to everyone was surely a thorn in those people's sides. It (and every other shared source project) died in obscurity (thankfully).
I often wonder if this was one of the seeds that eventually sprouted inside MS to make them start to take open source seriously. I even wonder if one day we will see them embrace software freedom. Well... I can dream can't I ;-)
Gone from being vehemently anti-Microsoft most of my career to going "Hmmmm, I should look at that."
Now to carve out time to do anything with any of it. :\
Both Apache and GPL grant patent use to everyone. I'd paste the relevant bit, but it's stupid-law-level-long. Point 3 in https://www.apache.org/licenses/LICENSE-2.0.txt - also see the exploding trap at the end of that point. You cannot sue the author for patent reasons.
It isn't that the MIT License is known to provide no protection; rather, it's unknown whether the MIT License provides protection. The MIT License contains strong wording to suggest it may very well provide protection against patents, but it's untested and not quite as strong as the patent grant in, say, Apache 2.0. It's a matter of knowns and unknowns.
Consequently, this is why the MIT License and the BSD License should not be lumped together.
It doesn't.. It's what MS essentially had prior to opensourcing .net proper.
They had some parts of it the library that were free, and some parts that were hands-off or we'll sue you.
It makes sense to try and lure people in at first with "free" and then scare them into buying licences if they ever manage to get big.
Apache version 2.0, on the other hand, has an express patent license. There are very good reasons to prefer an express patent license.
I have not heard such arguments before. Can you provide a link to someplace where these legal arguments are explained?
1. The permission language "deal in the Software without restriction" is very broad.
2. Of the more specific, enumerated permissions "use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of" the terms "copy", "modify", "publish", "distribute", and "copies" speak to the exclusive rights of copyright owners per United States Code title 17, section 106. The terms "use" and "sell" speak to things you can sue for under a patent per United States Code title 35, section 271. The term "sublicense" is generic to licenses of all kinds, including copyright licenses and patent licenses.
3. There is also a legal idea called "estoppel" that prevents, broadly speaking, leading people to believe they can violate your rights freely and then suing them, or taking back or shrinking permission that you've already granted. State Contracting and Engineering Corporation v. Florida, decided by the United States Court of Appeals for the Federal Circuit, is an interesting case in the patent context. You might find a summary online, if you haven't time to trawl through the court's written opinion.
To quote Larry Rosen, from his book Open Source Licensing:
> Be careful about implied licenses. An implied license is necessarily vague and incomplete. The terms and conditions of an implied license may not be clear to either the licensor or the licensee. Reliance on an implied license is particularly risk when important property interests are at stake.
If you're worried about an implied license for a specific reason, please talk to your company's legal or engage an attorney. It's going to require a judgment call, and you want someone on your side who will consider a lot more than what I've mentioned here in coming up with good advice.