This repository was archived by the owner on Jul 31, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 31, 2018. It is now read-only.
Archiving this repo #65
Description
The @nodejs/tsc has decided to archive this repo and move away from the node-eps process. See nodejs/TSC#335 for details.
Reacted by Tierney Cyren
Reacted by Tierney Cyren
Activity
trevnorris commentedon Sep 14, 2017
@jasnell so would the large number of comments for modules not have happened if it'd been placed in a PR? and where would a proposal like es modules have gone for implementation discussion?
jasnell commentedon Sep 14, 2017
Presumably in a separate working fork like what we've done with node-chakracore and http2 ... both of which worked out rather well.
Fishrock123 commentedon Sep 20, 2017
nodejs/TSC#335 (comment) (Me):
guybedford commentedon Mar 19, 2018
Would it make sense to revisit this decision given recent events?
ljharb commentedon Mar 19, 2018
@guybedford what recent events?
jasnell commentedon Mar 19, 2018
I don't believe so. There's nothing that could be done here that can't be done working on actual code in working repos.
guybedford commentedon Mar 19, 2018
I'm referring to the discussions in the current fetch / websocket feature issues in the main repo.
Yeah it doesn't seem this repo would help that either.
Perhaps some process around curated long discussions would be useful though - for example if I knew I was posting a particularly controversial feature request / issue discussion / PR to be able to create and link to a special discussion page that would have curation and per-comment voting / threading. Is there anything close to this in place currently?
Trott commentedon Jun 12, 2018
Superseded by nodejs/admin#160. Closing.