community-committee

The Node.js Community Committee (aka CommComm)

2Distinct people

2Mentions

0Explicit recommenders

261GitHub stars

REPOSITORY AT A GLANCE

What to know before exploring

The Node.js Community Committee (aka CommComm)

GitHub

No documented product use has been verified yet.

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.

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

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.

HN mentions by 6-hour interval2 dated mentions

Observed mentions: 2017-08-22 15:13:15 UTC to 2017-08-27 13:46:55 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

UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
Period	Start (UTC)	End (exclusive, UTC)	Mentions	Comments
Aug 22, 12:00	2017-08-22 12:00:00 UTC	2017-08-22 18:00:00 UTC	1	1
Aug 22, 18:00	2017-08-22 18:00:00 UTC	2017-08-23 00:00:00 UTC	0	0
Aug 23, 00:00	2017-08-23 00:00:00 UTC	2017-08-23 06:00:00 UTC	0	0
Aug 23, 06:00	2017-08-23 06:00:00 UTC	2017-08-23 12:00:00 UTC	0	0
Aug 23, 12:00	2017-08-23 12:00:00 UTC	2017-08-23 18:00:00 UTC	0	0
Aug 23, 18:00	2017-08-23 18:00:00 UTC	2017-08-24 00:00:00 UTC	0	0
Aug 24, 00:00	2017-08-24 00:00:00 UTC	2017-08-24 06:00:00 UTC	0	0
Aug 24, 06:00	2017-08-24 06:00:00 UTC	2017-08-24 12:00:00 UTC	0	0
Aug 24, 12:00	2017-08-24 12:00:00 UTC	2017-08-24 18:00:00 UTC	0	0
Aug 24, 18:00	2017-08-24 18:00:00 UTC	2017-08-25 00:00:00 UTC	0	0
Aug 25, 00:00	2017-08-25 00:00:00 UTC	2017-08-25 06:00:00 UTC	0	0
Aug 25, 06:00	2017-08-25 06:00:00 UTC	2017-08-25 12:00:00 UTC	0	0
Aug 25, 12:00	2017-08-25 12:00:00 UTC	2017-08-25 18:00:00 UTC	0	0
Aug 25, 18:00	2017-08-25 18:00:00 UTC	2017-08-26 00:00:00 UTC	0	0
Aug 26, 00:00	2017-08-26 00:00:00 UTC	2017-08-26 06:00:00 UTC	0	0
Aug 26, 06:00	2017-08-26 06:00:00 UTC	2017-08-26 12:00:00 UTC	0	0
Aug 26, 12:00	2017-08-26 12:00:00 UTC	2017-08-26 18:00:00 UTC	0	0
Aug 26, 18:00	2017-08-26 18:00:00 UTC	2017-08-27 00:00:00 UTC	0	0
Aug 27, 00:00	2017-08-27 00:00:00 UTC	2017-08-27 06:00:00 UTC	0	0
Aug 27, 06:00	2017-08-27 06:00:00 UTC	2017-08-27 12:00:00 UTC	0	0
Aug 27, 12:00	2017-08-27 12:00:00 UTC	2017-08-27 18:00:00 UTC	1	1

2 sources

The canonical source [1] on the Node side seems to have been fully redacted at this time, so here's the post in the community forum where people are discussing the issue [2]. Once again not taking sides (although this article seems to have dropped off the homepage). [1]: https://github.com/nodejs/TSC/issues/310 [2]: https://github.com/nodejs/community-committee/issues/111

https://github.com/nodejs/community-committee/issues/111 has a screenshot of the text previously in https://github.com/nodejs/TSC/issues/310 because "listing the issues was not fair to Rod". I'm an outsider to this, but it seems to me that the tl;dr was that he was basically undermining the moderation actions of the TSC and CTC.