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"?
Response to Nodejitsu NPM Trademark
11–20 of 22 posts
Re: Response to Nodejitsu NPM Trademark
#12It'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"?
There is no node foundation, "Node.js" is a Joyent's trademark. We had discussed this particular bikeshed in the mailing list last year. :)
Re: Response to Nodejitsu NPM Trademark
#13Issacs wrote the initial npm and was by far the largest contributor. https://github.com/npm/npm/graphs/contributors
According to Mikeal he "wrote the original version of the npm registry". More of his thoughts on the history of NPM here: https://gist.github.com/mikeal/8947417
the registry, yes, not npm itself. isaacs also has committed more to the actual registry code than I have as well.
Re: Response to Nodejitsu NPM Trademark
#14It'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"?
no,there is basically nodejitsu,strongloop and joyent but no Foundation. NodeJs is managed by private businesses which purpose are only to care about the interest of their shareholders, not nodejs or opensource on the node community. I guess NodeJS will be more like Nginx than Python in the way it will be managed. IE a free version + some premium services/packages... I would not rely too much on npm in the future though.
Re: Response to Nodejitsu NPM Trademark
#15It'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"?
Unfortunately, I think this is the one big issue barring Node from wide adoption. I love Node.js and the surrounding ecosystem, but all these companies fighting one another can't possibly be good for the community.
Re: Response to Nodejitsu NPM Trademark
#16Well. 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.
I hope the npm replacement word is going to be as easy and short, or even more so. nnn? "nnn is not npm"?
Re: Response to Nodejitsu NPM Trademark
#17Had to go 4 pages back in HN to find this. Guess this story is getting flagged by someone.
Re: Response to Nodejitsu NPM Trademark
#18I 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.
I pledge not to use nodejitsu or have any dealings with nodejitsu employees.
There's nothing to stop them from saying "sorry", and equally nothing to stop them from doing it again. It should not have happened in the first place.
Re: Response to Nodejitsu NPM Trademark
#19Had to go 4 pages back in HN to find this. Guess this story is getting flagged by someone.
I saw it via Node Weekly. Wondered why I didn't see it on HN. Go to post the links, already posted. Strange!
Re: Response to Nodejitsu NPM Trademark
#20Well. 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. I hope the npm replacement word is going to be as easy and short, or even more so. nnn? "nnn is not npm"?
Maybe just n3?
PS: It is weird that node.js community well known for internal battles. Everybody throw shit at each other and nobody win from this.