3 ms·

I wonder how it relates to a few npm forks (https://github.com/rlidwka/yapm https://github.com/rlidwka/yapm, https://github.com/visionmedia/npm https://github.c

by rlidwka 13y ago

I wonder how it relates to a few npm forks (https://github.com/rlidwka/yapm https://github.com/rlidwka/yapm, https://github.com/visionmedia/npm https://github.com/visionmedia/npm) created earlier this year, especially to second one since @visionmedia didn't change its name... And what about alternate npm-compatible registries (https://github.com/mbrevoort/node-reggie https://github.com/mbrevoort/node-reggie, https://github.com/rlidwka/sinopia https://github.com/rlidwka/sinopia, https://github.com/cnpm/cnpmjs.org https://github.com/cnpm/cnpmjs.org), not based on CouchDB? "npm" isn't only a product name anymore since it's used extremely widely, so this doesn't seem like a good thing to do.

ender7 13y ago
In the trademark world you are arguing that "npm" has become "genericized" [1]. That certainly can happen, but that would be a very hard argument to make given npm's relative youth and the lack of true use as a generic. The people you link are either forking the actual npm client (in which case they are referring to it as a proper noun), or are building their own repo architecture, in which case they refer to it as an "npm registry" or "npm repository", not just "an npm". [1] http://en.wikipedia.org/wiki/Generic_trademark http://en.wikipedia.org/wiki/Generic_trademark
- rlidwka 13y ago
  As far as I remember, "npm registry" is a trademark as well. Isn't it? At least, that's what is written here: https://github.com/npm/npm#legal-stuff https://github.com/npm/npm#legal-stuff . My point is: any single package README contains a phrase "install me using `npm install whatever`". It feels like it is generalized already...
malandrew 13y ago
Even without a trademark, the npm source has been Artistic License v2 for as long as I can remember, so any forks are obligated to change their name to have the right to forking the source code.

by rlidwka 13y ago

ender7 13y ago

In the trademark world you are arguing that "npm" has become "genericized" [1]. That certainly can happen, but that would be a very hard argument to make given npm's relative youth and the lack of true use as a generic. The people you link are either forking the actual npm client (in which case they are referring to it as a proper noun), or are building their own repo architecture, in which case they refer to it as an "npm registry" or "npm repository", not just "an npm". [1] http://en.wikipedia.org/wiki/Generic_trademark http://en.wikipedia.org/wiki/Generic_trademark

rlidwka 13y ago
As far as I remember, "npm registry" is a trademark as well. Isn't it? At least, that's what is written here: https://github.com/npm/npm#legal-stuff https://github.com/npm/npm#legal-stuff . My point is: any single package README contains a phrase "install me using `npm install whatever`". It feels like it is generalized already...

malandrew 13y ago

Even without a trademark, the npm source has been Artistic License v2 for as long as I can remember, so any forks are obligated to change their name to have the right to forking the source code.