search

nodejs / node-eps

Node.js Enhancement Proposals for discussion on future API additions/changes to Node core
442 stars 66 forks source link

Archiving this repo #65

Closed jasnell closed 6 years ago

jasnell commented 7 years ago

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

trevnorris commented 7 years ago

@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 commented 7 years ago

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

Fishrock123 commented 7 years ago

https://github.com/nodejs/TSC/issues/335#issuecomment-330893808 (Me):

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

guybedford commented 6 years ago

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

ljharb commented 6 years ago

@guybedford what recent events?

jasnell commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

Superseded by https://github.com/nodejs/admin/issues/160. Closing.