Is this (v3) repo still maintained?

[mikefarah]

Are you looking for new contributors? Has someone made a more active fork?

[niemeyer]

Yeah, I still look after it. I just haven't had as much time for it in the last year.

[mikefarah]

Yeah fair enough, thanks for all your work too! I must admit that I worry a little that it all comes down to a single person.

…

________________________________ From: Gustavo Niemeyer ***@***.***> Sent: Monday, October 4, 2021 9:03:30 PM To: go-yaml/yaml ***@***.***> Cc: Mike Farah ***@***.***>; Author ***@***.***> Subject: Re: [go-yaml/yaml] Is this (v3) repo still maintained? (#788) Yeah, I still look after it. I just haven't had as much time for it in the last year. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#788 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAIZHNIJ5SHWOLHW6WHUJ4LUFF3XFANCNFSM5FI3J7FQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[niemeyer]

Yeah, I understand the concern. I'm sure someone will pick it up if I drop it completely, but that's not the case right now.

In truth, that's one of the things I have never managed to fix in my open source projects, and I perceive that as a common issue elsewhere too. The high profile projects I'm responsible for end up with investment and proper quality teams, and take a lot of attention. My niche projects end up with just me, and in the few cases I tried to open up to co-maintainers, I ended up paying the price a few years later, either by having to spend significant time to bring the project back on track, or with it just dead.

So the only functional way I found of keeping projects like this in a healthy state that everyone can rely on is by doing work in bursts. A few days to a couple of weeks at a time, usually.

Even then, I realize it can be frustrating to be on the other side waiting for the action. But that's what I can manage, at least right now, to keep this 10+ years foundational project going.

[TristanSpeakEasy]

Is it worth reopening this ticket and looking for new maintainers? The issues and PRs are piling up and this is a critical package in a lot of downstream software

[andig]

@niemeyer would you consider onboarding more maintainers? It has been another two years since the last update and there are a couple of worthy PRs waiting for review.

[niemeyer]

There are 128 PRs, most of them worth of consideration, but many of them likely not proper, at least yet. What we need is a proper team to maintain this project as part of their job, with good oversight (we don't want another xz), and that's what I've been working on, attempting to organize a team at Canonical for this. That, or I move out from my current job and get more time again. Well, or the upstream Go team takes it over. I don't have the means to onboard one-off maintainers right now.