potiuk commented on code in PR #36969: URL: https://github.com/apache/airflow/pull/36969#discussion_r1467133611
########## contributing-docs/02_how_to_communicate.rst: ########## @@ -0,0 +1,152 @@ + .. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + .. http://www.apache.org/licenses/LICENSE-2.0 + + .. Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +How to communicate +================== + +Apache Airflow is a Community within Apache Software Foundation. As the motto of +the Apache Software Foundation states "Community over Code" - people in the +community are far more important than their contribution. + +This means that communication plays a big role in it, and this chapter is all about it. + +In our communication, everyone is expected to follow the `ASF Code of Conduct <https://www.apache.org/foundation/policies/conduct>`_. + +.. contents:: :local: + +Various Communication channels +------------------------------ + +We have various channels of communication - starting from the official devlist, comments +in the PR, Slack, wiki. + +All those channels can be used for different purposes. +You can join the channels via links at the `Airflow Community page <https://airflow.apache.org/community/>`_ + +* The `Apache Airflow devlist <https://lists.apache.org/list.html?d...@airflow.apache.org>`_ for: + * official communication + * general issues, asking community for opinion + * discussing proposals + * voting +* The `Airflow CWiki <https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Home?src=breadcrumbs>`_ for: + * detailed discussions on big proposals (Airflow Improvement Proposals also name AIPs) + * helpful, shared resources (for example Apache Airflow logos + * information that can be reused by others (for example instructions on preparing workshops) +* GitHub `Pull Requests (PRs) <https://github.com/apache/airflow/pulls>`_ for: + * discussing implementation details of PRs + * not for architectural discussions (use the devlist for that) +* The deprecated `JIRA issues <https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-4470?filter=allopenissues>`_ for: + * checking out old but still valuable issues that are not on GitHub yet + * mentioning the JIRA issue number in the title of the related PR you would like to open on GitHub + +**IMPORTANT** +We don't create new issues on JIRA anymore. The reason we still look at JIRA issues is that there are valuable +tickets inside of it. However, each new PR should be created on `GitHub issues <https://github.com/apache/airflow/issues>`_ +as stated in `Contribution Workflow Example <contribution-workflow.rst>`_ + +Slack details +------------- + +* The `Apache Airflow Slack <https://s.apache.org/airflow-slack>`_ for: + * ad-hoc questions related to development and asking for review (#development channel) + * asking for help with first contribution PRs (#development-first-pr-support channel) + * troubleshooting (#troubleshooting channel) + * using Breeze (#airflow-breeze channel) + * improving and maintaining documentation (#documentation channel) + * group talks (including SIG - special interest groups) (#sig-* channels) + * notifications (#announcements channel) + * random queries (#random channel) + * regional announcements (#users-* channels) + * occasional discussions (wherever appropriate including group and 1-1 discussions) + +Please exercise caution against posting same questions across multiple channels. Doing so not only prevents +redundancy but also promotes more efficient and effective communication for everyone involved. + +Devlist details +--------------- + +The devlist is the most important and official communication channel. Often at Apache project you can +hear "if it is not in the devlist - it did not happen". If you discuss and agree with someone from the +community on something important for the community (including if it is with maintainer or PMC member) the +discussion must be captured and reshared on devlist in order to give other members of the community to +participate in it. + +We are using certain prefixes for email subjects for different purposes. Start your email with one of those: + * ``[DISCUSS]`` - if you want to discuss something but you have no concrete proposal yet + * ``[PROPOSAL]`` - if usually after "[DISCUSS]" thread discussion you want to propose something and see + what other members of the community think about it. + * ``[AIP-NN]`` - if the mail is about one of the Airflow Improvement Proposals + * ``[VOTE]`` - if you would like to start voting on a proposal discussed before in a "[PROPOSAL]" thread Review Comment: Added. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
