Community

Apache Airflow was started at Airbnb as open source from the very first commit. The community has about 500 active members who support each other in solving problems

Join the community!

Join the devlist

If you want to stay up to date with what is going on in the project, want to discuss the features, talk about fixes or simply ask a question - this is the first step to take.

The preferred channel for discussion is using the official Apache Airflow mailing lists. To subscribe, send an email to:
- Users list: users-subscribe@airflow.apache.org and users-unsubscribe@airflow.apache.org to unsubscribe
- Dev list: dev-subscribe@airflow.apache.org and dev-unsubscribe@airflow.apache.org to unsubscribe

For ad-hoc questions you can use the official Slack of Airflow. See "Ask a question" below.

Report a bug

Use our GitHub to create a ticket.

Remember to put there as much information as you can, including:

tracebacks,
screens,
scenarios to repeat problem.

Ask a question

In case of any questions or doubts, feel free to reach to our community. There are two ways to do that.

Join the Apache Airflow slack. After creating account in slack you can join #troubleshooting and #development where you can look for help in using and developing Airflow respectively.
Ask at the devlist, see "Join the devlist" link above
Check Stack Overflow
Remember that Airflow is a community driven project, so in case of constant technical support please consider hiring a consultancy company.

Add a new feature

There are two steps required to create feature request for Airflow.

Create account at GitHub [Sign up]
Create new issue and choose ‘Feature request’. Try to put in the description as much information as you can to clarify your idea.
We encourage you to open a PR with your implementation of the feature. It would be great if you would take a look at our contribution guidelines.

Fix a bug

We don’t like bugs. If you found one please tell us as soon as possible using steps below.

Create account at GitHub [Sign up]
Create new issue and choose ‘Bug report’. Try to put in the description as much information as you can including replication steps, tracebacks and screens.
We encourage you to open a PR with bug fix. It would be great if you would take a look at our contribution guidelines.

Improve documentation

Some people may want to improve documentation and this is mostly welcomed!

Open a PR with changes
If you are not sure about your changes feel free to post a question on #documentation channel on our Slack.

Propose fundamental changes

If you have an idea that will change Airflow fundamentally then there are more steps to take but still rather simple ones.

Create Airflow Improvement Proposal (AIP) on project wiki (Airflow Improvements Proposals), describe your idea, discuss the pros and cons and explain why Airflow needs such changes.
When your AIP is ready, send it to our dev mailing list where the whole community will be able to discuss it and elaborate the final version.
When community will approve your proposal then it’s a signal to start the work! Prepare your change as single or sequence of PRs and voile!