-
Notifications
You must be signed in to change notification settings - Fork 307
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
Proposal To Archive The Intern Project #1210
Comments
Maybe there would be someone who would like to continue to maintain it? Forks, maybe? If there was a good knowledge share, I think it could be possible. |
We are still actively using this on a day-by-day basis. Does archiving mean that any pull request will also be impossible to be accepted? |
Archiving would essentially make the repo read-only, so no more PRs would be possible at that point. If you're still using it internally and need to make minor updates, one option would be to fork the project and republish it under a different name and/or to an alternative repository such as GitHub Packages. |
The reason I visited this repo today (and stumbled on this discussion) was because of a regression in starting the Chrome driver. If there are any other people still using Intern, then it would be useful to see if they are experiencing the same problem. That would also become more difficult. Then again, maybe there just aren't that many users anymore. Just out of curiosity, if people stopped using intern, which alternative did they migrate too? Maybe that would provide us with an adequate solution too. |
The OpenJS Foundation is proposing that the Intern project be archived.
This is due toJ ason Cheatham informing us that this project is no longer active. @jason0x43
Note the final decision on archiving is made via CPC consensus and with the approval of the maintainers of the project.
If folks believe this project should not be archived please comment in this thread.
Thank you!
The text was updated successfully, but these errors were encountered: