by tkhattra on 2/3/23, 1:45 AM with 19 comments
by dctoedt on 2/3/23, 2:41 PM
"Furthermore, the good will that was gained from free distribution of these software packages led to the flow back of both funding and software applications that support research and education at MIT. The cash flow has dwarfed the forgone revenue stream that likely would have come from licensing for a fee, and even that sum has been dwarfed by the value of the applications that became available.
"A lesson is that it can be important to look past the prospect of licensing for a fee, which may bring in a few dollars, and instead see the opportunity that opens if you give the software away. The potential reward can be orders of magnitude larger."
(Extra paragraphing added.)
by bhickey on 2/3/23, 2:59 PM
Stallman said:
> The term "MIT license" is a confusion. It is used to describe two different licenses; see https://gnu.org/licenses/license-list.html. We call them the X11 license and the Expat license. To distinguish them, we do not use the term "MIT license". The X11 license was, as far as I know, first used by X11. I don't know how it was written -- the question is not interesting to me.
Thanks Richard.
Hal recalled that it was drafted by Karen Hershey at the request of the Technology Transfer Office. Regretfully I don't have a copy of his original response.
by ghaff on 2/3/23, 2:35 PM
The current license actually matches a related but different license than the X11 license and at least one open source IP lawyer I know suspects there may have been a minor mixup when the "MIT license" was approved by OSI.
by icambron on 2/3/23, 2:52 PM
by thelastbender12 on 2/3/23, 2:41 PM
When I first got access to the internet, MIT seemed awfully productive in producing code. Before I found out that MIT License doesn't imply the work was done by a person at MIT!
by jmclnx on 2/3/23, 1:57 PM
by lukeh on 2/3/23, 6:29 AM
by froh on 2/3/23, 2:05 PM