-
Notifications
You must be signed in to change notification settings - Fork 318
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 repo dead? #184
Comments
Yes, it is obviously dead: There used to be around four releases per year until 2019 and no interaction from grafov since that year. There are some forks which are actively maintained, e.g.: As they don't have public issue trackers, I don't know how interested they are in collaboration with external users. |
Well. I have a little time for the project. The code is still used in a couple of proprietary projects. May be it is dangerous due to issues of the project but the proprietary code ...ok you know ) The patches and maintaining for the project are welcome. My email [email protected] or you can reach me in the issues. Unfortunataly my professional activity moved from video streaming several years ago. But I continue to work with Go language. I think the best way it is move the project under umbrella of some non profit organization who interested in Go libraries. Or add new maintainers who interest in this code in their projects. There was persons who maintain the project after me. I appreciated their help very much. But any of us sometime change their interests or professional area so last years the project abandoned. Ok, I'll try to keep the code anyway ) If you have actively maintainad replacements I'll put the links to README. |
Thank you added to readme. |
Is this repo dead?
No PR responses and... A lot of the DeepSource-PR failures are are red because of stuff already on master.
The text was updated successfully, but these errors were encountered: