Drop all references of IRC

We don't use this anymore, so let's also not send people there. The
forum is our main place to get help.

Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>

developer_manual/digging_deeper/performance.rst

@@ -64,4 +64,4 @@ The recommendation is to automatically do 10000 PROPFINDs or file uploads, measu
 Getting help
 ------------
 
-If you need help with performance or other issues please ask on our `forums <https://help.nextcloud.com>`_ or on our IRC channel **#nextcloud-dev** on **irc.freenode.net**.
+If you need help with performance or other issues please ask on our `forums <https://help.nextcloud.com>`_.

developer_manual/prologue/bugtracker/codereviews.rst

@@ -57,7 +57,6 @@ requests should be handled
 Questions?
 ----------
 
-Feel free to drop a line on the `forums`_ or join us on `IRC`_.
+Feel free to drop a line on the `forums`.
 
 .. _forums: https://help.nextcloud.com/
-.. _IRC: https://webchat.freenode.net/?channels=nextcloud-dev

developer_manual/prologue/bugtracker/triaging.rst

@@ -38,9 +38,9 @@ General considerations
 
 * You need a `GitHub account <https://github.com>`_ to contribute to bug triaging.
 * If you are not familiar with the GitHub issue tracker interface (which is used by Nextcloud to handle bug reports), you `may find this guide useful <https://guides.github.com/features/issues/>`_.
-* You will initially only be able to comment on issues. The ability to close issues or assign labels will be given liberally to those who have shown to be willing and able to contribute. Just ask on IRC!
+* You will initially only be able to comment on issues. The ability to close issues or assign labels will be given liberally to those who have shown to be willing and able to contribute.
 * Read `our bug reporting guidelines <https://github.com/nextcloud/server/blob/master/CONTRIBUTING.md#submitting-issues>`_ so you know what a good report should look like and where things belong. The `issue template <https://raw.github.com/nextcloud/server/master/issue_template.md>`_ asks specifically for some information developers need to solve issues.
-* It might even be fixed, sometimes! It can also be fruitful to contact the `developers on IRC <irc://freenode/#nextcloud-dev>`_. Tell them you're triaging bugs and share what problem you bumped into. Or just ask on the test-pilots mailing list.
+* It might even be fixed, sometimes! It can also be fruitful to contact the developers. Tell them you're triaging bugs and share what problem you bumped into. Or just ask on the test-pilots mailing list.
 * To ensure no two people are working on the same issue, we ask you to simply add a comment like "I am triaging this" in the issue you want to work on, and when done, before or after executing the triaging actions, note similarly that you're done.
 
     To be able to tag and close issues, you need to have access to the repository. For the core and sync app repositories this also means having signed the contributor agreement. However, this isn't really needed for triaging as you can comment after you're done triaging and somebody else can execute those actions.

developer_manual/prologue/help_communication.rst

@@ -9,15 +9,6 @@ Forums
 ------
 Communicate via our `forums <https://help.nextcloud.com>`_.
 
-IRC channels
-------------
-Chat with us on `IRC <http://www.irchelp.org/>`_. All channels are on **irc.freenode.net**:
-
-* Setup: **#nextcloud**
-* Development: **#nextcloud-dev**
-* Design: **#nextcloud-design**
-* Mobile: **#nextcloud-mobile**
-
 
 Maintainers
 -----------

developer_manual/prologue/security.rst

@@ -253,4 +253,4 @@ Always validate the URL before redirecting if the requested URL is on the same d
 Getting help
 ------------
 
-If you need help to ensure that a function is secure please ask on our `forum <https://help.nextcloud.com>`_ or on our IRC channel **#nextcloud-dev** on **irc.freenode.net**.
+If you need help to ensure that a function is secure please ask on our `forum <https://help.nextcloud.com>`_.