3 ms·
Yeah, kinda scary right? I'll keep digging, I'm surprised that a change in the wording of the license can't solve the problem. I'm assuming that if that's all
by wyldfire 11y ago
Yeah, kinda scary right? I'll keep digging, I'm surprised that a change in the wording of the license can't solve the problem. I'm assuming that if that's all it took, the author of that paper wouldn't have called for legislation changes.
- steveklabnik 11y agoIt is also interesting because this is talking about the license of the code, but in this particular situation, we have two licenses: the one the author gives for the code, but also npm's TOS. I wonder if this applies to the TOS as well, or if this is a feature of copyright law specifically. I would assume the latter, but I am not a laywer.
- wyldfire 11y agonpm's TOS is not quite the same because it's not a license. Therefore it's not governed by 17 USC (Copyrights). But if it were a contract, changing the terms of the contract probably is bound by some laws somewhere. I doubt that the TOS constitutes a contract but it seems like an analogous problem to whether the acceptance of the open source license constitutes a contract.
- steveklabnik 11y agoRight, that's what I was trying to say, but got a bit sloppy. :)