Looking for a co-maintainer

[frostming]

Human review has now become a bottleneck due to the rising number of AI-assisted PRs. Some of them may fix the issue and make the CI green, but may bring regressions that are hard to catch by testing coverage. Reviewing such PRs are always a pain given the complexity of this project's codebase.

I'm looking for co-maintainers to help share this workload. Responsibilities would include reviewing and merging pull requests, triaging issues, and helping decide the project's direction going forward.

Ideally, a co-maintainer would have:

• Prior experience contributing to tomlkit or a good understanding of the TOML spec
• Familiarity with Python packaging and testing tools
• (Human) Time to regularly review PRs and issues (not necessarily full-time, but consistently)

If you're interested in helping out, please comment below with a bit about your background and any relevant experience. Thanks for considering it!

[davidpavlovschi]

Hi @frostming — I'd like to volunteer. For judging fit: in #576, dimbleby's review moved me off a memoization band-aid onto the bisection approach, and before adopting the suggested bisect(..., key=...) one-liner I flagged that it would silently break Python 3.9, which tomlkit still supports and tests. That's the failure mode your first paragraph describes — changes that make CI green while breaking something coverage doesn't catch — and it's what I'd focus reviews on. I'd suggest starting small: I take triage and first-pass review, you keep merge rights, and you judge from the output whether to extend trust.

[frostming]

Thank you @davidpavlovschi invitation is sent.