3 ms·
> possibly not complying with the MIT license. I think this author is trying to make the MIT license do something it was not designed to do and is not generall
by jrochkind1 6y ago
> possibly not complying with the MIT license.
I think this author is trying to make the MIT license do something it was not designed to do and is not generally understood to do. I think he chose the wrong license if he wanted his work to legally require his permission to be copied.
I'm not even sure what parts of the license he thinks have been broken. (The idea that it's even possible to violate terms of the MIT license is I admit somewhat new to me).
Elsewhere in the thread, commenters suggest the violated clause is: "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."
But I have never before seen it suggested that the MIT License is in fact "viral" like the GPL, that it requires derivative works to also be licensed MIT. The license is usually understood as quite the opposite, and often used intentionally because of that. If that's what you wanted, you chose wrong with MIT license.
Generally when I personally see code with an MIT License, I understand that I am able to copy whatever I want from that project to my own projects, I thought that was the point of it. Do y'all not do the same?
Copying ideas or a name does not seem to me to be "a copy or substantial portion of the Software"; but even aside from the particular license terms, the worse part for this argument is they are generally not protected by copyright at all.
> has reimplemented the app with almost the same features and configuration syntax using GitHub actions
Reimplementation? So nobody is alleging actual code got copied? "Features" are not generally even copyrightable at all, it doesn't matter what license you use.
Whether "configuration syntax" is copyrightable or not... I guess the author is taking the Oracle side in Google v. Oracle, on copyright protection of APIs. But if you believed your "configuration syntax" was copyrightable and you wanted to require people to ask your permission before copying it -- you really ought not to release it under an MIT License.
Even apart from licensing, in general I don't think "features" or "configuration syntax" are or ought to be protected by copyright at all. I'm sorry, yes, people can copy them from you.
If the David and Goliath roles were reversed, I have a hard time believing a large corporation alleging someone had violated copyright for cloning "features and configuration syntax" -- for something released under the MIT license in the first place -- would get any sympathy at all. We (software devs) have generally supported the right to clone software, for good reason.
Re-using the name is certainly rude. I am not sure if it is actionable. The rest of it... it's not even about open source, its about that cloning software has always been allowed (although Oracle v. Google may be about to change that, which will be a disaster).
- Xylakant 6y ago> Generally when I personally see code with an MIT License, I understand that I am able to copy whatever I want from that project to my own projects, I thought that was the point of it. Do y'all not do the same? You are allowed to take and copy it to your project. You just need to retain the notice along with it - IANAL but I usually just copy the licence in a code comment along with the copied section (or file). I usually include a pointer to the original source for audit purposes. That doesn't make my project MIT licensed, but that part of the code that I lifted without substantial modification remains MIT licensed, even if I make my project closed source commercial. There's no way around that - I cannot claim it as my own since I have not written it. Same for public domain code.