Switch from freenode to libera

* remove unhelpful comment * yes, macports is also moved to libera
MoarVM · Jul 18, 2021 · a0d05b4 · a0d05b4
1 parent 8a5e05b
commit a0d05b4
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 7 deletions.
diff --git a/README.markdown b/README.markdown
@@ -89,7 +89,7 @@ Some key features provided by MoarVM include:
 
 Contributions by pull request are accepted. Commit bits are given to those who
 contribute quality work. If you are interested in contributing, drop by the
-`#moarvm` channel on freenode.org.
+`#moarvm` channel on libera.chat.
 
 See the LICENSE file in the root directory for information on the license of
 the source code in the MoarVM repository.

diff --git a/docs/contributing.org b/docs/contributing.org
@@ -5,17 +5,14 @@ Or, how to work on MoarVM.
 * Community
 
 MoarVM is a fairly small community. We communicate primarily on the
-#moarvm channel on freenode, and to a lesser extent via github issues.
+#moarvm channel on libera.chat, and to a lesser extent via github issues.
 
 We use IRC bots to keep up to date with new commits that are
 published; but those don't always work well, unfortunately.
 
 The [[https://rakudoweekly.blog/][Rakudo Weekly News]] newsletter publishes progress in MoarVM, and there's
 also the =/r/rakulang= subreddit.
 
-Apparently you can connect to freenode via discord, but the author of
-this text wouldn't know how.
-
 * Code Standards
 
 Some things to keep in mind are:

diff --git a/docs/reveal.md b/docs/reveal.md
@@ -163,4 +163,4 @@ work on trying to get a more concrete roadmap together there.
 ## Where is...
 
 * The Git repository: https://github.com/MoarVM/MoarVM
-* The IRC channel: #moarvm on freenode.org
+* The IRC channel: #moarvm on libera.chat
diff --git a/ports/macports/README.md b/ports/macports/README.md
@@ -47,6 +47,6 @@ When updating the `Portfile` to reflect the new release:
         * **port**: `MoarVM`
         * Make sure to attach the diff.
 
-    * Hang out in `#macports` on freenode and mention the ticket or write to the macports-dev mailing list with URL to the ticket and a descriptive subject if there is no response for a while.
+    * Hang out in `#macports` on libera.chat and mention the ticket or write to the macports-dev mailing list with URL to the ticket and a descriptive subject if there is no response for a while.
 
 5. Push the updated `Portfile` also to git.