If you’re a heavy Airflow user and have code that you use in your own environment, an excellent way to get involved with the wider community is to contribute back to the Apache Airflow project itself. It’s an effective way to push forward a tool you depend on and to support everyone else using it alongside you in the open-source community.
If you’re interested and have some code handy, here are some initial steps you can take:
1. Read the Contributing Guide for Airflow
It’s not as scary as it looks.
2. Fork Airflow
- Fork Airflow, pull your forked version down so you can edit the code
- Have a look at the “Local virtualenv development environment” section for testing best practices
pip install -e ".[devel]"
This line will install Airflow into the virtual env you create, as you’ll need to be in the top level of the airflow repo you forked when you run it.
4. Hack Away.
Once you have a forked version of Apache Airflow installed locally, you’re free to start hacking at it.
5. Submit a PR.
Once you’re ready to submit a PR, check out the Pull Request Guidelines.
- Airflow Slack Channel (check out the #development channel for help)
- JIRA: List of all Open Issues to Apache Airflow, in case your code addresses any of them
- Reach out to us at firstname.lastname@example.org or DM us directly in the Airflow Slack Channel. We have a handful of Apache Airflow committers on our team and would love to help out.