-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Module abandoned? #1034
Comments
any news? |
I've tried reaching out to @niemeyer on email but no luck. |
It's not abandoned, but maintenance is unfortunately behind while my daily attention is elsewhere, as has been stated a few times here. My goal is to move the project under a team at Canonical, but it's not there yet. |
Thank you for the response @niemeyer, much appreciated. I was not aware this has been stated already. Maybe leave the issue open for better discoverability? I realise how much effort it is to maintain such a widely-used project. This module is imho one of the basic building blocks of many Go applications and has little existing alternatives. It would be great- while the transition is ongoing- to get bugs and maybe obvious, self-contained features (like #901?) addressed. |
This module has a number of good quality PR that slowly get bit-rodden. The last update (the unfortunate 1 billion dollar mistake) is two years old. It is not clear, if this module is still being maintained (seems it isn't).
It would be great to get an update on the state of this module and worst case lay grounds for a coordinated fork.
/cc @niemeyer
Update note there is https://github.com/goccy/go-yaml as maintained and 1k-starred alternative.
The text was updated successfully, but these errors were encountered: