node-forward/node deactivation

[19h]

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 🚶

[algesten]

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]

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]

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]

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]

Thanks @mikeal for clearing up!