Before reading this document, you should be familiar with Contributors' guide. This document assumes that you are a bit familiar how Airflow's community work, but you would like to learn more about the rules by which we add new members.
Often you can hear two different terms about people who have write access to the Airflow repository - "committers" and "maintainers". This is because those two terms are used in different contexts.
For all practical purposes, both terms are interchangeable because the Apache Software Foundation rule is the only Committers can have write access to the repositories managed by the PMC (Project Management Committee) and that all Committers get write access to the repository.
You will see both terms used in different documentation, therefore our goal is not to use one of the terms only - it is unavoidable to see both terms anyway. As a rule, we are using "committer" term in the context of the official rules concerning Apache Software Foundation and "maintainer" term in the context where technical GitHub access and permissions to the project are important.
Committers are community members who have write access to the project's repositories, i.e., they can modify the code, documentation, and website by themselves and also accept other contributions. There is no strict protocol for becoming a committer. Candidates for new committers are typically people that are active contributors and community members.
Some people might be active in several of those areas and while they might have not enough 'achievements' in any single one of those, their combined contributions in several areas all count.
As a community, we appreciate contributions to the Airflow codebase, but we also place equal value on those who help Airflow by improving the community in some way. It is entirely possible to become a committer (and eventually a PMC member) without ever having to change a single line of code.
General prerequisites that we look for in all candidates:
Committers are more than contributors. While it's important for committers to maintain standing by committing code, their key role is to build and foster a healthy and active community. This means that committers should:
To become a PMC member the committers should meet all general prerequisites. Apart from that the person should demonstrate distinct community involvement or code contributions.
Guidelines from ASF are listed at ASF: New Candidates for Committership.
Only a current PMC member can nominate a current committer to be part of PMC.
If the vote fails or PMC members needs more evidence, then one of the PMC Member (who is not the Proposer) can become the Mentor and guide the proposed candidates on how they can become a PMC member.
Candidate Proposer
This is the person who launches the DISCUSS thread & makes the case for a PMC promotion
Candidate Mentor
If the committee does not have enough information, requires more time, or requires more evidence of candidate's eligibility, a mentor, who is not the proposer, is selected to help mentor the candidate The mentor should try to remain impartial -- their goal is to provide the missing evidence and to try to coach/mentor the candidate to success.
In order to re-raise a candidate vote, both Proposer and Mentor must be in favor. Again, the mentor must try to remain impartial and cannot be the Proposer.
If you know you are not going to be able to contribute for a long time (for instance, due to a change of job or circumstances), you should inform the PMC and we will mark you as "inactive". Inactive committers will be removed from the "roster" on ASF and will no longer have the power of being a Committer (especially write access to the repos). As merit earned never expires, once you become active again you can simply email the PMC and ask to be reinstated.
The PMC also can mark committers as inactive after they have not been involved in the community for more than 12 months.
To be able to merge PRs, committers have to integrate their GitHub ID with Apache systems. To do that follow steps:
#internal-airflow-ci-cd
channel to be configured in self-hosted runners
by the CI team. Wait for confirmation that this is done and some helpful tips from the CI teamdev/breeze/src/airflow_breeze/global_constants.py
(COMMITTERS variable).asf.yaml
.此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。