2 ms·
That's covered by their terms of service, quoted in the OP: "Your Content belongs to you. You decide whether and how to license it. But at a minimum, you licen
by kibwen 11y ago
That's covered by their terms of service, quoted in the OP:
"Your Content belongs to you. You decide whether and how to license it. But at a minimum, you license npm to provide Your Content to users of npm Services when you share Your Content. That special license allows npm to copy, publish, and analyze Your Content, and to share its analyses with others."
Services like this have to account for such rights in their terms of service, because distribution is a minefield even for properly-licensed packages. For example, the MIT license covers only "this software and associated documentation files", which AFAICT means that if you have e.g. a screenshot in your repo then conceivably you could request a DMCA takedown on anyone distributing your repo. Likewise GPL doesn't cover anything but code, not even documentation (you're expected to remember to explicitly use the GNU Free Documentation License to cover that).
IANAL, so I'd be happy if someone who was would chime in with any corrections.
- ajdlinux 11y agoSince when did the GPL not cover non-code artifacts? The FSF's view at http://www.gnu.org/licenses/gpl-faq.en.html#GPLOtherThanSoftware http://www.gnu.org/licenses/gpl-faq.en.html#GPLOtherThanSoft...: "You can apply the GPL to any kind of work, as long as it is clear what constitutes the “source code” for the work. The GPL defines this as the preferred form of the work for making changes in it. However, for manuals and textbooks, or more generally any sort of work that is meant to teach a subject, we recommend using the GFDL rather than the GPL."