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 (archive):
  - users-subscribe@airflow.apache.org
  - users-unsubscribe@airflow.apache.org to unsubscribe
- Dev list (archive):
  - dev-subscribe@airflow.apache.org
  - dev-unsubscribe@airflow.apache.org to unsubscribe

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

Subscribe to the newsletter

Get regular monthly updates on recent events and communications in the Airflow community.

You will learn about:

recent releases,
upcoming and recent events,
the PR of the Month,
recent blog posts and guides,
activity on the dev list.

Start a discussion

Use our GitHub Discussions to start a discussion.

You can start discussions about:

proposing a new feature,
whether what you are observing is a real issue,
your brainstorms,
how others solve their problems.

Report a bug

Use our GitHub Issue to create an issue.

Remember to include as much information as you can, including:

tracebacks,
screens,
scenarios to repeat the problem (mandatory).

If you are unsure if this is a problem with Airflow, start a GitHub Discussion first.

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 a feature request for Airflow.

Create an account at GitHub [Sign up]
Create a 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 find one, please tell us as soon as possible using the steps below.

Create an account at GitHub [Sign up].
Create a 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 your bug fix. It would be great if you would take a look at our contribution guidelines.

Improve documentation

Some people might want to improve documentation and this is most welcome!

Open a PR with changes.
If you are not sure about your changes, feel free to post a question in the #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 they are still rather simple ones.

Create an Airflow Improvement Proposal (AIP) on the 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 the community approves your proposal, this is a signal to start the work! Prepare your change as a single or sequence of PRs and voila!