From 533e166a7d5e48813e6c8daee31b7fc9ebe7904e Mon Sep 17 00:00:00 2001 From: Mario Colombo Date: Wed, 17 Apr 2024 18:24:22 +0200 Subject: [PATCH 1/2] Replace Slack with Discord --- docs/contributing/code.rst | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/contributing/code.rst b/docs/contributing/code.rst index 45091eb6a7..40bff1a9b7 100644 --- a/docs/contributing/code.rst +++ b/docs/contributing/code.rst @@ -17,7 +17,7 @@ Here's what the contribution process looks like in brief: #. Fork our `GitHub`_ repository, https://github.com/django-cms/django-cms #. Work locally and push your changes to your repository. #. When you feel your code is good enough for inclusion, send us a pull request. -#. After that, please join the `Slack Channel`_ of our Pull Request Review work group (#workgroup-pr-review). This group of friendly community members is dedicated to reviewing pull requests. Report your PR and find a “pr review buddy” who is going to review your pull request. +#. After that, please join our Discord server (`#contributors `_). This group of friendly community members is dedicated to reviewing pull requests. Report your PR and find a “pr review buddy” who is going to review your pull request. #. Get acknowledged by the django CMS community for your contribution See the :ref:`contributing_patch` how-to document for a walk-through of this process. @@ -28,7 +28,7 @@ Basic requirements and standards ******************************** If you're interested in developing a new feature for the CMS, it is recommended -that you first discuss it on the `Slack channel `_ so as +that you first discuss it on `Discord `_ so as not to do any work that will not get merged in anyway. - Code will be reviewed and tested by at least one core developer, preferably @@ -107,7 +107,7 @@ coverage will only be accepted with a very good reason; bug-fixing patches **must** demonstrate the bug with a test to avoid regressions and to check that the fix works. -We have a `Slack Channel`_ and of course the code reviews mechanism on GitHub - do use them. +We have a `Discord Server `_ and of course the code reviews mechanism on GitHub - do use them. .. _contributing_frontend: @@ -202,4 +202,3 @@ the source modules. .. _freenode: http://freenode.net/ .. _pull request: http://help.github.com/send-pull-requests/ .. _git: http://git-scm.com/ -.. _Slack Channel: https://django-cmsworkspace.slack.com/ From 4691a15bd49769da196b13f271a9fa6b6c4bca6a Mon Sep 17 00:00:00 2001 From: Mario Colombo Date: Wed, 17 Apr 2024 18:41:14 +0200 Subject: [PATCH 2/2] more occurrences --- docs/contributing/code_of_conduct.rst | 3 +-- docs/contributing/development-community.rst | 12 ++++-------- docs/contributing/development-policies.rst | 4 ++-- .../guideline-for-django-cms-projects.rst | 4 ++-- docs/contributing/management.rst | 3 +-- docs/index.rst | 4 ++-- docs/introduction/index.rst | 2 +- 7 files changed, 13 insertions(+), 19 deletions(-) diff --git a/docs/contributing/code_of_conduct.rst b/docs/contributing/code_of_conduct.rst index 2579afef76..ad56eaedf2 100644 --- a/docs/contributing/code_of_conduct.rst +++ b/docs/contributing/code_of_conduct.rst @@ -11,8 +11,7 @@ and polite. We will not tolerate abusive behaviour or language or any form of harassment. Individuals whose behaviour is a cause for concern will be given a warning, and if -necessary will be excluded from participation in official django CMS channels (Slack -group, email lists, etc) and events. The `Django Software Foundation +necessary will be excluded from participation in official django CMS channels and events. The `Django Software Foundation `_ will also be informed of the issue. Raising a concern diff --git a/docs/contributing/development-community.rst b/docs/contributing/development-community.rst index d4fb9ba553..8c51879e0d 100644 --- a/docs/contributing/development-community.rst +++ b/docs/contributing/development-community.rst @@ -69,19 +69,15 @@ But before you start getting your hands dirty, you should make sure to join us o order to stay updated with the latest news and to connect with other users across the world. -You can join us online: +You can join us online through our `support channels `_ -- in our `django CMS Slack channel `_ -- on `StackOverflow `_ - -You should make sure to join our Slack workspace. It is our main communication platform. -Users from all over the world use Slack to talk about django CMS and to support each +You should make sure to join our Discord server. It is our main communication platform. +Users from all over the world use Discord to talk about django CMS and to support each other in answering support requests. StackOverflow is a very popular, community-based space to find and contribute answers to technical challenges You can also follow: -- the `@djangocms `_ Twitter account for general - announcements +- the `django CMS Youtube account `_ - the `django CMS Association LinkedIn `_ account diff --git a/docs/contributing/development-policies.rst b/docs/contributing/development-policies.rst index 5094accb22..474d92075d 100644 --- a/docs/contributing/development-policies.rst +++ b/docs/contributing/development-policies.rst @@ -62,7 +62,7 @@ To create a proposal... 1. please use this `DEP template `_ 2. create a discussion in the main `Github repository `_ 3. discuss, discuss, discuss -4. join the Tech Committee `Slack Channel `_ (#technical-committee) and make the team aware of your proposal after the proposal has been reviewed by the Technical Committee, it is put to a vote at one of the weekly meetings of the technical committee +4. join the Tech Committee (`#technical-committee `_) and make the team aware of your proposal after the proposal has been reviewed by the Technical Committee, it is put to a vote at one of the weekly meetings of the technical committee **************** @@ -82,7 +82,7 @@ Example of retrospective approach. * ... * Unscheduled Releases -> e.g. bug fix -> 3.x.x -The release management workgroup can be found on `Slack `_ in #release-management channel. +Release management is managed on `Discord `_ in the #technical-committee channel. For questions regarding the release process please join the channel and reach out. We're happy to help. Long-Term Support Release diff --git a/docs/contributing/guideline-for-django-cms-projects.rst b/docs/contributing/guideline-for-django-cms-projects.rst index a3407a447a..4e09230e99 100644 --- a/docs/contributing/guideline-for-django-cms-projects.rst +++ b/docs/contributing/guideline-for-django-cms-projects.rst @@ -31,8 +31,8 @@ Approval by Tech Committee of the django CMS Association New projects or project transfers under the django CMS patronage must first be approved by the `Tech Committee `_. -For that you should join the #tech-committee channel on `Slack -`_ and simply submit your proposal. Then, the TC +For that you should join the #tech-committee channel on `Discord +`_ and simply submit your proposal. Then, the TC decides whether or not your project is in line with the product roadmap and overall vision for django CMS. diff --git a/docs/contributing/management.rst b/docs/contributing/management.rst index 8508b73304..98b06f2365 100644 --- a/docs/contributing/management.rst +++ b/docs/contributing/management.rst @@ -27,8 +27,7 @@ Raising an issue Except in the case of security matters, of course, you're welcome to raise -issues in any way that suits you - the Slack group -` or in person if you happen to meet another django CMS +issues in any way that suits you or in person if you happen to meet another django CMS developer. It's very helpful though if you don't just raise an issue by mentioning it to people, but actually diff --git a/docs/index.rst b/docs/index.rst index d6d7bbfb01..dbaa877037 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -123,10 +123,10 @@ organisation that exists to support the development of django CMS and its commun .. rst-class:: column column2 -Slack +Discord ~~~~~ -Join `our friendly Slack group `_ for **support** and +Join `our friendly Discord server `_ for **support** and to **share ideas** and **discuss technical questions** with other members of the community. diff --git a/docs/introduction/index.rst b/docs/introduction/index.rst index 5e279c4d81..604a10f536 100644 --- a/docs/introduction/index.rst +++ b/docs/introduction/index.rst @@ -37,4 +37,4 @@ django CMS by hand, rather than using the django CMS quistart project, see :doc:`/introduction/01-install` and then follow the rest of the tutorials. Either way, you'll be able to find support and help from the numerous friendly members -of the django CMS community on `our Slack group `_. +of the django CMS community on `our Discord server `_.