-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Archive the repo? #179
Comments
It looks like the maintainer posted a general Help Wanted ad in July of 2020: http://bitprophet.org/blog/2020/07/02/help-wanted/ Seems a better alternative to archiving the repo (for now), would be to see if we can find enough help and/or someone qualified to take over the maintainer role. |
I seem to vaguely recall reading that post. It doesn't mention this specific project, though. |
Typically burn out effects all projects 😞 |
cc @bitprophet ☝️ |
Alabaster's kind of inbetween - yes, burnout, but also it's (slightly) less prone to bitrot than my other projects / is in a more stable place so its priority always lags behind the others :( I'm intending to see whether I can convince some of the Sphinx contributors to take it over, since it's the default there now. There will be announcements if/when that happens and I assume it'd move into their GH org. |
Glad to hear there are conversations with some of the Sphinx contributors, I tried to look but couldn't find any. |
There hasn't been a release since 2018 and the last commit implies that this project isn't going to be maintained anymore. So it'd probably be reasonable to just archive it or at least pin an issue + a readme message stating the status explicitly.
The text was updated successfully, but these errors were encountered: