-
Notifications
You must be signed in to change notification settings - Fork 96
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
Is this project dead? Time to fork? … #79
Comments
I could. But will need the community support for it though, of course. |
I would still prefer that @wolever revive this project. Maybe add some of us as a collaborator to the project? |
@wolever has not bothered fixing a critical bug in this code for six months even though there is a PR fixing it. Now, there are good reasons why someone can be away from a project for that long. However, not hearing anything from them, it is hard to judge what those reasons are and what we can do to help. We could set up a joint community to fork this… I know it is possible but have not done so. |
@wolever is holding an AMA today. https://twitter.com/SpankChain/status/1047549330817736704 Unfortunately I won't be able to join. Could you join and try to talk to him? |
@safiyat No, I cannot make it. Besides, I have not been inflected by tweeter. |
We should fork this and move on. We've reached out to @wolever many times with no response. He's active on twitter and apparently doesn't want to maintain this project. |
Ahh, folks, I'm so sorry :( I have no excuse for the tardiness. Commenting on the PR now. |
@adam820 I am pretty sure that it is. |
A PR which fixes #73 and #74 still has not been merged after six months. This point to this project being dead.
Does anyone have the time to fork it and maintain it?
The text was updated successfully, but these errors were encountered: