I pledge not to use nodejitsu or have any dealings with nodejitsu employees until I see a blog post stating that they have changed their minds and are not going to hijack npm trademark.
Issacs wrote the initial npm and was by far the largest contributor.<p><a href="https://github.com/npm/npm/graphs/contributors" rel="nofollow">https://github.com/npm/npm/graphs/contributors</a>
I wonder how it relates to a few npm forks (<a href="https://github.com/rlidwka/yapm" rel="nofollow">https://github.com/rlidwka/yapm</a>, <a href="https://github.com/visionmedia/npm" rel="nofollow">https://github.com/visionmedia/npm</a>) created earlier this year, especially to second one since @visionmedia didn't change its name...<p>And what about alternate npm-compatible registries (<a href="https://github.com/mbrevoort/node-reggie" rel="nofollow">https://github.com/mbrevoort/node-reggie</a>, <a href="https://github.com/rlidwka/sinopia" rel="nofollow">https://github.com/rlidwka/sinopia</a>, <a href="https://github.com/cnpm/cnpmjs.org" rel="nofollow">https://github.com/cnpm/cnpmjs.org</a>), not based on CouchDB?<p>"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.
It's my understanding that in open source communities, the relevant trademarks are usually held by a community-led foundation (e.g. the Apache Software Foundation, the Python Software Foundation). Is there no "Node Foundation"?
Well. This is the week I started really getting into node. It's also the week I found about this. It's all disheartening. It's probably a necessary awakening step for developers in regards to truly considering the ownership of their tools.<p>I hope the npm replacement word is going to be as easy and short, or even more so. nnn? "nnn is not npm"?