DAdankohn1·Mar 25, 2015Submission
Draft Node.js Foundation Technical Governance Proposal
3 points · Open discussionjoyent
nodejs-advisory-board
Web Development2014–2015
joyent / nodejs-advisory-board · Archived
nodejs-advisory-board
Meeting Minutes and Working Group Discussions
5Distinct people
5Mentions
0Explicit recommenders
157GitHub stars
What to know before exploring
What it is
Meeting Minutes and Working Group Discussions
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week5 dated mentions
Observed mentions: 2014-11-12 09:29:27 UTC to 2015-03-25 15:47:04 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 10 | 2014-11-10 00:00:00 UTC | 2014-11-17 00:00:00 UTC | 1 | 1 | 0 |
| Nov 17 | 2014-11-17 00:00:00 UTC | 2014-11-24 00:00:00 UTC | 0 | 0 | 0 |
| Nov 24 | 2014-11-24 00:00:00 UTC | 2014-12-01 00:00:00 UTC | 2 | 0 | 2 |
| Dec 1 | 2014-12-01 00:00:00 UTC | 2014-12-08 00:00:00 UTC | 0 | 0 | 0 |
| Dec 8 | 2014-12-08 00:00:00 UTC | 2014-12-15 00:00:00 UTC | 0 | 0 | 0 |
| Dec 15 | 2014-12-15 00:00:00 UTC | 2014-12-22 00:00:00 UTC | 0 | 0 | 0 |
| Dec 22 | 2014-12-22 00:00:00 UTC | 2014-12-29 00:00:00 UTC | 0 | 0 | 0 |
| Dec 29 | 2014-12-29 00:00:00 UTC | 2015-01-05 00:00:00 UTC | 0 | 0 | 0 |
| Jan 5 | 2015-01-05 00:00:00 UTC | 2015-01-12 00:00:00 UTC | 0 | 0 | 0 |
| Jan 12 | 2015-01-12 00:00:00 UTC | 2015-01-19 00:00:00 UTC | 1 | 0 | 1 |
| Jan 19 | 2015-01-19 00:00:00 UTC | 2015-01-26 00:00:00 UTC | 0 | 0 | 0 |
| Jan 26 | 2015-01-26 00:00:00 UTC | 2015-02-02 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2 | 2015-02-02 00:00:00 UTC | 2015-02-09 00:00:00 UTC | 0 | 0 | 0 |
| Feb 9 | 2015-02-09 00:00:00 UTC | 2015-02-16 00:00:00 UTC | 0 | 0 | 0 |
| Feb 16 | 2015-02-16 00:00:00 UTC | 2015-02-23 00:00:00 UTC | 0 | 0 | 0 |
| Feb 23 | 2015-02-23 00:00:00 UTC | 2015-03-02 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2 | 2015-03-02 00:00:00 UTC | 2015-03-09 00:00:00 UTC | 0 | 0 | 0 |
| Mar 9 | 2015-03-09 00:00:00 UTC | 2015-03-16 00:00:00 UTC | 0 | 0 | 0 |
| Mar 16 | 2015-03-16 00:00:00 UTC | 2015-03-23 00:00:00 UTC | 0 | 0 | 0 |
| Mar 23 | 2015-03-23 00:00:00 UTC | 2015-03-30 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
5 sourcesHere's the most recent minutes (2014-12-19) for the Node.js Advisory Board where they discussed Io.js (while considering their 0.12 release).
https://github.com/joyent/nodejs-advisory-board/blob/master/...
In Io.js 1.0.0Sorry for the delay, it takes a while to polish the minutes and then gain consensus from the rest of the group about the final minutes. The US Holiday didn't help much either (as well as finalizing RobotsConf, life, etc) They are here now: https://github.com/joyent/nodejs-advisory-board/blob/master/...
In IO.js – Evented I/O for V8 javascriptI don't have very specific details as I'm a bystander too but it seems Node has been stuck in 0.10.x land since early 2013 (http://blog.nodejs.org/2013/03/11/node-v0-10-0-stable/) while Node 0.12 and 1.0 releases were being talked about well over a year ago by former BDFL Isaac Schlueter (now at npm). Joyent, the current project stewards, have not been able to deliver a stable release in that time and don't share public plans / aren't communicating very much.
One of the many symptoms of that slow development process is that Node.js is basically running an unsupported version of V8 (https://twitter.com/jmayer/status/532971494695907328).
From what I've read, node-forward is/was only meant as a fork in the GitHub sense: they'd try to get their stuff merged back into node mainline. The GitHub fork has since been made private (https://github.c
Read the rest
om/node-forward/discussions/issues/7) and they're working to set up a proper governance model so that the community can truly be in charge. Joyent has reacted (I believe, it might have been in the works prior to node-forward) by proposing a node advisory board (https://github.com/joyent/nodejs-advisory-board) but it seems to be too little too late for at least some of the people behind node-forward (I've read what seem like irreconcilable disagreements about how it should be run).
I have no idea what (if anything) io.js is in relation to node-forward or if the same people are behind it. Can't find any announcements / endorsements on Twitter, so maybe it was just posted here before whoever is behind it were ready to go live.
Node.js Advisory Board Meeting Minutes and Working Group Discussions
31 points · Open discussion