Merge pull request #1313 from SethTisue/fix-gitter-links

Author: SethTisue

_posts/2015-07-26-sip-slip-summary-july-2015.md

@@ -40,7 +40,7 @@ https://github.com/scala/scala/pull/4547 is a closed pull request against Scala
 ### Invitation to Comment
 
 For the time being, until a formal SLIP submission is contributed, please register interest
-on the [scala/slip gitter channel](https://gitter.im/scala/slip) with your contact details (preferably email, if you don't want to make that public, contact @dickwall directly on gitter).
+on the scala/slip gitter channel with your contact details (preferably email, if you don't want to make that public, contact @dickwall directly on gitter).
 
 ## Implicits in For Comprehensions
 

_posts/2015-12-09-schedule-update.md

@@ -38,7 +38,7 @@ Areas where participation is welcome include:
     and [docs.scala-lang](https://github.com/scala/scala.github.com/pulls) repos.
 
 You can talk to us about 2.12 on the [scala-internals mailing list](https://groups.google.com/forum/#!forum/scala-internals) 
-and the [scala/contributors Gitter room](https://gitter.im/scala/contributors).
+and the scala/contributors chat room.
 (An [expanded community page](https://www.scala-lang.org/community/) on the Scala site lists these and other forums and resources.)
 
 Your feedback will inform any revisions needed to the schedule described here.

_posts/2016-03-14-announcing-the-scala-center.md

@@ -79,8 +79,4 @@ logical platform to put this great work on a more stable basis.
 
 We are starting out now with a rough direction and expect that most details of the Center’s working will become clearer once we have gained some experience in our activities. For now, we are soliciting the community for help.
 
-If you have time or funding to contribute, and would like to work on a project that is useful to the community at large, please join us in the [Scala Center gitter channel](https://gitter.im/scala/center) and get involved!
-
-
-
-
+If you have time or funding to contribute, and would like to work on a project that is useful to the community at large, please talk to us on our forums and chat rooms and get involved!

_posts/2016-03-17-getting-into-scaladoc-dev.md

@@ -123,5 +123,5 @@ Here's a laundry list of things we need to do:
 The full list of ideas and things to do can be found on
 [scala-dev](https://github.com/scala/scala-dev/issues/84). Comment on the issue
 or reach out to one of us (@felixmulder, @heathermiller, @vladureche) on the
-[scala/contributors gitter](https://gitter.im/scala/contributors) if you're
+scala/contributors chat room if you're
 interested in knowing more!

_posts/2016-05-23-scala-moocs-specialization-launched.md

@@ -34,4 +34,4 @@ you can visit each course's landing page:
 - **[Parallel Programming](https://www.coursera.org/learn/scala-parallel-programming/)**
 
 More info about each course can be found on the [Scala Specialization page](https://www.coursera.org/specializations/scala), or on
-the [Scala Center's website](https://scala.epfl.ch/). Questions, or to join the discussion about the Scala Center, visit us in the [Scala Center gitter channel](https://gitter.im/scala/center)!
+the [Scala Center's website](https://scala.epfl.ch/). Questions, or to join the discussion about the Scala Center, visit us in our forums and chat rooms.

_posts/2016-07-12-a-reformed-scala-improvement-process.md

@@ -31,4 +31,5 @@ Starting next month, that too will see a reformed process mostly due to the fact
 
 #### Talk to us!
 
-Ideas? Questions? Concerns? Come on over to the [Scala Center gitter channel](https://gitter.im/scala/center) and holler at us! Or just come say hi :)
+Ideas? Questions? Concerns? Come on over to our forums and chat rooms and holler at us!
+

_posts/2017-02-28-collections-rework.md

@@ -203,7 +203,7 @@ In practice though, this kind of array can be treated as quasi-immutable, so we
 
 We are currently working on the new design as part of [SCP-007](https://github.com/scalacenter/advisoryboard/blob/master/proposals/007-collections.md) which is funded by [Scala Center](https://scala.epfl.ch/). At this stage all work is happening in the [collection-strawman](https://github.com/scala/collection-strawman) repository with the goal of refining and completing it to the point where we are confident that it can and should become a part of Scala 2.13. The core project team consists of Julien Richard-Foy (from Scala Center), Martin Odersky, Rex Kerr and myself (as a member of the Scala team at Lightbend who maintain the Scala compiler).
 
-If you'd like to get involved, now is the time to weigh in on the discussions that are happening on the pull requests and issues. We also have a [Gitter channel](https://gitter.im/scala/collection-strawman) and a [Scala Contributors](https://contributors.scala-lang.org/t/ongoing-work-on-standard-collections-redesign/293) discourse discussion thread.
+If you'd like to get involved, now is the time to weigh in on the discussions that are happening on the pull requests and issues. We also have a chat room and a [Scala Contributors](https://contributors.scala-lang.org/t/ongoing-work-on-standard-collections-redesign/293) discourse discussion thread.
 
 A few topics still need further exploration:
 

_posts/2018-01-16-community-build-growth.md

@@ -116,12 +116,10 @@ questions you might have are already answered there.
 If you have a question or want to get involved in the community
 build or in open source work on Scala more generally, come to the Scala
 contributors [forum](https://contributors.scala-lang.org) or
-[chat room](https://gitter.im/scala/contributors).
+chat room.
 
 Especially involved or specialized discussions about the community
-build can move to the community build's own
-[Gitter room](https://gitter.im/scala/community-builds) and
-[GitHub issues](https://github.com/scala/community-build/issues).
+build can move to [GitHub issues](https://github.com/scala/community-build/issues).
 
 ## Credits
 

_posts/2019-03-18-announcing-new-community-representative.md

@@ -17,7 +17,7 @@ Rob, aka [tpolecat](https://tpolecat.github.io/about.html), is familiar in the S
 * his leadership role in [Typelevel](https://typelevel.org/)
 * his popular open-source projects, including [Doobie](https://github.com/tpolecat/doobie) (a database library) and [Tut](https://github.com/tpolecat/tut) (a tool for machine-checked documentation)
 * his many conference talks on pure-functional programming
-* his tireless efforts on [Gitter](https://gitter.im/scala/scala) and IRC to help newcomers learn Scala and functional programming
+* his tireless efforts on Gitter and IRC to help newcomers learn Scala and functional programming
 
 At his day job, he writes Scala code at the [Gemini Observatory](https://www.gemini.edu/), supporting astronomy research. 🔭✨
 

blog/_posts/2017-11-30-bloop-release.md

@@ -185,8 +185,8 @@ developers writing Scala code. With this effort, the Scala Center continues its
 commitment to improve the tooling in the Scala ecosystem and help open source
 developers and companies alike be more productive.
 
-If you have a question or want to get involved, come to [the Scala Center Gitter
-channel](https://gitter.im/scala/center) to chat!
+If you have a question or want to get involved, come to our forums and chat rooms
+to talk!
 
 [scalacenter/bloop]: https://github.com/scalacenter/bloop
 [nailgun]: https://github.com/facebook/nailgun/

news/_posts/2017-03-06-roadmap-2.13.md

@@ -26,4 +26,4 @@ In tandem, the modularisation of the standard library (begun with Scala 2.11) wi
 
 Scala 2.13 is a library release, which means the language itself won't see big changes. However, we continue to invest heavily in the implementation, with a single goal: make the compiler faster. The first phase of this work involves benchmarking infrastructure, to guide our progress towards a faster compiler. After that, we will attack slowness on all fronts with all available tools. In addition to YourKit and other JVM profilers, which we have been using intensively over the years, we now have a JMH benchmarking harness for the compiler. We are also investigating lower-level performance (cpu caches, memory access patterns, JIT profiles, etc). We are eager to hear your ideas at the compiler performance theme issue. Please head over to [the new compiler-benchmark repo](https://github.com/scala/compiler-benchmark) for the benchmarks and the issue tracker, or [discuss this theme here](https://github.com/scala/scala-dev/issues/322).
 
-Finally, there are [many more things](https://github.com/scala/scala-dev/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.13+label%3Awishlist) we'd like to include in 2.13. Let us know if you'd like to work on one of these. We're always happy to help! In addition to GitHub, you'll find us on [Scala Contributors](https://contributors.scala-lang.org) (forum) and [scala/contributors](https://gitter.im/scala/contributors) (chat).
+Finally, there are [many more things](https://github.com/scala/scala-dev/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.13+label%3Awishlist) we'd like to include in 2.13. Let us know if you'd like to work on one of these. We're always happy to help! In addition to GitHub, you'll find us on our forums and chat rooms.