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
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! 🙏
The text was updated successfully, but these errors were encountered:
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.
Context
The last update in this repo dates back 2+ years ago (Sep 16, 2022).
The
encoding/json
library has evolved (slightly yet) e.g. https://go.dev/doc/go1.22#minor_library_changes (see this code snippet), and will evolve in the future (e.g. golang/go#45669).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
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! 🙏
The text was updated successfully, but these errors were encountered: