nodejs/CTC
View on GitHub ↗ ★ 80 archived
Node.js Core Technical Committee & Collaborators
7 mentions on Hacker News by 6 people: 2 stories, 5 comments · first 2017-05-09 · latest 2018-09-19
20082026
-
…the CoC doing the weaponizing. Here are a few examples: * https://bugs.ruby-lang.org/issues/12004 * https://github.com/nodejs/CTC/issues/165 * https://github.com/opal/opal/issues/941 And really you can just go to CoralineAda's twitter to…
comment by malvosenior · 2018-09-19 · in Code, conflict, and conduct -
…his peers had plenty of blatantly sexist tweets and received no reports for CoC violations.[3] 1. https://github.com/nodejs/CTC/issues/165 2. https://quillette.com/2017/07/18/neurodiversity-case-free-sp... 3. Such as…
comment by chroma · 2018-09-19 · in Code, conflict, and conduct -
https://github.com/nodejs/CTC/issues/165 I assume that they forked because they don't believe Rod should be on the node leadership teams.
comment by sb8244 · 2017-08-26 · in Nvm will **not** be adding support for Ayo.js -
▲ 214
Rod Vagg's statement on the request to be removed from the Node.js CTCstory by krlkv · 2017-08-25 · 170 comments
-
rvagg responds: https://github.com/nodejs/CTC/issues/165#issuecomment-324798...
comment by styfle · 2017-08-25 · in Node.js is forked to Ayo.js (pronounced like “IO”) -
▲ 4
Rod Vagg's statementstory by seishun · 2017-08-25 · 0 comments
-
More info about why this landed can be found here: https://github.com/nodejs/CTC/issues/12
comment by styfle · 2017-05-09 · in Node.js promisify in core