Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Looking for a co-maintainer

Open
#574 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
python

Research direction

This issue seeks a co-maintainer rather than a code change. Review the stated responsibilities—PR review and merging, issue triage, and project-direction decisions—along with the requested TOML spec, Python packaging, and testing experience. Done means establishing an ongoing maintainer arrangement, not completing a bounded patch.

Written by the indexing model from the issue text.

Description

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!

Dominant language
Python
Stars
850
Forks
163
Avg merge
13m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python-poetry/tomlkit

All issues in python-poetry/tomlkit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.