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

node-forward/node deactivation #192

Closed
19h opened this issue Dec 21, 2014 · 5 comments
Closed

node-forward/node deactivation #192

19h opened this issue Dec 21, 2014 · 5 comments

Comments

@19h
Copy link
Contributor

19h commented Dec 21, 2014

The TC addendum from 10 days ago mentions the node-forward/node repository:

6014f5c#diff-5f0aa123070e5ca6eb6c0ed9b4b3cc76R41

However, it is disabled now: ("This repository has been disabled.")

https://github.com/node-forward/node

Either this lacks a note or it went past me. Could you please clarify?

Thanks 🚶

@19h 19h changed the title node-forward/node node-forward/node deactivation Dec 21, 2014
@algesten
Copy link

the node-forward/node repository was disabled because when it was put out there, Joyent/Scott Hammond flagged it as a potential infringement of Joyent's trademarks. this is the whole reason for io.js being called "io.js"

@19h
Copy link
Contributor Author

19h commented Dec 21, 2014

Well, I am aware of that. I was able to see both repos tho and it wasn't disabled. Additionally AFAIK Joyents trademark of Node was pulled thus not enforceable. .. So after all it was disabled due to Joyents' struggle against io.js independence? 😕

@algesten
Copy link

io.js was set up by Fedor Indutny, after node-forward/node was disabled. and Fedor also got the main contributors, who were behind node-forward/node, on board with io.js. Joyent has, as far as I know, not made any struggle against io.js. They discussed it in the node advisory board https://github.com/joyent/nodejs-advisory-board/blob/master/meetings/2014-12-04/minutes.md#iojs-fork-scott-hammond and decided that Scott Hammond is to draft "AB Position on io.js". Likewise they're looking to io.js for a statement on the relationship with joyent/node. Whether the goal is to merge back etc.

@mikeal
Copy link
Contributor

mikeal commented Dec 22, 2014

It was private, I created an Issue informing everyone that it was deprecated a while ago. We changed the plan on this org from Bronze to Free which disabled any private repos, that's why it now shows as "disabled."

@19h
Copy link
Contributor Author

19h commented Dec 25, 2014

Thanks @mikeal for clearing up!

@19h 19h closed this as completed Dec 25, 2014
eti-p-doray pushed a commit to eti-p-doray/node that referenced this issue Aug 28, 2024
eti-p-doray pushed a commit to eti-p-doray/node that referenced this issue Aug 28, 2024
* [wasi] Stop using V8 fast API

* Revert "[wasi] Stop using V8 fast API"

This reverts commit 0d5d171.

* Revert "[v8] Stop using deprecated fields of v8::FastApiCallbackOptions (nodejs#192)"

This reverts commit 286ed38.
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

3 participants