blob: 972c9baa90375ac4ac057db5ae9bda5144e047cf [file] [log] [blame]
---
title: Community
menu:
main:
weight: 1
---
<div class="community--accordion-container">
{{< accordion title="Join the devlist" description="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." logo_path="icons/join-devlist-icon.svg" open="true" >}}
<ol class="counter-blue mx-auto">
<li>
<p class="bodytext__medium--brownish-grey">
The preferred channel for discussion is using the official Apache Airflow mailing lists.
To subscribe, send an email to:
</p>
<ul class="ticks-blue mx-auto">
<li>
Users list: <a class="list-link" href="mailto:users-subscribe@airflow.apache.org">users-subscribe@airflow.apache.org</a> <small>and <a class="list-link" href="mailto:users-unsubscribe@airflow.apache.org">users-unsubscribe@airflow.apache.org</a> to unsubscribe</small>
</li>
<li>
Dev list: <a class="list-link" href="mailto:dev-subscribe@airflow.apache.org">dev-subscribe@airflow.apache.org</a> <small>and <a class="list-link" href="mailto:dev-unsubscribe@airflow.apache.org">dev-unsubscribe@airflow.apache.org</a> to unsubscribe</small>
</li>
</ul>
</li>
<p class="bodytext__medium--brownish-grey">
For ad-hoc questions you can use the official Slack of Airflow. See <b>"Ask a question"</b> below.
</p>
</ol>
{{< /accordion >}}
{{< accordion title="Start a discussion" description="Use our [GitHub Discussions](https://github.com/apache/airflow/discussions) to start a discussion." logo_path="icons/ask-question-icon.svg" >}}
<p class="bodytext__medium--brownish-grey">You can start discussions about anything:</p>
<ul class="ticks-blue mx-auto">
<li>propose a new feature,</li>
<li>discuss if what you observe is a real issue,</li>
<li>generally brainstorm about your ideas,</li>
<li>ask others how they solve their problems,</li>
</ul>
{{< /accordion >}}
{{< accordion title="Report a bug" description="Use our [GitHub Issue](https://github.com/apache/airflow/issues) to create an issue." logo_path="icons/bug-icon.svg" >}}
<p class="bodytext__medium--brownish-grey">Remember to put there as much information as you can, including:</p>
<ul class="ticks-blue mx-auto">
<li>tracebacks,</li>
<li>screens,</li>
<li>scenarios to repeat problem (mandatory),</li>
<li>if you are unsure if this is a problem with Airflow - start a [GitHub Discussion](https://github.com/apache/airflow/discussions) first</li>
</ul>
{{< /accordion >}}
{{< accordion title="Ask a question" description="In case of any questions or doubts, feel free to reach to our community. There are two ways to do that." logo_path="icons/ask-question-icon.svg" >}}
<ol class="counter-blue mx-auto">
<li>
<a href="https://apache-airflow-slack.herokuapp.com/">Join the Apache Airflow slack</a>.
After creating account in slack you can join
<a href="https://apache-airflow.slack.com/messages/troubleshooting">#troubleshooting</a> and
<a href="https://apache-airflow.slack.com/messages/development">#development</a>
where you can look for help in using and developing Airflow respectively.
</li>
<li>Ask at the devlist, see <b>"Join the devlist"</b> link above</li>
<li>Check <a href="https://stackoverflow.com/questions/tagged/airflow">Stack Overflow</a></li>
<li>
Remember that Airflow is a community driven project, so in case of
constant technical support please consider hiring a consultancy company.
</li>
</ol>
{{< /accordion >}}
{{< accordion title="Add a new feature" description="There are two steps required to create feature request for Airflow." logo_path="icons/new-feature-icon.svg" >}}
<ol class="counter-blue mx-auto">
<li>Create account at GitHub <a href="https://github.com">[Sign up]</a></li>
<li>
Create <a href="https://github.com/apache/airflow/issues/new/choose">new issue</a> and choose ‘Feature request’. Try to put in the description as much information as you can to clarify your idea.
</li>
<li>
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
<a href="https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst">contribution guidelines</a>.
</li>
</ol>
{{< /accordion >}}
{{< accordion title="Fix a bug" description="We don’t like bugs. If you found one please tell us as soon as possible using steps below." logo_path="icons/fix-bug-icon.svg" >}}
<ol class="counter-blue mx-auto">
<li>Create account at GitHub <a href="https://github.com">[Sign up]</a></li>
<li>
Create <a href="https://github.com/apache/airflow/issues/new/choose">new issue</a> and choose ‘Bug report’. Try to put in the description as much information as you can including replication steps, tracebacks and screens.
</li>
<li>
We encourage you to open a PR with bug fix. It would be great if you would take a look at our
<a href="https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst">contribution guidelines</a>.
</li>
</ol>
{{< /accordion >}}
{{< accordion title="Improve documentation" description="Some people may want to improve documentation and this is mostly welcomed!" logo_path="icons/documentation-icon.svg" >}}
<ol class="counter-blue mx-auto">
<li>Open a PR with changes</li>
<li>
If you are not sure about your changes feel free to post a question on #documentation channel on our <a
href="https://apache-airflow.slack.com">Slack</a>.
</li>
</ol>
{{< /accordion >}}
{{< accordion title="Propose fundamental changes" description="If you have an idea that will change Airflow fundamentally then there are more steps to take but still rather simple ones." logo_path="icons/project-icon.svg" >}}
<ol class="counter-blue mx-auto">
<li>
Create Airflow Improvement Proposal (AIP) on project wiki
(<a href="https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals">Airflow
Improvements Proposals</a>),
describe your idea, discuss the pros and cons and explain why Airflow needs such changes.
</li>
<li>
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.
</li>
<li>
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!
</li>
</ol>
{{< /accordion >}}
</div>