Commit 61bab7d

authored

Merge pull request #2541 from kpreid/discord

Remove mentions of Discord.

2 parents 1d4927d + cf406ba commit 61bab7dCopy full SHA for 61bab7d

File tree

3 files changed

-12

lines changed

src
- about-this-guide.md
- diagnostics
  - error-codes.md
- getting-started.md

3 files changed

-12

lines changed

`‎src/about-this-guide.md‎`

Lines changed: 0 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -74,7 +74,6 @@ You might also find the following sites useful:`
`74`	`74`	`of the team procedures, active working groups, and the team calendar.`
`75`	`75`	`- [std-dev-guide] -- a similar guide for developing the standard library.`
`76`	`76`	`- [The t-compiler zulip][z]`
`77`		-- `#contribute` and `#wg-rustup` on [Discord](https://discord.gg/rust-lang).
`78`	`77`	`- The [Rust Internals forum][rif], a place to ask questions and`
`79`	`78`	`discuss Rust's internals`
`80`	`79`	`- The [Rust reference][rr], even though it doesn't specifically talk about`

`‎src/diagnostics/error-codes.md‎`

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -20,7 +20,7 @@ explanations should help users understand why their code cannot be accepted by`
`20`	`20`	`the compiler. Rust prides itself on helpful error messages and long-form`
`21`	`21`	`explanations are no exception. However, before error explanations are`
`22`	`22`	`overhauled[^new-explanations] it is a bit open as to how exactly they should be`
`23`		`-written, as always: ask your reviewer or ask around on the Rust Discord or Zulip.`
	`23`	`+written, as always: ask your reviewer or ask around on the Rust Zulip.`
`24`	`24`
`25`	`25`	`[^new-explanations]: See the draft RFC [here][new-explanations-rfc].`
`26`	`26`

`‎src/getting-started.md‎`

Lines changed: 7 additions & 10 deletions

Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,6 @@ quick guide for the most useful things. For more information, [see this`
`11`	`11`	`chapter on how to build and run the compiler](./building/how-to-build-and-run.md).`
`12`	`12`
`13`	`13`	`[internals]: https://internals.rust-lang.org`
`14`		`-[rust-discord]: http://discord.gg/rust-lang`
`15`	`14`	`[rust-zulip]: https://rust-lang.zulipchat.com`
`16`	`15`	`[coc]: https://www.rust-lang.org/policies/code-of-conduct`
`17`	`16`	`[walkthrough]: ./walkthrough.md`
`@@ -20,8 +19,7 @@ chapter on how to build and run the compiler](./building/how-to-build-and-run.md`
`20`	`19`	`## Asking Questions`
`21`	`20`
`22`	`21`	`If you have questions, please make a post on the [Rust Zulip server][rust-zulip] or`
`23`		`-[internals.rust-lang.org][internals]. If you are contributing to Rustup, be aware they are not on`
`24`		-Zulip - you can ask questions in `#wg-rustup` [on Discord][rust-discord].
	`22`	`+[internals.rust-lang.org][internals].`
`25`	`23`	`See the [list of teams and working groups][governance] and [the Community page][community] on the`
`26`	`24`	`official website for more resources.`
`27`	`25`
`@@ -30,10 +28,12 @@ official website for more resources.`
`30`	`28`
`31`	`29`	`As a reminder, all contributors are expected to follow our [Code of Conduct][coc].`
`32`	`30`
`33`		-The compiler team (or `t-compiler`) usually hangs out in Zulip [in this
`34`		`-"stream"][z]; it will be easiest to get questions answered there.`
	`31`	+The compiler team (or `t-compiler`) usually hangs out in Zulip in
	`32`	`+[the #t-compiler channel][z-t-compiler];`
	`33`	`+questions about how the compiler works can go in [#t-compiler/help][z-help].`
`35`	`34`
`36`		`-[z]: https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler`
	`35`	`+[z-t-compiler]: https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler`
	`36`	`+[z-help]: https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp`
`37`	`37`
`38`	`38`	`Please ask questions! A lot of people report feeling that they are "wasting`
`39`	`39`	expert time", but nobody on `t-compiler` feels this way. Contributors are
`@@ -162,15 +162,12 @@ incredibly helpful:`
`162`	`162`	`- [Triaging issues][triage]: categorizing, replicating, and minimizing issues is very helpful to the Rust maintainers.`
`163`	`163`	`- [Working groups][wg]: there are a bunch of working groups on a wide variety`
`164`	`164`	`of rust-related things.`
`165`		`-- Answer questions in the _Get Help!_ channels on the [Rust Discord`
`166`		`- server][rust-discord], on [users.rust-lang.org][users], or on`
`167`		`- [StackOverflow][so].`
	`165`	`+- Answer questions on [users.rust-lang.org][users], or on [Stack Overflow][so].`
`168`	`166`	`- Participate in the [RFC process](https://github.com/rust-lang/rfcs).`
`169`	`167`	`- Find a [requested community library][community-library], build it, and publish`
`170`	`168`	`it to [Crates.io](http://crates.io). Easier said than done, but very, very`
`171`	`169`	`valuable!`
`172`	`170`
`173`		`-[rust-discord]: https://discord.gg/rust-lang`
`174`	`171`	`[users]: https://users.rust-lang.org/`
`175`	`172`	`[so]: http://stackoverflow.com/questions/tagged/rust`
`176`	`173`	`[community-library]: https://github.com/rust-lang/rfcs/labels/A-community-library`

0 commit comments

Comments

(0)

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit 61bab7d

File tree

3 files changed

3 files changed

`‎src/about-this-guide.md‎`

`‎src/diagnostics/error-codes.md‎`

`‎src/getting-started.md‎`

0 commit comments