License not terribly clear
Baughn opened this issue ยท 11 comments
Context: I'm attempting to package Mekanism for TPPI3C.
Your README claims it's MIT-licensed, which is great. My question is... precisely which MIT license?
They'd all work. But if you could add a LICENSE file to the repository, we'd have a bit more clarity.
That's one of them. The problem would be that there are at least half a dozen "MIT Licenses", and they have subtle differences.
I'm pretty sure they all the same at
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.`
only difference could be
Except as contained in this notice, the name(s) of the above copyright holders shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization.
or part or mentioning the trademark (im pretty sure Mekanism is aready a trademark and its not this Mekanism), but how it affects you as a modpack creator?
I am assuming here but most likely looking for clarification on redistributing the mod files.
License part of the readme.md says
As such, I have decided to license Mekanism under the MIT license, allowing for anyone with an interest in the project to fork/pull/distribute.
allowing for anyone with an interest in the project to distribute
Let me be clear, then: I'm fairly sure the license allows me to do what I'm doing. I don't think I've got any problems with it.
But it took me about half an hour to do the research so I'd be reasonably sure of that. It'd save the next guy that half-hour if there was a LICENSE file in the repo.
@Baughn What exactly are you doing then?
Compiling my own version to distribute with TPPI3C, since the build server doesn't seem to provide HTTPS.
ISP has a tendency to inject javascript in downloads that aren't secured, occasionally corrupting the download in the process. I don't want to know what they might do to a .jar.
And really, it's basic common sense. You don't download executables over insecure channels.