This is an automated email from the ASF dual-hosted git repository. potiuk pushed a commit to branch v2-8-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 6fc75fb2437b06686ec440dc9ee6a6e9ae19cda6 Author: Jarek Potiuk <[email protected]> AuthorDate: Fri Feb 16 22:55:40 2024 +0100 Update slack channel names following new naming schemes (#37495) Following LAZY CONSENSUS on devlist: https://lists.apache.org/thread/v9s6pc46o96y7xpd519mflnlx7r8sslo we rename the channels in our docs. (cherry picked from commit 45cf40f67304d49f4cd43a5e7ad8628ae4c170ba) --- .github/ISSUE_TEMPLATE/airflow_bug_report.yml | 2 +- .github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml | 2 +- .../ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml | 2 +- .../ISSUE_TEMPLATE/airflow_providers_bug_report.yml | 2 +- .github/ISSUE_TEMPLATE/feature_request.yml | 2 +- contributing-docs/02_how_to_communicate.rst | 8 ++++---- contributing-docs/16_contribution_workflow.rst | 2 +- contributing-docs/README.rst | 4 ++-- dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md | 2 +- docs/apache-airflow/installation/index.rst | 21 +++++++++++++++------ 10 files changed, 28 insertions(+), 19 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/airflow_bug_report.yml b/.github/ISSUE_TEMPLATE/airflow_bug_report.yml index cb437184fa..1a31ebb246 100644 --- a/.github/ISSUE_TEMPLATE/airflow_bug_report.yml +++ b/.github/ISSUE_TEMPLATE/airflow_bug_report.yml @@ -124,7 +124,7 @@ body: This is absolutely not required, but we are happy to guide you in the contribution process especially if you already have a good understanding of how to implement the fix. Airflow is a community-managed project and we love to bring new contributors in. - Find us in #development-first-pr-support on Slack! + Find us in #new-contributors on Slack! options: - label: Yes I am willing to submit a PR! - type: checkboxes diff --git a/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml b/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml index 2a3d51bf22..6bfc7f3366 100644 --- a/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml +++ b/.github/ISSUE_TEMPLATE/airflow_doc_issue_report.yml @@ -50,7 +50,7 @@ body: This is absolutely not required, but we are happy to guide you in the contribution process especially if you already have a good understanding of how to implement the fix. Airflow is a community-managed project and we love to bring new contributors in. - Find us in #development-first-pr-support on Slack! + Find us in #new-contributors on Slack! options: - label: Yes I am willing to submit a PR! - type: checkboxes diff --git a/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml b/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml index 140279906d..4639a12251 100644 --- a/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml +++ b/.github/ISSUE_TEMPLATE/airflow_helmchart_bug_report.yml @@ -117,7 +117,7 @@ body: This is absolutely not required, but we are happy to guide you in the contribution process especially if you already have a good understanding of how to implement the fix. Airflow is a community-managed project and we love to bring new contributors in. - Find us in #development-first-pr-support on Slack! + Find us in #new-contributors on Slack! options: - label: Yes I am willing to submit a PR! - type: checkboxes diff --git a/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml b/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml index 24a4edaad0..475ca5d027 100644 --- a/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml +++ b/.github/ISSUE_TEMPLATE/airflow_providers_bug_report.yml @@ -205,7 +205,7 @@ body: This is absolutely not required, but we are happy to guide you in the contribution process especially if you already have a good understanding of how to implement the fix. Airflow is a community-managed project and we love to bring new contributors in. - Find us in #development-first-pr-support on Slack! + Find us in #new-contributors on Slack! options: - label: Yes I am willing to submit a PR! - type: checkboxes diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml index aa8dc8e965..c771b2a236 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -52,7 +52,7 @@ body: If want to submit a PR you do not need to open feature request, <b>just create the PR!</b>. Especially if you already have a good understanding of how to implement the feature. Airflow is a community-managed project and we love to bring new contributors in. - Find us in #development-first-pr-support on Slack! + Find us in #new-contributors on Slack! It's optional though - if you have good idea for small feature, others might implement it if they pick an interest in it, so feel free to leave that checkbox unchecked. diff --git a/contributing-docs/02_how_to_communicate.rst b/contributing-docs/02_how_to_communicate.rst index e264014d67..e14fcae92e 100644 --- a/contributing-docs/02_how_to_communicate.rst +++ b/contributing-docs/02_how_to_communicate.rst @@ -60,9 +60,9 @@ 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) + * ad-hoc questions related to development and asking for review (#contributors channel) + * asking for help with first contribution PRs (#new-contributors channel) + * troubleshooting (#user-troubleshooting channel) * using Breeze (#airflow-breeze channel) * improving and maintaining documentation (#documentation channel) * group talks (including SIG - special interest groups) (#sig-* channels) @@ -132,7 +132,7 @@ Here are a few rules that are important to keep in mind when you enter our commu * Do not be afraid to ask questions * The communication is asynchronous - do not expect immediate answers, ping others on slack - (#development channel) if blocked + (#contributors channel) if blocked * There is a #newbie-questions channel in slack as a safe place to ask questions * You can ask one of the maintainers to be a mentor for you, maintainers can guide you within the community * You can apply to more structured `Apache Mentoring Programme <https://community.apache.org/mentoringprogramme.html>`_ diff --git a/contributing-docs/16_contribution_workflow.rst b/contributing-docs/16_contribution_workflow.rst index 0ee07c9558..713232ac5a 100644 --- a/contributing-docs/16_contribution_workflow.rst +++ b/contributing-docs/16_contribution_workflow.rst @@ -48,7 +48,7 @@ In general, your contribution includes the following stages: 4. Make the change and create a `Pull Request (PR) from your fork <https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork>`__. -5. Ping @ #development slack, comment @people. Be annoying. Be considerate. +5. Ping @ #contributors slack, comment @people. Be annoying. Be considerate. Step 1: Fork the Apache Airflow Repo ------------------------------------ diff --git a/contributing-docs/README.rst b/contributing-docs/README.rst index d2fc5c7c7e..aacc529ec4 100644 --- a/contributing-docs/README.rst +++ b/contributing-docs/README.rst @@ -39,10 +39,10 @@ of the community works and you might need to get some mentorship from other memb community - mostly Airflow committers (maintainers). Mentoring new members of the community is part of maintainers job so do not be afraid of asking them to help you. You can do it via comments in your PR, asking on a devlist or via Slack. For your convenience, -we have a dedicated ``#development-first-pr-support`` Slack channel where you can ask any questions +we have a dedicated ``#new-contributors`` Slack channel where you can ask any questions about making your first Pull Request (PR) contribution to the Airflow codebase - it's a safe space where it is expected that people asking questions do not know a lot Airflow (yet!). -If you need help with Airflow see the Slack channel #troubleshooting. +If you need help with Airflow see the Slack channel #user-troubleshooting. To check on how mentoring works for the projects under Apache Software Foundation's `Apache Community Development - Mentoring <https://community.apache.org/mentoring/>`_. diff --git a/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md b/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md index fe5579ed1a..aa1c621864 100644 --- a/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md +++ b/dev/WHAT_GOES_INTO_THE_NEXT_RELEASE.md @@ -57,7 +57,7 @@ and mark the issues they think are bug fixes, to go into the next release This is the only thing that the maintainer has to do to get the PR proposed to be considered in the next patch release. Sometimes - if controversial - maintainers discuss the proposals in -the #release-management channel in Slack, sometimes in #development or in the PR itself - +the #release-management channel in Slack, sometimes in #contributors or in the PR itself - especially if the release manager decides to not include it and changes the milestone (and explains why). # What's the release manager's role ? diff --git a/docs/apache-airflow/installation/index.rst b/docs/apache-airflow/installation/index.rst index 67820123b8..9f9f76cd27 100644 --- a/docs/apache-airflow/installation/index.rst +++ b/docs/apache-airflow/installation/index.rst @@ -89,13 +89,16 @@ More details: :doc:`installing-from-sources` **Where to ask for help** -* The ``#development`` slack channel for building the software. - -* The ``#troubleshooting`` slack is a channel for quick general troubleshooting questions. The +* The ``#user-troubleshooting`` channel on slack can be used for quick general troubleshooting questions. The `GitHub discussions <https://github.com/apache/airflow/discussions>`__ if you look for longer discussion and have more information to share. +* The ``#user-best-practices`` channel on slack can be used to ask for and share best practices on using and deploying airflow. + * If you can provide description of a reproducible problem with Airflow software, you can open issue at `GitHub issues <https://github.com/apache/airflow/issues>`_ +* If you want to contribute back to Airflow, the ``#contributors`` slack channel for building the Airflow itself + + Using PyPI ''''''''''' @@ -143,9 +146,11 @@ More details: :doc:`/installation/installing-from-pypi` **Where to ask for help** -* The ``#troubleshooting`` channel on Airflow Slack for quick general +* The ``#user-troubleshooting`` channel on Airflow Slack for quick general troubleshooting questions. The `GitHub discussions <https://github.com/apache/airflow/discussions>`__ if you look for longer discussion and have more information to share. +* The ``#user-best-practices`` channel on slack can be used to ask for and share best + practices on using and deploying airflow. * If you can provide description of a reproducible problem with Airflow software, you can open issue at `GitHub issues <https://github.com/apache/airflow/issues>`__ @@ -205,9 +210,11 @@ and official constraint files- same that are used for installing Airflow from Py **Where to ask for help** * For quick questions with the Official Docker Image there is the ``#production-docker-image`` channel in Airflow Slack. -* The ``#troubleshooting`` channel on Airflow Slack for quick general +* The ``#user-troubleshooting`` channel on Airflow Slack for quick general troubleshooting questions. The `GitHub discussions <https://github.com/apache/airflow/discussions>`__ if you look for longer discussion and have more information to share. +* The ``#user-best-practices`` channel on slack can be used to ask for and share best + practices on using and deploying airflow. * If you can provide description of a reproducible problem with Airflow software, you can open issue at `GitHub issues <https://github.com/apache/airflow/issues>`__ @@ -262,9 +269,11 @@ More details: :doc:`helm-chart:index` * For quick questions with the Official Docker Image there is the ``#production-docker-image`` channel in Airflow Slack. * For quick questions with the official Helm Chart there is the ``#helm-chart-official`` channel in Slack. -* The ``#troubleshooting`` channel on Airflow Slack for quick general +* The ``#user-troubleshooting`` channel on Airflow Slack for quick general troubleshooting questions. The `GitHub discussions <https://github.com/apache/airflow/discussions>`__ if you look for longer discussion and have more information to share. +* The ``#user-best-practices`` channel on slack can be used to ask for and share best + practices on using and deploying airflow. * If you can provide description of a reproducible problem with Airflow software, you can open issue at `GitHub issues <https://github.com/apache/airflow/issues>`__
