nodejs/TSC on Hacker News

▲ 1

story by Brysonbw · 2025-07-13 · 0 comments

…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

comment by linkgoron · 2022-06-11 · in Bringing Forward the End-of-Life Date for Node.js 16

…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…

comment by Nicksil · 2021-11-26 · in In response to the moderation team resignation (Rust)

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...

comment by rangibaby · 2020-04-12 · in YouTube accidentally permanently terminated my account

> 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…

comment by matheusmoreira · 2019-10-29 · in Helping newcomers become contributors to open projects

…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?

▲ 2

Node.js Strategic Initiatives

story by stablemap · 2017-11-20 · 0 comments

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…

comment by wmmm · 2017-09-05 · in Rod Vagg's statement on the request to be removed from the Node.js CTC

> 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…

comment by wmmm · 2017-09-05 · in Rod Vagg's statement on the request to be removed from the Node.js CTC

▲ 1

Meta: merge the TSC and CTC back into a single entity

story by awjr · 2017-08-31 · 0 comments

▲ 2

Node.js TSC and CTC re-merged

story by krlkv · 2017-08-30 · 0 comments

▲ 4

Node.js CTC and TSC have been merged back together

story by akras14 · 2017-08-29 · 2 comments

see also: https://github.com/nodejs/TSC/issues/324 https://www.reddit.com/r/node/comments/6whs2e/multiple_coc_v... https://archive.is/YnGGz

comment by maxharris · 2017-08-28 · in Ashleygwilliams and zkat have been harassing other node contributors

…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

comment by tekacs · 2017-08-27 · in After governance breakdown, Node.js leaders fight for its survival

…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...

comment by tekacs · 2017-08-27 · in After governance breakdown, Node.js leaders fight for its survival

…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

comment by brudgers · 2017-08-26 · in Rod Vagg's statement on the request to be removed from the Node.js CTC

The code of conduct is here: https://github.com/nodejs/TSC/blob/master/CODE_OF_CONDUCT.md

comment by brudgers · 2017-08-26 · in Rod Vagg's statement on the request to be removed from the Node.js CTC

Fortunately, somebody already took a snapshot and there's a way back : https://web.archive.org/web/20170821212745/https://github.co...

comment by pvorb · 2017-08-25 · in Rod Vagg's statement on the request to be removed from the Node.js CTC

…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…

comment by zbentley · 2017-08-25 · in Rod Vagg's statement on the request to be removed from the Node.js CTC

…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

comment by orless · 2017-08-25 · in Rod Vagg's statement on the request to be removed from the Node.js CTC

▲ 2

Meta: vote regarding Rod's status on the TSC – Issue #310 – Node.js/TSC

story by eibrahim · 2017-08-25 · 0 comments

…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

…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

…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…

comment by akras14 · 2017-08-23 · in Node.js is forked to Ayo.js (pronounced like “IO”)

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...

comment by slang800 · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

…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

comment by gedy · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

…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…

comment by geofft · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

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…

comment by strictnein · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

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…

comment by geofft · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

Pre-redaction details are here: https://web.archive.org/web/20170821212745/https://github.co...

comment by pimterry · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

There is a list here: https://web.archive.org/web/20170821212745/https://github.co...

comment by Others · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

…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

comment by iamthepieman · 2017-08-22 · in Effective immediately I am stepping down from the Nodejs TSC

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

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

…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

▲ 4

Express Applies to Become a Node “Top Level Project”

story by wesleytodd · 2016-01-30 · 0 comments

▲ 22

IBM is applying to move Express to the Node.js Foundation

story by creamyhorror · 2016-01-29 · 1 comment