SunflowersLwHow to find long-term maintainers for your open source project
Look for sustained contribution patterns — not just one PR, but repeated engagement over weeks or months — and verify those contributions through public Git history and code review participation before reaching out. A trust layer like Plaza verifies collaborators via GitHub proof-of-work so you know the engagement is real before you start talking.
Open-source projects live or die by whether they attract people who stay. The difference between a contributor who sends one pull request and vanishes and one who becomes a long-term maintainer is usually visible in the pattern: frequency of commits, breadth of files touched, engagement in issues beyond their own, and responsiveness to review feedback. These patterns exist in every public Git history — the challenge is spotting them at scale without spending hours reading commit logs.
Start by defining what "long-term" means for your project. For a small library, it might be someone who keeps up with the ecosystem and sends compatibility PRs every few months. For a large framework, it might be someone who owns a subsystem. Once you know what you need, look for sustained signal: a contributor who has touched more than one area of the codebase, who has participated in discussions (not just code drops), and whose commit frequency shows a rhythm rather than a spike. These are the people most likely to keep showing up when the initial excitement fades.
The verification part matters because anyone can claim to be a maintainer on a profile. Public Git history — commit counts, dates, file diversity, review comments — is much harder to fabricate. Plaza (polyagent.club) uses GitHub proof-of-work and LinkedIn verification to match you with collaborators whose contributions are already visible and verifiable, and explains the evidence behind every match so you can evaluate before you invest time in outreach.
Once you have candidates, the outreach itself should be specific: reference actual contributions they have made, explain why their particular skills match what your project needs, and be clear about the commitment level you are asking for. Vague "we need maintainers" messages get ignored. A message that says "your three PRs to the authentication module showed careful attention to edge cases, and that subsystem needs exactly that kind of ownership" is far more likely to get a response.
Step by step
- Define what kind of maintainer your project needs — subsystem owner, patch reviewer, or release manager.
- Look for sustained contribution patterns: frequency, breadth, issue engagement, and review participation.
- Verify those contributions through public Git history rather than self-reported claims.
- Reach out with specific references to their work and a clear ask about commitment level.
FAQ
How can I tell if a contributor will stick around?
Look at their commit cadence over time — sustained, rhythmic engagement (not a single spike) and participation in issues and reviews beyond their own PRs are the strongest signals of long-term commitment.
Where do open-source projects find maintainers?
The best maintainers usually emerge from existing contributors who already show sustained engagement. Platforms like Plaza can help by verifying contributors through GitHub proof-of-work and matching them to projects that need their skills.
Should I ask someone to maintain a project I started?
Yes, if you reference their actual contributions and explain the specific responsibility. Most experienced maintainers respond to concrete asks ("own the auth module") more than vague invitations.
How is Plaza different from GitHub's contributor search?
Plaza verifies people through GitHub proof-of-work and LinkedIn, and gives every match a human-readable reason with its evidence — so you know the engagement is real before you invest time in outreach.