-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
It's currently private, we are probably waiting for things to get going a bit more and an actual announcement, I'd assume. |
I suspect it's just to prevent people from creating lots of issues and pull |
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. |
.. they would be |
@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. |
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. |
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. |
So, what is going on? How can one see what is going on in node-forward/node? |
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. |
It's taking some more time. If you want access to the repo, ping me. |
@bnoordhuis thank you, I would really love that |
@vkurchatkin Invitation sent. |
From what i understood, this is still limited access? No entry fOr us
|
That's correct, it's still private. I'll give read access to anyone who asks, though. |
Well then: can I please have read access? :-) Thanks, Zlatko
|
@zladuric Invite sent. :-) |
@bnoordhuis May I get an invite as well? :D |
@droppedoncaprica Sent! |
@bnoordhuis May I join also? ^__^ |
@bnoordhuis Thank you! |
@yoshuawuyts Sure, added. |
@bnoordhuis If it is still possible, could I also get an invite ? |
@bnoordhuis thanks! :D |
@Mickael-van-der-Beek Sure thing, invite sent. |
@bnoordhuis I would be interested in seeing what's in the repo. May I have an invite? |
@bnoordhuis Thank you very much ! |
@medimatrix Of course. Invite under way. |
@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. |
@bnoordhuis - Outstanding! Thanks for the tips. I look forward to diving in. |
✋ |
@bnoordhuis - I'd love an invite. |
@bnoordhuis - May I have an invite? |
@palmerabollo @Schoonology @aselbie Invites in your inbox. How's life on the East Coast, Schoon? :-) |
@bnoordhuis could I have an invite too? Many thanks in advance. |
@roryrjb No problem, invite sent. |
@bnoordhuis I'd love an invite. Thank you for taking the time to give us all access 👍 |
@akshayp You're welcome. :-) Invite sent. |
@bnoordhuis hey can I get an invite when you have some time? Thanks! |
@bnoordhuis - I'd love to have access. Thanks for doing this! |
@bnoordhuis can I get an access too? |
@bnoordhuis could I also receive an invite? Thanks in advance. |
@bnoordhuis very interested to take a read-only peek. Thank you. |
I hope i can get a invite too,thank's. |
@bnoordhuis could you please send me an invite too? Thanks! |
if y'all are gonna be using this over on the @atom shell send me an invite too - thanks |
@ruimarinho @gstack Invites sent. |
please, send me an invite too |
Would love an invite also. Thanks. |
@greelgorke @ruiquelhas Invites sent. |
thanks! |
May I get an invite? Thanks. |
And me. I'd like to help and join the development, thanks! |
@timaschew @KenanSulayman Certainly. Invites sent. |
requesting a read access invitation ... thanks |
@rhbecker No problem, invite sent. |
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. |
Last time I checked this organization has joyent/node forked repo. But now I can not see it. Am I missing something here ? :)
The text was updated successfully, but these errors were encountered: