4 ms·
I'm kinda iffy on this. I mean, I get the idea behind it and I appreciate the spirit of it. But now we have yet one more home-grown license that probably hasn
by mindcrime 10y ago
I'm kinda iffy on this. I mean, I get the idea behind it and I appreciate the spirit of it. But now we have yet one more home-grown license that probably hasn't been vetted by anybody, has unknown legal ramifications, and basically just adds to the noise and confusion around OSS licensing.
Sure, as a layman, I can read this and assume that it probably means what I think it means. But if I wanted to incorporate this code into another project, would I really be willing to be the farm on that?
License proliferation[1] is a real issue and I think we should all take it into consideration. Anyway, I hope the author at least submits this to OSI[2] and - hopefully - gets it certified as an OSI approved OSS license.
[1]: https://opensource.org/proliferation-report https://opensource.org/proliferation-report
[2]: https://opensource.org/approval https://opensource.org/approval
- em3rgent0rdr 10y agogood idea about having the author submit this to OSI...I guess I'll make an issue report on that github page. But this license shouldn't have any concerns about legal ramifications since it explicitly states that the request is non-binding. So as far as the law is concern, this is MIT license.
- em3rgent0rdr 10y agoOk, I submitted: https://github.com/thestk/rtmidi/issues/110 https://github.com/thestk/rtmidi/issues/110