Overview
We would like to more people to use, contribute to, and maintain Airflow. These three aims align with the 3 main roles of members within our community : users, contributors, and committers/maintainers. We would like to instill a sense of ownership and pride among the members of our community by encouraging:
- people to use Airflow
- users to to Airflow
- contributors to become committers
You can contribute to Airflow in many ways such as:
- reporting bugs
- suggesting features and Road Map items
- submitting pull-requests for both bug fixes and new features
- attending Airflow meet-ups
- helping in answering questions on gitter, the dev email list, PRs, and s
Does Your Company Use Airflow?
If so, then add your company (
along with your GitHub handle) as links to the
README.md and submit a Pull Request (
with associated JIRA). We'll happily merge it.
![Airflow > Contributors' Guide [ARCHIVED] > Screenshot 2016-08-10 22.41.01.png](/confluence/download/attachments/62697734/Screenshot%202016-08-10%2022.41.01.png?version=1&modificationDate=1470894919000&api=v2)
Details on Contributing
Getting Started
In order to contribute to Airflow, please be sure to:
Submitting PRs
- When filing PRs, remember to
- rebase your fork : http://stackoverflow.com/a/7244456/1110993
- squash your commits
- Create a JIRA for your bug fix/feature enhancement - point the JIRA "External Issue URL" to your PR URL
- Preface your commit's subject & PR's title with [AIRFLOW-XXX], where XXX is the JIRA number, and add a JIRA link in the PR description
- Some folks just preface the PR title with [AIRFLOW-XXX], but we need the commit message subject to contain the JIRA id
- add an Apache License header to all new files
- & follow the 7 rules of good Git commits