You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 15, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 15, 2025. It is now read-only.
The issue tracker in this repo has grown around 35+ more issues that have not/partially been addressed since the latest change to the repo.
Questions
Is this repository still maintained?
If it is not maintained anymore, should there be a banner indicating it / should their be a call for maintainers?
This issue is not meant to be aggressive or negative in any ways, I just stumbled upon the above and figured it was worth clarifying the current status of the repository.
Thanks! 🙏
Reacted by Liam Conrad, jurekl, Sergio Kovtunenko, udfordria and Dmitriy Tikhomirov
I suggest adding a small banner in the README to notify people of the status. WDYT?
In addition to that, it's a bit complicated for anyone to know what taking on the maintenance of this repo looks like. What are the next steps? Where should one start? Are there how-to's and guides that I'm not aware of?
Should there be a call for maintainers on the #golang-nuts Google Groups? Maybe there's been one already, sorry if that is the case.
Reacted by Ivan Tarbakou, mightatnight, nuric, Sergio Kovtunenko, Aleksandr Shalimov, udfordria and Dmitriy Tikhomirov
I am willing to become a maintainer and support the repository, keeping it up to date.
I see that many fixes and updates can still be done and many new issues have been created and are waiting for attention.
Ready to take over this repository if it is transferred to me.
Activity
taowen commentedon Jan 8, 2025
looking for a maintainer
mlevieux commentedon Jan 8, 2025
Hello @taowen ! Thanks for the answer 🙏
I suggest adding a small banner in the
READMEto notify people of the status. WDYT?In addition to that, it's a bit complicated for anyone to know what taking on the maintenance of this repo looks like. What are the next steps? Where should one start? Are there how-to's and guides that I'm not aware of?
Should there be a call for maintainers on the #golang-nuts Google Groups? Maybe there's been one already, sorry if that is the case.
Sagleft commentedon Feb 15, 2025
I am willing to become a maintainer and support the repository, keeping it up to date.
I see that many fixes and updates can still be done and many new issues have been created and are waiting for attention.
Ready to take over this repository if it is transferred to me.
my contact for communication: https://t.me/sagleft