This document assumes that you know how Airflow's community work, but you would like to learn more about the rules by which we add new members.
Before reading this document, you should be familiar with Contributor's guide.
There is no strict protocol for becoming a committer. Candidates for new committers are typically people that are active contributors and community members.
The key aspects of a committer are:
- Consistent contributions over the past 6 months
- Understanding of Airflow Core or has displayed a holistic understanding of a particular part and made contributions towards a more strategic goal
- Understanding of contributor/committer guidelines: Contributors' Guide
- Quality of the commits
- Visibility in community discussions (dev mailing list, Slack and GitHub)
- Testing Release Candidates
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.
- Has been a committer for at least 3 months
- Is still active community member (Visible on mailing list or reviewing PRs at the minimum)
- Visibility on discussions on the dev mailing list
- Spreading the word for "Airflow" either:
- Talks at meetups, conferences, etc
- Creating content like videos, blogs, etc
- Growing the community:
- Mentors new members/contributors
- Answers users/contributors via Github issues, dev list or slack
- Consistent voting on RCs for at least past 3 releases lifecycles
- Engagement in Airflow Improvements Proposals either:
- Has been actively voting on AIPs
- Has been proposing and leading their implementation
- Actively involved in code contributions:
- Code reviews
- Merging pull requests
- Fixing bugs and implementing improvements
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 -- his/her 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.
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:
- Consistent contribution over last few months
- Visibility on discussions on the dev mailing list, Slack channels or Github issues/discussions
- Contributions to community health and project's sustainability for the long-term
- Understands contributor/committer guidelines: Contributors' Guide
- Makes high-quality commits (especially commit messages), and assess the impact of the changes, including upgrade paths or deprecation policies
- Testing Release Candidates to help the release cycle
- Proposed and led to completion Airflow Improvement Proposal(s)
- Demonstrates an understanding of one of the following areas or has displayed a holistic understanding
of a particular part and made contributions towards a more strategic goal
- Airflow Core
- API
- Docker Image
- Helm Chart
- Dev Tools (Breeze / CI)
- Certain Providers
- Has made a significant improvement or added an integration with services/technologies important to the Airflow Ecosystem
- Was instrumental in triaging issues
- Improved documentation of Airflow in significant way
- Lead change and improvements introduction in the “community” processes and tools
- Actively spreads the word about Airflow, for example organising Airflow summit, workshops for community members, giving and recording talks, writing blogs
- Reporting bugs with detailed reproduction steps
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:
- Review PRs in a timely and reliable fashion
- They should also help to actively whittle down the PR backlog
- Answer questions (i.e. on the dev list, in PRs, in GitHub Issues, slack, etc...)
- Take on core changes/bugs/feature requests
- Some changes are important enough that a committer needs to ensure it gets done. This is especially the case if no one from the community is taking it on.
- Improve processes and tooling
- Refactoring code