diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8f6ae3f9dfc78eded0b978970fb5e18f50ed27cc..d9a8033e5b97ec9625d8a68dab7ff4f3d497286b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -17,5 +17,5 @@ You can reach out in the following ways: * [Discussions](https://github.com/arbor-sim/arbor/discussions). Any questions or remarks regarding using Arbor for your research are welcome. -* [Slack](https://mcnest.slack.com). If you're interested in developing Arbor itself, you can visit our Slack. +* [Gitter](https://gitter.im/arbor-sim/community). If you're interested in developing Arbor itself, get in touch on Gitter. * [Email](mailto:contact@arbor-sim.org). diff --git a/README.md b/README.md index f69290f6943c6e9c7aa3ccd0b3e68220e7216ca5..7a398352fae731478bdb4720162619c1479cd6de 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,7 @@ [](https://github.com/arbor-sim/arbor/actions/workflows/basic.yml) [](https://gitpod.io/#https://github.com/arbor-sim/arbor) [](https://docs.arbor-sim.org/en/latest/) +[](https://gitter.im/arbor-sim/community) # Arbor Library diff --git a/doc/contrib/index.rst b/doc/contrib/index.rst index ac7c61af9b2c36247e6cdc0ad818042918cd2ab0..62b77007e14460692e74690d4c8bee3f14f0ae27 100644 --- a/doc/contrib/index.rst +++ b/doc/contrib/index.rst @@ -152,6 +152,6 @@ You can reach out in the following ways: - `Discussions <https://github.com/arbor-sim/arbor/discussions>`__. Any questions or remarks regarding using Arbor for your research are welcome. -- `Slack <https://mcnest.slack.com>`__. If you’re interested in - developing Arbor itself, you can visit our Slack. +- `Gitter <https://gitter.im/arbor-sim/community>`__. If you’re interested in + developing Arbor itself, get in touch on Gitter. - `Email <mailto:contact@arbor-sim.org>`__. diff --git a/doc/contrib/pr.rst b/doc/contrib/pr.rst index 892cbd9f07f86cd5d800c3e29316d3ccb62b86e2..1d98cb7fea2510524afd12588860784ca9784f0b 100644 --- a/doc/contrib/pr.rst +++ b/doc/contrib/pr.rst @@ -18,7 +18,7 @@ the workflow is as follows: - You can use labels to categorize your PR. For very large PRs, it is likely the reviewer will have many questions and comments. It - can be helpful to reach out on our Slack, Discussions or by email + can be helpful to reach out on Gitter, Github Discussions or by email beforehand if you’ve big things planned for Arbor! - Commit logical units with clear commit messages. - Add a change summary to the PR message. If you remembered to commit