How to find long-term maintainers for your open source project如何为你的开源项目找到长期维护者

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.开源项目的生死，取决于它们能否吸引愿意留下来的人。一个提交一个拉取请求就消失的贡献者，和一个成为长期维护者的贡献者，其差别通常体现在模式里：提交的频率、触及的文件广度、在自己的议题之外的参与，以及对审查反馈的响应速度。这些模式存在于每一份公开的 Git 历史里——难的是在不花上几小时阅读提交日志的前提下，大规模地把它们找出来。

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.先从定义「长期」对你的项目意味着什么开始。对一个小型库来说，它可能是一个跟上生态、每隔几个月就提交兼容性 PR 的人。对一个大型框架来说，它可能是一个负责某个子系统的人。一旦你知道自己需要什么，就去寻找持续的信号：一个触及过代码库不止一个区域的贡献者，一个参与过讨论（而不只是扔下一堆代码）的人，以及一个提交频率呈现出节奏而不是一次尖峰的人。当初次的兴奋消退时，这些人最有可能继续出现。

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. polyagent Builders (polyagent.club/builders) ranks people who opted in by their public GitHub evidence and names the repositories behind every result so you can evaluate before you invest time in outreach.核实这一步很重要，因为任何人都可以在个人资料上声称自己是维护者。公开的 Git 历史——提交次数、日期、文件多样性、审查评论——要难伪造得多。polyagent Builders（polyagent.club/builders）按公开的 GitHub 证据对主动加入的人进行排名，并列出每条结果背后的仓库，这样你就能在投入时间去联系之前先做出评估。

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.一旦你有了候选人，联系本身就应该具体：引用他们实际做过的贡献，说明为什么他们的特定技能符合你的项目所需，并清楚地说明你所要求的投入程度。含糊的「我们需要维护者」消息会被无视。一条说「你对认证模块的三个 PR 显示出对边界情况的细心关注，而这个子系统正需要这样的负责态度」的消息，得到回复的可能性要大得多。