Comment by jrowen
19 days ago
The author links to another article of theirs called "Open Source is Bigger Than You Can Imagine," which hinges on the size of the npm registry. npm says "open source" on their landing page, and has an "npm Open Source" section of their policies, which places no restrictions on how you license your npm package (save for a special license to them).
This does seem very bazaar to me, but this would all be deemed Not Open Source by the [cathedral/megachurch?] community, correct? Do people take issue with npm using the term open source?
Why would that all be deemed “Not Open Source”?
My understanding is that something can only be called Open Source (vs. Source Available) if it uses one of the approved licenses that uphold the GNU Four Freedoms of Software. Which isn't a requirement of npm.
Now I'm curious how many NPM packages use non-OSI/FSF-approved licenses.