Page History

...

• Have some questions?
  • Send emails to the dev list listed below
  • Ask question from the community on gitter
• 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

Submitting PRs

Note that more information as to how to setup your environment and run tests locally and on Travis-CI is available on the CONTRIBUTING.md on Github.

• 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 only preface the PR title with [AIRFLOW-XXX], but we also need the commit message subject to contain the JIRA id. This is because we use the subject line in the commit messages when creating the release notes. 
  • add an Apache License header to all new files
  • & follow the 7 rules of good Git commits
    
    

...