The success of open source software (OSS) projects relies on voluntary contributions from various community roles.Being a committer signifies gaining trust and higher privileges. Substantial studies have focused on the requirements of becoming a committer, but most of them are based on interviews or several hypotheses, lacking a comprehensive understanding of committers' qualifications.We explore both the policies and practical implementations of committer qualifications in modern top OSS communities. Through a thematic analysis of these policies, we construct a taxonomy of committer qualifications, consisting of 26 codes categorized into nine themes, including Personnel-related to Project, Communication, and Long-term Participation. We also highlight the variations in committer qualifications emphasized in different OSS community governance models. For example, projects following the core maintainer model value project comprehension, while projects following the company-backed model place significant emphasis on user issue resolution. Then, we propose eight sets of metrics and perform survival analysis on two representative OSS projects to understand how these qualifications are implemented in practice. We find that the probability of gaining commit rights decreases as participation time passes.The selection criteria in practice are generally consistent with the community policies. Developers who submit high-quality code, actively engage in code review, and make extensive contributions to related projects are more likely to be granted commit rights. However, there are some qualifications that do not align precisely, and some are not adequately evaluated. This study contributes to the understanding of trust establishment in modern top OSS communities, assists communities in better allocating commit rights, and supports developers in achieving self-actualization through OSS participation.

翻译：开源软件（OSS）项目的成功依赖于来自社区不同角色成员的自愿贡献。成为提交者意味着获得信任和更高的权限。已有大量研究关注成为提交者的条件，但大多数基于访谈或若干假设，缺乏对提交者资质的全面理解。我们探讨了现代顶级开源社区中提交者资质的政策及其实际实施情况。通过对这些政策的主题分析，我们构建了一个提交者资质分类体系，包含26个编码，归纳为九个主题，包括与项目相关的人员、沟通和长期参与等。我们还强调了不同开源社区治理模型下提交者资质的差异。例如，遵循核心维护者模型的项目更重视项目理解，而遵循公司支持模型的项目则着重强调用户问题的解决。随后，我们提出了八组度量指标，并对两个代表性开源项目进行了生存分析，以了解这些资质在实际中的实施情况。我们发现，随着参与时间的推移，获得提交权限的概率逐渐降低。实际中的选拔标准与社区政策总体一致。提交高质量代码、积极参与代码审查、并对相关项目做出广泛贡献的开发者更有可能获得提交权限。然而，部分资质与实际存在偏差，某些资质也未得到充分评估。本研究有助于理解现代顶级开源社区中信任的建立机制，协助社区更合理地分配提交权限，并支持开发者通过参与开源社区实现自我价值。