HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nodejs
board
JavaScript2017–2017
nodejs / board · Archived

board

The Node Foundation Board of Directors

5Distinct people
5Mentions
0Explicit recommenders
52GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The Node Foundation Board of Directors

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, 11:56:56 AM 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 hour5 dated mentions

Observed mentions: 2017-08-24 13:24:20 UTC to 2017-08-25 14:40:25 UTC.

0122017-08-24 13:00:00 UTC to 2017-08-24 14:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsAug 24, 13:002017-08-24 14:00:00 UTC to 2017-08-24 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 15:00:00 UTC to 2017-08-24 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 16:00:00 UTC to 2017-08-24 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 17:00:00 UTC to 2017-08-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 18:00:00 UTC to 2017-08-24 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 19:00:00 UTC to 2017-08-24 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 20:00:00 UTC to 2017-08-24 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 21:00:00 UTC to 2017-08-24 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 22:00:00 UTC to 2017-08-24 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-24 23:00:00 UTC to 2017-08-25 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-08-25 00:00:00 UTC to 2017-08-25 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 01:00:00 UTC to 2017-08-25 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 25, 01:002017-08-25 02:00:00 UTC to 2017-08-25 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 03:00:00 UTC to 2017-08-25 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 04:00:00 UTC to 2017-08-25 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 05:00:00 UTC to 2017-08-25 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2017-08-25 06:00:00 UTC to 2017-08-25 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 07:00:00 UTC to 2017-08-25 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 08:00:00 UTC to 2017-08-25 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 09:00:00 UTC to 2017-08-25 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 10:00:00 UTC to 2017-08-25 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 11:00:00 UTC to 2017-08-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 12:00:00 UTC to 2017-08-25 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 13:00:00 UTC to 2017-08-25 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-25 14:00:00 UTC to 2017-08-25 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 25, 14:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 24, 13:002017-08-24 13:00:00 UTC2017-08-24 14:00:00 UTC211
Aug 24, 14:002017-08-24 14:00:00 UTC2017-08-24 15:00:00 UTC000
Aug 24, 15:002017-08-24 15:00:00 UTC2017-08-24 16:00:00 UTC000
Aug 24, 16:002017-08-24 16:00:00 UTC2017-08-24 17:00:00 UTC000
Aug 24, 17:002017-08-24 17:00:00 UTC2017-08-24 18:00:00 UTC000
Aug 24, 18:002017-08-24 18:00:00 UTC2017-08-24 19:00:00 UTC000
Aug 24, 19:002017-08-24 19:00:00 UTC2017-08-24 20:00:00 UTC000
Aug 24, 20:002017-08-24 20:00:00 UTC2017-08-24 21:00:00 UTC000
Aug 24, 21:002017-08-24 21:00:00 UTC2017-08-24 22:00:00 UTC000
Aug 24, 22:002017-08-24 22:00:00 UTC2017-08-24 23:00:00 UTC000
Aug 24, 23:002017-08-24 23:00:00 UTC2017-08-25 00:00:00 UTC101
Aug 25, 00:002017-08-25 00:00:00 UTC2017-08-25 01:00:00 UTC000
Aug 25, 01:002017-08-25 01:00:00 UTC2017-08-25 02:00:00 UTC000
Aug 25, 02:002017-08-25 02:00:00 UTC2017-08-25 03:00:00 UTC000
Aug 25, 03:002017-08-25 03:00:00 UTC2017-08-25 04:00:00 UTC000
Aug 25, 04:002017-08-25 04:00:00 UTC2017-08-25 05:00:00 UTC000
Aug 25, 05:002017-08-25 05:00:00 UTC2017-08-25 06:00:00 UTC101
Aug 25, 06:002017-08-25 06:00:00 UTC2017-08-25 07:00:00 UTC000
Aug 25, 07:002017-08-25 07:00:00 UTC2017-08-25 08:00:00 UTC000
Aug 25, 08:002017-08-25 08:00:00 UTC2017-08-25 09:00:00 UTC000
Aug 25, 09:002017-08-25 09:00:00 UTC2017-08-25 10:00:00 UTC000
Aug 25, 10:002017-08-25 10:00:00 UTC2017-08-25 11:00:00 UTC000
Aug 25, 11:002017-08-25 11:00:00 UTC2017-08-25 12:00:00 UTC000
Aug 25, 12:002017-08-25 12:00:00 UTC2017-08-25 13:00:00 UTC000
Aug 25, 13:002017-08-25 13:00:00 UTC2017-08-25 14:00:00 UTC000
Aug 25, 14:002017-08-25 14:00:00 UTC2017-08-25 15:00:00 UTC101

What Hacker News says

5 sources
(after reading through https://github.com/nodejs/board/issues/58 and other issues related to this situation) The Github comment revision needs to stop. It makes it impossible for people who were not involved in the original conversation to understand what actually happened. Without a full archive of all revisions, you cannot even judge if the edits were made in good faith or if the current text represents the author's original intent. It casts doubt on everything. The whole mess is even worse on long threads like the ones linked to. Editing a comment that other users responded to can make the responding comments look silly or stupid, or completely change the meaning of their response. This is mostly a process thing but Github also needs to improve how edits are handled.
In The Truth About Rod Vagg

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.