You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by ms...@apache.org on 2019/06/13 16:47:30 UTC
[cassandra] branch trunk updated: ninja: Fix slack channel names in
docs
This is an automated email from the ASF dual-hosted git repository.
mshuler pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/trunk by this push:
new c241029 ninja: Fix slack channel names in docs
c241029 is described below
commit c24102906d41eb2f06b737c3c3d89be9a151e9f7
Author: Michael Shuler <ms...@apache.org>
AuthorDate: Thu Jun 13 11:47:22 2019 -0500
ninja: Fix slack channel names in docs
---
doc/source/bugs.rst | 2 +-
doc/source/contactus.rst | 10 ++++++----
doc/source/development/release_process.rst | 2 +-
3 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/doc/source/bugs.rst b/doc/source/bugs.rst
index 196ea3a..32d676f 100644
--- a/doc/source/bugs.rst
+++ b/doc/source/bugs.rst
@@ -18,7 +18,7 @@ Reporting Bugs
==============
If you encounter a problem with Cassandra, the first places to ask for help are the :ref:`user mailing list
-<mailing-lists>` and the ``Cassandra`` :ref:`Slack room <slack>`.
+<mailing-lists>` and the ``cassandra`` :ref:`Slack room <slack>`.
If, after having asked for help, you suspect that you have found a bug in Cassandra, you should report it by opening a
ticket through the `Apache Cassandra JIRA <https://issues.apache.org/jira/browse/CASSANDRA>`__. Please provide as much
diff --git a/doc/source/contactus.rst b/doc/source/contactus.rst
index 308d872..3ed9004 100644
--- a/doc/source/contactus.rst
+++ b/doc/source/contactus.rst
@@ -17,7 +17,7 @@
Contact us
==========
-You can get in touch with the Cassandra community either via the mailing lists or slack_ rooms.
+You can get in touch with the Cassandra community either via the mailing lists or :ref:`Slack rooms <slack>`.
.. _mailing-lists:
@@ -40,9 +40,11 @@ email to confirm your subscription. Make sure to keep the welcome email as it co
unsubscribe.
.. _slack:
+
Slack
-_____
+-----
To chat with developers or users in real-time, join our rooms on `ASF Slack <https://s.apache.org/slack-invite>`__:
-- ``#cassandra`` - for user questions and general discussions.
-- ``#cassandra-dev`` - strictly for questions or discussions related to Cassandra development.
+
+- ``cassandra`` - for user questions and general discussions.
+- ``cassandra-dev`` - strictly for questions or discussions related to Cassandra development.
diff --git a/doc/source/development/release_process.rst b/doc/source/development/release_process.rst
index 464ecd6..b3c4032 100644
--- a/doc/source/development/release_process.rst
+++ b/doc/source/development/release_process.rst
@@ -244,7 +244,7 @@ Fill out the following email template and send to both user and dev mailing list
Update Slack Cassandra topic
---------------------------
-Update Cassandra topic in Slack::
+Update topic in ``cassandra`` :ref:`Slack room <slack>`
/topic cassandra.apache.org | Latest releases: 3.11.4, 3.0.18, 2.2.14, 2.1.21 | ask, don't ask to ask
Tweet from @Cassandra
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org