You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect it's just to prevent people from creating lots of issues and pull
requests before build infrastructure is in place. It'd probably be best for
contributions to continue to target joyent/node for now.
It's been taken private for now pending resolution of a trademark issue with Joyent. I missed the call where the decision was made but I believe it was done as a goodwill gesture towards Joyent; apparently, they were genuinely baffled by the fork. Discussions are ongoing, please watch this space.
Does that mean they are "baffled" by the other 7,243 forks? The word "node" is not the trademark they own. The license states exactly what they can actually enforce.
@hij1nx not espousing an opinion either way, but since 2012 Joyent has asserted in the LICENSE for joyent/node, that "node" is a trademark of Joyent. They have not, however, ever filed for this trademark with the USPTO office, but they have filed (and received) a mark for "node.js".
It is also interesting that the trademark policy you linked to does not explicitly talk about "node", but makes sense given they never filed for the mark.
Not sure if this is the best place to post this, but count me in if you need help moving forwards. I have a pretty good grasp on Node and love what this project is trying to accomplish.
@mikeal Note, the USPTO's actual website search is terrible, and links are session-based. Please use http://trademarks.justia.com which is in every way superior and has the same information.
Node advisory board was just formed. I think it includes some active node-forward people. Probably we still need to wait some time to hear how things progress.
Activity
Fishrock123 commentedon Oct 13, 2014
It's currently private, we are probably waiting for things to get going a bit more and an actual announcement, I'd assume.
cc @mikeal
Qard commentedon Oct 13, 2014
I suspect it's just to prevent people from creating lots of issues and pull
requests before build infrastructure is in place. It'd probably be best for
contributions to continue to target joyent/node for now.
bnoordhuis commentedon Oct 13, 2014
It's been taken private for now pending resolution of a trademark issue with Joyent. I missed the call where the decision was made but I believe it was done as a goodwill gesture towards Joyent; apparently, they were genuinely baffled by the fork. Discussions are ongoing, please watch this space.
heapwolf commentedon Oct 13, 2014
Does that mean they are "baffled" by the other
7,243forks? The word "node" is not thetrademarkthey own. Thelicensestates exactly what they can actually enforce.Fishrock123 commentedon Oct 13, 2014
.. they would be
indexzero commentedon Oct 14, 2014
@hij1nx not espousing an opinion either way, but since 2012 Joyent has asserted in the LICENSE for joyent/node, that "node" is a trademark of Joyent. They have not, however, ever filed for this trademark with the USPTO office, but they have filed (and received) a mark for "node.js".
It is also interesting that the trademark policy you linked to does not explicitly talk about "node", but makes sense given they never filed for the mark.
mikeal commentedon Oct 14, 2014
Actually, they did file it but abandoned it http://trademarks.justia.com/852/62/node-85262599.html. "node" is a pre-existing general programming term so it's very doubtful it ever would have been approved.
JulianGindi commentedon Oct 16, 2014
Not sure if this is the best place to post this, but count me in if you need help moving forwards. I have a pretty good grasp on Node and love what this project is trying to accomplish.
isaacs commentedon Oct 16, 2014
@mikeal Note, the USPTO's actual website search is terrible, and links are session-based. Please use http://trademarks.justia.com which is in every way superior and has the same information.
vkurchatkin commentedon Nov 11, 2014
So, what is going on? How can one see what is going on in node-forward/node?
ilkkao commentedon Nov 11, 2014
Node advisory board was just formed. I think it includes some active node-forward people. Probably we still need to wait some time to hear how things progress.
bnoordhuis commentedon Nov 12, 2014
It's taking some more time. If you want access to the repo, ping me.
vkurchatkin commentedon Nov 12, 2014
@bnoordhuis thank you, I would really love that
bnoordhuis commentedon Nov 12, 2014
@vkurchatkin Invitation sent.
zladuric commentedon Nov 12, 2014
From what i understood, this is still limited access? No entry fOr us
lurkers?
Am 12.11.2014 15:11 schrieb "Ben Noordhuis" notifications@github.com:
107 remaining items
victormx commentedon Nov 28, 2014
I hope i can get a invite too,thank's.
bnoordhuis commentedon Nov 28, 2014
@emkay @clarle @egeozcan @jodytate @jacogr @victormx Invites sent, welcome.
ruimarinho commentedon Nov 30, 2014
@bnoordhuis could you please send me an invite too? Thanks!
lynchpin4 commentedon Nov 30, 2014
if y'all are gonna be using this over on the @atom shell send me an invite too - thanks
bnoordhuis commentedon Nov 30, 2014
@ruimarinho @gstack Invites sent.
greelgorke commentedon Dec 1, 2014
please, send me an invite too
ruiquelhas commentedon Dec 1, 2014
Would love an invite also. Thanks.
bnoordhuis commentedon Dec 1, 2014
@greelgorke @ruiquelhas Invites sent.
greelgorke commentedon Dec 1, 2014
thanks!
timaschew commentedon Dec 1, 2014
May I get an invite? Thanks.
19h commentedon Dec 1, 2014
And me. I'd like to help and join the development, thanks!
bnoordhuis commentedon Dec 1, 2014
@timaschew @KenanSulayman Certainly. Invites sent.
rhbecker commentedon Dec 1, 2014
requesting a read access invitation ... thanks
bnoordhuis commentedon Dec 1, 2014
@rhbecker No problem, invite sent.
cjihrig commentedon Dec 3, 2014
For anyone else requesting access, it appears that development of node-forward/node is going to move to the already public iojs/io.js repo.