Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request access to node-forward/node here #7

Open
chetandhembre opened this issue Oct 12, 2014 · 137 comments
Open

Request access to node-forward/node here #7

chetandhembre opened this issue Oct 12, 2014 · 137 comments

Comments

@chetandhembre
Copy link

Last time I checked this organization has joyent/node forked repo. But now I can not see it. Am I missing something here ? :)

@Fishrock123
Copy link
Member

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
Copy link
Member

Qard commented 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
Copy link
Member

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
Copy link
Member

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.

@Fishrock123
Copy link
Member

apparently, they were genuinely baffled by the fork.

.. they would be

@indexzero
Copy link

@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
Copy link
Member

mikeal commented Oct 14, 2014

that "node" is a trademark of Joyent. They have not, however, ever filed for this trademark with the USPTO office

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
Copy link

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
Copy link

isaacs commented 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
Copy link

So, what is going on? How can one see what is going on in node-forward/node?

@ilkkao
Copy link

ilkkao commented 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
Copy link
Member

It's taking some more time. If you want access to the repo, ping me.

@vkurchatkin
Copy link

@bnoordhuis thank you, I would really love that

@bnoordhuis
Copy link
Member

@vkurchatkin Invitation sent.

@zladuric
Copy link

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:

@vkurchatkin https://github.com/vkurchatkin Invitation sent.

Reply to this email directly or view it on GitHub
#7 (comment)
.

@bnoordhuis
Copy link
Member

That's correct, it's still private. I'll give read access to anyone who asks, though.

@zladuric
Copy link

Well then: can I please have read access?

:-)

Thanks,

Zlatko
Am 12.11.2014 16:36 schrieb "Ben Noordhuis" notifications@github.com:

That's correct, it's still private. I'll give read access to anyone who
asks, though.

Reply to this email directly or view it on GitHub
#7 (comment)
.

@bnoordhuis
Copy link
Member

@zladuric Invite sent. :-)

@Albert-IV
Copy link
Member

@bnoordhuis May I get an invite as well? :D

@bnoordhuis
Copy link
Member

@droppedoncaprica Sent!

@yoshuawuyts
Copy link

@bnoordhuis May I join also? ^__^

@Albert-IV
Copy link
Member

@bnoordhuis Thank you!

@bnoordhuis
Copy link
Member

@yoshuawuyts Sure, added.

@Mickael-van-der-Beek
Copy link

@bnoordhuis If it is still possible, could I also get an invite ?

@yoshuawuyts
Copy link

@bnoordhuis thanks! :D

@bnoordhuis
Copy link
Member

@Mickael-van-der-Beek Sure thing, invite sent.

@mediremi
Copy link

@bnoordhuis I would be interested in seeing what's in the repo. May I have an invite?

@Mickael-van-der-Beek
Copy link

@bnoordhuis Thank you very much !

@bnoordhuis
Copy link
Member

@medimatrix Of course. Invite under way.

@bnoordhuis
Copy link
Member

@tomgco @michaelnisi @jkrems @radicalsauce @lalitkapoor @yosuke-furukawa @diaswrd Invites in your inbox, welcome aboard.

@radicalsauce Yes, there are plenty of ways to get involved. See e.g. https://github.com/node-forward/mentors or pick an open bug (from either the node-forward/node or joyent/node bug tracker) and start hacking. Documentation fixes and bug triage are always welcome. If you are into IRC, we hang out in #node-forward on freenode.net. Let me know if you need help with anything. I'm bnoordhuis on IRC.

@radicalsauce
Copy link

@bnoordhuis - Outstanding! Thanks for the tips. I look forward to diving in.

@palmerabollo
Copy link

@Schoonology
Copy link
Member

@bnoordhuis - I'd love an invite.

@aselbie
Copy link

aselbie commented Nov 26, 2014

@bnoordhuis - May I have an invite?

@bnoordhuis
Copy link
Member

@palmerabollo @Schoonology @aselbie Invites in your inbox.

How's life on the East Coast, Schoon? :-)

@roryrjb
Copy link

roryrjb commented Nov 26, 2014

@bnoordhuis could I have an invite too? Many thanks in advance.

@bnoordhuis
Copy link
Member

@roryrjb No problem, invite sent.

@akshayp
Copy link
Member

akshayp commented Nov 26, 2014

@bnoordhuis I'd love an invite. Thank you for taking the time to give us all access 👍

@bnoordhuis
Copy link
Member

@akshayp You're welcome. :-) Invite sent.

@emkay
Copy link
Member

emkay commented Nov 28, 2014

@bnoordhuis hey can I get an invite when you have some time? Thanks!

@clarle
Copy link
Member

clarle commented Nov 28, 2014

@bnoordhuis - I'd love to have access. Thanks for doing this!

@egeozcan
Copy link

@bnoordhuis can I get an access too?

@jodytate
Copy link

@bnoordhuis could I also receive an invite? Thanks in advance.

@jacogr
Copy link

jacogr commented Nov 28, 2014

@bnoordhuis very interested to take a read-only peek. Thank you.

@victormx
Copy link

I hope i can get a invite too,thank's.

@bnoordhuis
Copy link
Member

@emkay @clarle @egeozcan @jodytate @jacogr @victormx Invites sent, welcome.

@ruimarinho
Copy link
Member

@bnoordhuis could you please send me an invite too? Thanks!

@lynchpin4
Copy link

if y'all are gonna be using this over on the @atom shell send me an invite too - thanks

@bnoordhuis
Copy link
Member

@ruimarinho @gstack Invites sent.

@greelgorke
Copy link

please, send me an invite too

@ruiquelhas
Copy link

Would love an invite also. Thanks.

@bnoordhuis
Copy link
Member

@greelgorke @ruiquelhas Invites sent.

@greelgorke
Copy link

thanks!

@timaschew
Copy link

May I get an invite? Thanks.

@19h
Copy link

19h commented Dec 1, 2014

And me. I'd like to help and join the development, thanks!

@bnoordhuis
Copy link
Member

@timaschew @KenanSulayman Certainly. Invites sent.

@rhbecker
Copy link

rhbecker commented Dec 1, 2014

requesting a read access invitation ... thanks

@bnoordhuis
Copy link
Member

@rhbecker No problem, invite sent.

@cjihrig
Copy link

cjihrig commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests