Hacker GitHub

← All repos

nodejs/TSC

View on GitHub ↗ ★ 693 JavaScript

The Node.js Technical Steering Committee

37 mentions on Hacker News by 31 people: 8 stories, 29 comments · first 2016-01-29 · latest 2025-07-13

Mentions per year 37 mentions · busiest year 2017 (28)
20082026
  1. …upgrading, but obviously it was too backwards-compatibility breaking to land without a new major. https://github.com/nodejs/TSC/issues/1222 https://github.com/nodejs/TSC/pull/859
  2. …thread https://old.reddit.com/r/node/comments/6whs2e/multiple_coc_v... NodeJS GitHub issue thread https://github.com/nodejs/TSC/issues/324 HN threads https://news.ycombinator.com/item?id=16085545 https://news.ycombinator.com/item?id=1511598…
  3. A person (people?) got really angry about the eggplant emoji a few years ago: https://github.com/nodejs/TSC/issues/8 https://www.reddit.com/r/KotakuInAction/comments/3xtep0/socj...
  4. > I would be interested in seeing these. I have some links bookmarked: https://github.com/nodejs/TSC/issues/325 https://archive.is/XcxSf https://archive.is/YnGGz https://archive.is/EJmJ7 That directly followed a failed attempt at…
  5. …want to be reflected in the project? So why were there no consequences following this report? https://github.com/nodejs/TSC/issues/324 The Twitter in question clearly is associated with Node.js: https://twitter.com/ag_dubs >@nodejs…
    comment by matheusmoreira · 2018-05-08 · in Who controls glibc?
  6. HAVE YOU EVEN SEEN THE ACCUSATIONS? HERE IT IS: https://web.archive.org/web/20170821212745/https://github.co... 1. "Rod’s first action was to apologize to a contributor who had been repeatedly moderated" 2. "Rod did not moderate himself…
  7. > James Snell's reasoning behind hiding the accusations inside the committee deliberations is theoretically sound: to keep Rod from getting harassed. No. It is not. Saying that the specific accusations were removed to keep Rod from getting…
  8. see also: https://github.com/nodejs/TSC/issues/324 https://www.reddit.com/r/node/comments/6whs2e/multiple_coc_v... https://archive.is/YnGGz
  9. …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
  10. …read everything yet, I'm just gathering links for people to draw their own conclusions. [1]: https://github.com/nodejs/TSC/issues/310 [2]: https://medium.com/@rvagg/the-truth-about-rod-vagg-f063f6a53...
  11. …to have acted contrary to good faith. I don't see evidence to support that conspiracy theory. [1]: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md
  12. The code of conduct is here: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md
  13. Fortunately, somebody already took a snapshot and there's a way back : https://web.archive.org/web/20170821212745/https://github.co...
  14. …collaboration and community-building. There was once a list of grievances against this person here https://github.com/nodejs/TSC/issues/310 . That list is no longer present; it has been redacted, and a reason for that redaction has been…
  15. …it is "Other conduct which could reasonably be considered inappropriate in a professional setting". https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md
  16. …anything wrong. He merely apologized for having to censor someone because the CoC is pretty vague: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md It's not a violation of the CoC. They are attacking him for their perceived…
    comment by chisleu · 2017-08-23 · in Node.js has forked into Ayo
  17. …gets repeated all the time, yet no one has ever shown any supporting evidence AFAIK. [0] https://github.com/nodejs/TSC
    comment by bauerd · 2017-08-23 · in Node.js has forked into Ayo
  18. …and follow up comments were considered inappropriate by some. Even more details here: https://github.com/nodejs/TSC/issues/310 """ The TSC members were not able to reach a natural consensus on the steps forward so a vote was called on two…
  19. Well, it ended up getting archived before the list was removed. Whether that's right or wrong, the info is out there: https://web.archive.org/web/20170821212745/https://github.co...
  20. …due to non-technical matters. Merging the CTC and TSC sounds like a smart approach to balance this: https://github.com/nodejs/TSC/issues/312
  21. …committee has lots of jobs, yes. One of them is the maintaining and enforcing the Code of Conduct: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md I think it's totally fine for a member of the group to disagree privately with…
  22. The unredacted details still feel like they're missing something: https://web.archive.org/web/20170821212745/https://github.co... "...Rod’s first action was to apologize to a contributor who had been repeatedly moderated. Rod did not…
  23. 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…
  24. Pre-redaction details are here: https://web.archive.org/web/20170821212745/https://github.co...
  25. There is a list here: https://web.archive.org/web/20170821212745/https://github.co...
  26. …he would be better served by sticking around to work on the revisions to the code of conduct [0] https://github.com/nodejs/TSC/issues/310
  27. Full details: main issue is that someone posted a link against CoCs, then subsequently screenshotted abusive tweets they received: http://webcache.googleusercontent.com/search?q=cache:https:/...
    comment by nailer · 2017-08-22 · in NPM staffer forks Node again
  28. The why is here: https://github.com/nodejs/TSC/issues/310 Beyond that, the last fork forced some positive changes. I hope this one does the same.
    comment by hermanradtke · 2017-08-22 · in NPM staffer forks Node again
  29. …around the same time as some other npm drama (e.g. https://github.com/nodejs/node/issues/3959 and https://github.com/nodejs/TSC/issues/21 and https://github.com/nodejs/NG/issues/26 , leading up to https://github.com/nodejs/NG/issues/29 )…
    comment by pluma · 2016-03-23 · in I've Just Liberated My Modules