You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafficcontrol.apache.org by fr...@apache.org on 2021/09/21 19:56:30 UTC

[trafficcontrol] branch master updated: Update link to join #traffic-control on the ASF slack

This is an automated email from the ASF dual-hosted git repository.

friede pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficcontrol.git


The following commit(s) were added to refs/heads/master by this push:
     new 7996403  Update link to join #traffic-control on the ASF slack
7996403 is described below

commit 7996403d202dca849e8d10c9d745e273181ebd19
Author: Zach Hoffman <zr...@apache.org>
AuthorDate: Tue Sep 21 12:39:52 2021 -0600

    Update link to join #traffic-control on the ASF slack
---
 .github/ISSUE_TEMPLATE/1-bug-report.md          | 2 +-
 .github/ISSUE_TEMPLATE/2-feature-request.md     | 2 +-
 .github/ISSUE_TEMPLATE/3-improvement-request.md | 2 +-
 .github/ISSUE_TEMPLATE/config.yml               | 2 +-
 docs/source/faq.rst                             | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/1-bug-report.md b/.github/ISSUE_TEMPLATE/1-bug-report.md
index c8b886c..fc588a4 100644
--- a/.github/ISSUE_TEMPLATE/1-bug-report.md
+++ b/.github/ISSUE_TEMPLATE/1-bug-report.md
@@ -26,7 +26,7 @@ If this issue identifies a security vulnerability, DO NOT submit it! Instead, co
 the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
 guidelines at https://apache.org/security regarding vulnerability disclosure.
 
-- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/slack-invite)
+- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request)
 or the Traffic Control Users mailing list (send an email to users-subscribe@trafficcontrol.apache.org to subscribe).
 - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
     * https://github.com/apache/trafficcontrol/issues
diff --git a/.github/ISSUE_TEMPLATE/2-feature-request.md b/.github/ISSUE_TEMPLATE/2-feature-request.md
index ff6819d..d6223b2 100644
--- a/.github/ISSUE_TEMPLATE/2-feature-request.md
+++ b/.github/ISSUE_TEMPLATE/2-feature-request.md
@@ -26,7 +26,7 @@ If this issue identifies a security vulnerability, DO NOT submit it! Instead, co
 the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
 guidelines at https://apache.org/security regarding vulnerability disclosure.
 
-- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/slack-invite)
+- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request)
 or the Traffic Control Users mailing list (send an email to users-subscribe@trafficcontrol.apache.org to subscribe).
 - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
     * https://github.com/apache/trafficcontrol/issues
diff --git a/.github/ISSUE_TEMPLATE/3-improvement-request.md b/.github/ISSUE_TEMPLATE/3-improvement-request.md
index 9fd5205..b6f9d32 100644
--- a/.github/ISSUE_TEMPLATE/3-improvement-request.md
+++ b/.github/ISSUE_TEMPLATE/3-improvement-request.md
@@ -26,7 +26,7 @@ If this issue identifies a security vulnerability, DO NOT submit it! Instead, co
 the Apache Traffic Control Security Team at security@trafficcontrol.apache.org and follow the
 guidelines at https://apache.org/security regarding vulnerability disclosure.
 
-- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/slack-invite)
+- For *SUPPORT QUESTIONS*, use the #traffic-control channel on the ASF slack (https://s.apache.org/tc-slack-request)
 or the Traffic Control Users mailing list (send an email to users-subscribe@trafficcontrol.apache.org to subscribe).
 - Before submitting, please **SEARCH GITHUB** for a similar issue or PR
     * https://github.com/apache/trafficcontrol/issues
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 77b9f65..52df685 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -17,5 +17,5 @@ contact_links:
     url: http://trafficcontrol.apache.org/mailing_lists
     about: Reach out to one of the Traffic Control mailing lists for discussion.
   - name: Support questions
-    url: https://s.apache.org/slack-invite
+    url: https://s.apache.org/tc-slack-request
     about: Visit us at ‌#traffic-control on Slack to ask a question.
diff --git a/docs/source/faq.rst b/docs/source/faq.rst
index 5c311c1..d311540 100644
--- a/docs/source/faq.rst
+++ b/docs/source/faq.rst
@@ -30,7 +30,7 @@ Who is using Traffic Control?
 
 How do I get help with Traffic Control?
 =======================================
-Join us at ``#traffic-control`` on the `ASF Slack <https://s.apache.org/slack-invite>`_ or send your questions to our `mailing list <ma...@trafficcontrol.apache.org>`_.  Slack is usually the best forum for quick Q&A type issues -- like when you are getting a Traffic Control CDN up and running or if you have a question about configuration. Any discussions that could potentially lead to decisions being made about the project -- like a new feature -- should happen on `the developer m [...]
+Join us at ``#traffic-control`` on the `ASF Slack <https://s.apache.org/tc-slack-request>`_ or send your questions to our `mailing list <ma...@trafficcontrol.apache.org>`_.  Slack is usually the best forum for quick Q&A type issues -- like when you are getting a Traffic Control CDN up and running or if you have a question about configuration. Any discussions that could potentially lead to decisions being made about the project -- like a new feature -- should happen on `the develop [...]
 
 How do I get involved with the development of Traffic Control?
 ==============================================================