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 contributor 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 Jiras

Overview

In order to contribute to Airflow, please be sure to:

• Register on the following Apache mailing lists
  • dev@airflow.incubator.apache.org
    
    • Start by sending an email to dev-subscribe@airflow.incubator.apache.org- this will initiate an automated subscription process
    • The dev lists is where we, as a community, share information, pose and answer questions, and vote on policy changes
  • commits@airflow.incubator.apache.org
    
    • Start by sending an email to commits-subscribe@airflow.incubator.apache.org- this will initiate an automated subscription process
    • The commits list is updated by comments on Jiras and PRs and is the way you can keep abreast of discussions around Jiras.
• Sign up for both https://issues.apache.org/jira/browse/AIRFLOW and https://cwiki.apache.org/confluence/display/AIRFLOW accounts
• Visit and read docs on https://github.com/apache/incubator-airflow & Airflow Home
• When filing PRs, remember to 
  • rebase your fork : http://stackoverflow.com/a/7244456/1110993
  • squash your commits
  • preface your PR's title with [AIRFLOW-XXX], where XXX is the JIRA number, and add a JIRA link in the PR description
  • add an Apache License header to all new files
  • & follow the 7 rules of good Git commits