Anything the community can do to help maintain this library?

[tonglil]

This yaml library seems to be the definitely library depended on by many Go packages.

Is there something the community can do to help merge fixes to various identified and confirmed issues @niemeyer?

[kevinburke]

triaging bugs would probably help, indicating issues that should be closed would help, performing code reviews on open issues would probably help

[niemeyer]

Several weeks back I had a conversation with @rogpeppe and we agreed he'd allocate some of his time to keeping this library up-to-date and well taken care of. This seems to be taking slightly more time than expected to happen, though.

@rogpeppe Do you have any news there?

[nmiyake]

Happy to do a pass on some of these things -- we make extensive use of this library and find it very valuable and would love to see some more movement on some of the open issues/PRs.

What's the best way to flag issues that should be closed? Is there someone I can @ to flag to who can close out things that are stale/resolved?

[balanatarajan]

@niemeyer What is the expected commitment for maintaining this? I can see whether someone in my team would be willing to help as well

[lox]

I'm happy to assist to. We make heavy use of it too.

[niemeyer]

@lox Help is always appreciated, and that's true of anything I have some involved on.

The best way to help is to engage and perform tasks that other long term maintainers would otherwise have to sit down and dedicate spans of time to do. Once the PR is ready for merging, it's easy to click on the button.

For example, I see you have interest on #220. This PR has a large number of changes that are completely unrelated to fixing a bug. It doesn't even describe what the problem is, although I can see that there's clearly a problem and that other people agree, which means we want to merge something. So, valuable work includes:

• Reviewing code, looking for potential issues
• Separating related changes from unrelated changes
• Ensuring all the changes are well tested
• Ensuring we're following established conventions from Go
• Finding what the conventions are in the first place (no matter how experienced, following patterns involves looking for them too)
• Recommending actions (closing bugs)

Hope that helps a bit.

As a side note, I'm working on yaml.v3 right now. Some major improvements coming.

[lox]

I'll see what I can do!

[niemeyer]

Thanks @lox, and welcome.