Skip to content
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.

Current Status? #628

Open
jasnell opened this issue Feb 3, 2020 · 2 comments
Open

Current Status? #628

jasnell opened this issue Feb 3, 2020 · 2 comments

Comments

@jasnell
Copy link
Member

jasnell commented Feb 3, 2020

@nodejs/node-chakracore ... What is the current status of this project? We've previously made accommodations in nodejs/node master to help here (e.g. AliasedBuffer) that aren't really needed elsewhere so it would be great to know if those are still necessary.

If this project is not moving forward, we should archive this repo.

@cjihrig
Copy link
Contributor

cjihrig commented Feb 11, 2020

+1 to archiving this if there is no response from @nodejs/node-chakracore by Monday (Feb 17), as there are also a number of security vulnerabilities reported by GitHub here every week.

@divmain
Copy link

divmain commented Feb 14, 2020

node-chakracore no longer aligns with our long-term strategy. That being the case, we have no objection to archival. We also want to express our thanks for your partnership in moving this project forward over the last several years.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants