Archiving this repo

[jasnell]

The @nodejs/tsc has decided to archive this repo and move away from the node-eps process. See nodejs/TSC#335 for details.

[trevnorris]

@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]

Presumably in a separate working fork like what we've done with node-chakracore and http2 ... both of which worked out rather well.

[Fishrock123]

nodejs/TSC#335 (comment) (Me):

... I am not for this. I think it is useful and it should be used more.

[guybedford]

Would it make sense to revisit this decision given recent events?

[ljharb]

@guybedford what recent events?

[jasnell]

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]

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]

Superseded by nodejs/admin#160. Closing.