-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archival of the node-chakracore repo #821
Comments
I had a brief chat with @aruneshchandra a week or so ago. They are working on a deprecation strategy for node-chakracore with the folks they know were making use of it. It would likely be best to avoid archiving until after confirmation from msft that the deprecation process has been defined. |
That said, I'm +1 on archiving as soon as we get a go-ahead from the msft folks |
+1 to archive once we have confirmation from the msft folks |
+1 to archive as soon as there is confirmation, but let's wait for a while until that happens |
Hey everybody - thanks for being patient as we work things out on our end. We have no objection to archiving |
Thank you @divmain. I've gone ahead and archived it. |
Hello everyone. ChakraCore will be owned by community soon (chakra-core/ChakraCore#6384). There are some discussions on making Node ChakraCore active again. Would it be possible to unarchieve the repo in future if work on Node ChakraCore will be resumed? |
I'd personally be fine with unarchiving the repo if people plan to actively work on it. A revived effort could also live outside of the nodejs org. |
TL;DR - Microsoft doesn't plan to maintain the repo anymore.
See nodejs/node-chakracore#628 for all of the details.
I'd like to archive this repo. Is anyone opposed to doing so?
The text was updated successfully, but these errors were encountered: