You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "potiuk (via GitHub)" <gi...@apache.org> on 2024/02/16 21:28:34 UTC
[PR] Update slack channel names following new naming schemes [airflow]
potiuk opened a new pull request, #37495:
URL: https://github.com/apache/airflow/pull/37495
Following LAZY CONSENSUS on devlist:
https://lists.apache.org/thread/v9s6pc46o96y7xpd519mflnlx7r8sslo
we rename the channels in our docs.
<!--
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.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information.
In case of fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a newsfragment file, named `{pr_number}.significant.rst` or `{issue_number}.significant.rst`, in [newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update slack channel names following new naming schemes [airflow]
Posted by "Taragolis (via GitHub)" <gi...@apache.org>.
Taragolis commented on code in PR #37495:
URL: https://github.com/apache/airflow/pull/37495#discussion_r1493006759
##########
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)
Review Comment:
Maybe instead of related to development use something related to contribution to Airflow.
I worry that someone see development and this one would be a trigger to “I develop my pipeline and something doesn’t work well may I ask in contributors channel”
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update slack channel names following new naming schemes [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on code in PR #37495:
URL: https://github.com/apache/airflow/pull/37495#discussion_r1493016911
##########
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)
Review Comment:
Yeah. Context is important.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update slack channel names following new naming schemes [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk merged PR #37495:
URL: https://github.com/apache/airflow/pull/37495
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update slack channel names following new naming schemes [airflow]
Posted by "Taragolis (via GitHub)" <gi...@apache.org>.
Taragolis commented on code in PR #37495:
URL: https://github.com/apache/airflow/pull/37495#discussion_r1493007438
##########
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)
Review Comment:
I know this placed into the contributors documentation
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Update slack channel names following new naming schemes [airflow]
Posted by "jedcunningham (via GitHub)" <gi...@apache.org>.
jedcunningham commented on code in PR #37495:
URL: https://github.com/apache/airflow/pull/37495#discussion_r1493015740
##########
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)
Review Comment:
I think it's okay, we are already deep in the contributing docs here. But good call out.
--
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-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org