4 ms·
> it would be wise to get those in writing. I agree with that, projects should clearly state their goals and priorities upfront. But relying on legalese from M
by type0 6y ago
> it would be wise to get those in writing.
I agree with that, projects should clearly state their goals and priorities upfront. But relying on legalese from MIT license is not the solution.
- cycloptic 6y agoIt's not clear what else it is that you'd want. The MIT license seems to get used because it's short and to the point in stating priorities: Here's the software, do what you want with it, but don't take credit and don't come after us if it doesn't work for your use case or if it causes your CPU to explode. If your issue is with the "legalese," it wouldn't be any less meaningful if you stated it differently.