remove most references to the discord server

src/SUMMARY.md

@@ -109,7 +109,6 @@
         - [Crater agents](./infra/docs/crater-agents.md)
         - [Dev Desktops](./infra/docs/dev-desktop.md)
         - [GitHub App for dev-desktops](./infra/docs/dev-desktop-github-app.md)
-        - [Discord moderation bot](./infra/docs/discord-mods-bot.md)
         - [Domain names and DNS](./infra/docs/dns.md)
         - [docs.rs](./infra/docs/docs-rs.md)
         - [ECS services management](./infra/docs/ecs-services.md)

src/governance/project-groups.md

@@ -11,7 +11,7 @@ Project groups are a kind of Rust team intended to work on a specific project wi
   - A charter outlining the group's scope and goals.
   - Appointed shepherds and team liaisons.
   - An associated repository.
-  - Dedicated streams on Discord/Zulip/etc.
+  - Dedicated streams on Zulip/etc.
 
 [RFC 2856]: https://rust-lang.github.io/rfcs/2856-project-groups.html
 
@@ -49,7 +49,7 @@ A project group should have the following;
 - No _"formal decision making power"_: meaning that they are not able to accept RFCs on `rust-lang/rfcs`.
   - Groups are of course encouraged to create RFCs as well as advocate their concerns and desired changes to the Rust teams and community.
 - Dedicated space(s) in of Rust's officially managed discussion platforms.
-  - As of the time of this writing this includes [Zulip] and [Discord].
+  - As of the time of this writing this is [Zulip].
   - Ideally the group should use the same platform as their parent team to ease communication, though there may be cases where the team agrees to a group trying out a different platform.
 
 ### Creating The Charter
@@ -73,7 +73,6 @@ Since project groups are approved by their relevant parent team, it's up to each
 
 [rust-lang.org]: https://rust-lang.org
 [zulip]: https://rust-lang.zulipchat.com
-[discord]: https://discord.gg/rust-lang
 
 ## Initial Setup
 
@@ -141,7 +140,7 @@ This is a high level overview of the complete process of a project group.
 3. Create infrastructure for group.
 
    - GitHub repository under `rust-lang` for hosting work and discussions, such as for draft RFCs.
-   - A Discord channel or a Zulip stream for communication.
+   - A Zulip stream for communication.
    - Project group in [`rust-lang/team`], as well as a team on GitHub, for handling permissions.
 
 4. Create a post on the Inside Rust blog announcing creation of the group. Be sure to include the following information.

src/how-to-start-contributing.md

@@ -14,8 +14,6 @@ other contributors on the following places:
   teams and contributors. It is also a great place to observe on what is going on.
   - You can check out e.g. the compiler team (`t-compiler`) Zulip ["channel"][t-compiler-channel]
 - [internals.rust-lang.org][internals] (IRLO) is a forum for discussing development of Rust.
-- [Rust Discord][rust-discord] can be used to ask about [Rustup][rustup] contributions
-  in the `#wg-rustup` channel.
 
 See also the [list of teams and working groups][governance] and [the Community page][community] on the
 official website for more resources.
@@ -128,17 +126,14 @@ There are various ways in which you can contribute to Rust projects:
 
 - Or, if you like programming language discussions, you could participate in our [RFC process](https://github.com/rust-lang/rfcs).
 
-- You can also answer questions to help other Rust users, in the _Get Help!_ channels on the [Rust Discord
-  server][rust-discord], on [users.rust-lang.org][users] (URLO), or on [StackOverflow][so].
+- You can also answer questions to help other Rust users, on [users.rust-lang.org][users] (URLO), or on [StackOverflow][so].
 
 [rustdoc-ui]: https://rustc-dev-guide.rust-lang.org/rustdoc-internals.html
 [rustc-perf-ui]: https://github.com/rust-lang/rustc-perf/tree/master/site
-[rust-discord]: https://discord.gg/rust-lang
 [users]: https://users.rust-lang.org/
 [so]: http://stackoverflow.com/questions/tagged/rust
 [rustup]: https://github.com/rust-lang/rustup
 [internals]: https://internals.rust-lang.org
-[rust-discord]: http://discord.gg/rust-lang
 [rust-zulip]: https://rust-lang.zulipchat.com
 [coc]: https://www.rust-lang.org/policies/code-of-conduct
 [issue-triage]: ./release/issue-triaging.md

src/lang/index.md

@@ -4,7 +4,6 @@ This section documents meta processes by the language team.
 
 ### External Links
 
-- The language team has communications channels on [Discord] as well as [Zulip].
+- The language team has communications channels on [Zulip].
 
-[Discord]: https://discord.gg/rust-lang
 [Zulip]: https://rust-lang.zulipchat.com

src/lang/triage-meeting-procedure.md

@@ -40,8 +40,7 @@ To execute this meeting you:
 
 ## Main meeting
 
-* Ping the team on discord `@lang-team`
-* Begin the recording on Zoom, if you have acccess 
+* Begin the recording on Zoom, if you have access 
     * If nobody has access to the recording, oh well, we don't do it every week
 * Discuss item by item and take some notes on what was said
     * Add specific actions to the action items section above

src/platforms/discord.md

@@ -1,44 +1,5 @@
 ## Discord
 
-Rust's Discord is currently used by a variety of teams such as Community, Ops, and Documentation, as well as their working groups. It is also maintained as a communication tool for Domain Working Groups, and provides a space for general discussion among Rust users, contributors, and beginners. 
-
-# Where to go for help with using Discord
-Discord's support center provides documentation about its [user interface](https://support.discordapp.com/hc/en-us/categories/200404398) and [account settings](https://support.discordapp.com/hc/en-us/categories/200404358).
-
-# Getting started
-
-1) Understand community standards <br/>
-Discord, like all official Rust spaces, is governed by the Code of Conduct. Before joining the conversation there, you can prepare by reading the [Code of Conduct and Moderation Guidelines](https://www.rust-lang.org/community#conduct).
-It is also useful to read [Discord's Community Guidelines](https://discordapp.com/guidelines)
-
-2) Access channels <br/>
-To access the Rust Discord, visit [https://discord.gg/rust-lang](https://discord.gg/rust-lang). If you do not already have a Discord account, you can register for one as part of the process of gaining access. Your first action should be agreeing to our Code of Conduct by following the instructions in #welcome.
-
-3) Configure notifications <br/>
-It is a good idea to disable notifications for channels that are not relevant to you, so that you will not be overwhelmed with messages. 
-Select the expansion arrow next to the server name banner (titled "The Rust Programming Language") and select Notifications from the dropdown. Then follow the configuration instructions provided [on the Discord Support site](https://support.discordapp.com/hc/en-us/articles/215253258-Notifications-Settings-101).
-
-# Appropriate conversation
-Discussions should be related to the channel purpose. On team channels, conversation should be related to team business.
-All channels are expected to be used for purposes related to the Rust project. Discussion of (for example) wildlife or sightseeing are not appropriate. 
-
-# Channels
-
-The following channels are relevant to newcomers to the Rust project: 
-* welcome - Where you agree to the CoC.
-* rust-usage - This is a channel where you can access support for resolving specific language use questions. The [Rust Users Forum](https://users.rust-lang.org/) is also relevant to your needs.
-* beginners - Here, you can meet people who began using Rust relatively recently. 
-* contribute - Interested in contributing to the Rust project? In addition to joining this channel, you can subscribe to the [This Week In Rust](https://this-week-in-rust.org/) newsletter, where many opportunities are regularly posted. 
-It may also help to find out more about [specific teams](https://www.rust-lang.org/governance#teams).
-
-Channels outside of General are for contributors to Rust.
-
-# Messages
-Discord conversation takes place when people are available, so you should not generally expect that your messages will receive a response quickly unless a meeting is taking place. Depending on how your notifications are configured, you will see a red circle on top of the Discord icon in your system tray when new messages are received. If you wish to communicate with a specific individual, right-click on their user icon and select "Message" in the dropdown menu.
-
-# Read-only view
-Set up a Discord account (as described in Getting Started, above) in order to access Discord. There is not
-currently a read-only archive view available. 
-
-
+Rust used to have an official server on Discord. It has been shut down and is read-only now in favor of Zulip.
 
+The read-only view can be accessed via [https://discord.gg/rust-lang](https://discord.gg/rust-lang).

src/release/issue-triaging.md

@@ -38,7 +38,7 @@ When an issue is opened, it usually receives the `needs-triage` label automatica
 To do the initial triage and remove the `needs-triage` label, the following conditions should be fulfilled/considered. It's okay if not all of these are always considered. Treat this non-exhaustive list as a guideline, not a hard checklist:
 
 - The issue should make sense, that is, it should present a problem.
-    - For example, if an issue is a question about Rust in general, the issue should be closed and the user redirected to [URLO]/[Discord]. You can, of course, answer the question too, but make sure to mention that the user should go to [URLO]/[Discord] next time.
+    - For example, if an issue is a question about Rust in general, the issue should be closed and the user redirected to [URLO]. You can, of course, answer the question too, but make sure to mention that the user should go to [URLO] next time.
 - Check if this issue is a duplicate of earlier-reported issues.
     - If you are certain this is a duplicate, close this issue as a duplicate of the earlier issue. Make sure this is obvious in the backlink of the earlier issue, or explicitly link to the duplicate issue.
     - If you are not sure, you can still leave a comment to indicate the other issue is possibly a duplicate, similar, or related.
@@ -225,7 +225,6 @@ Another useful thing to do is to go through `E-needs-mcve` and `E-needs-bisectio
 [`rust-lang/rust`]: https://github.com/rust-lang/rust
 [URLO]: https://users.rust-lang.org
 [IRLO]: https://internals.rust-lang.org/
-[Discord]: https://discord.gg/rust-lang
 [`cargo-bisect-rustc`]: https://github.com/rust-lang/cargo-bisect-rustc
 [`t-release/triage`]: https://rust-lang.zulipchat.com/#narrow/stream/242269-t-release.2Ftriage