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.
2026-11-04 07:12:48 +00:00 · 2024-02-16 22:55:40 +01:00
1 parent a7307c5993
commit 45cf40f673
@@ -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
@@ -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
@@ -118,7 +118,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
@@ -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
@@ -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.
@@ -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>`_
@@ -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
 ------------------------------------
@@ -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/>`_.
@@ -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 ?
@@ -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>`__