From 92994fe7886b652aaec1a706c944852d4ce6bb35 Mon Sep 17 00:00:00 2001 From: Eric Huss Date: Wed, 9 Aug 2023 15:12:20 -0700 Subject: [PATCH] Fix some broken links. --- src/community/survey-faq.md | 2 +- src/compiler/prioritization/procedure.md | 2 +- src/compiler/steering-meeting/how-to-run-planning.md | 2 +- src/docs-rs/self-hosting.md | 7 +++++-- src/infra/docs/bors.md | 2 +- src/platforms/twitter.md | 2 +- src/release/process.md | 2 +- src/triagebot/pr-assignment.md | 2 +- 8 files changed, 12 insertions(+), 9 deletions(-) diff --git a/src/community/survey-faq.md b/src/community/survey-faq.md index e9ca96cb6..6df21a4ea 100644 --- a/src/community/survey-faq.md +++ b/src/community/survey-faq.md @@ -1,6 +1,6 @@ # State of Rust Survey FAQ -In this FAQ we try to answer common questions about the Annual State of the Rust Language Community Survey. If in your opinion there is a missing question or if you have a concern about this document, please do not hesitate to contact the [Rust Community Team](community-team@rust-lang.org) or open an [issue with the Community Team](https://github.com/rust-community/team/issues). +In this FAQ we try to answer common questions about the Annual State of the Rust Language Community Survey. If in your opinion there is a missing question or if you have a concern about this document, please do not hesitate to contact the [Rust Community Team](mailto:community-team@rust-lang.org) or open an [issue with the Community Team](https://github.com/rust-community/team/issues). ## Why is this survey important for the Rust project? diff --git a/src/compiler/prioritization/procedure.md b/src/compiler/prioritization/procedure.md index 4a532716c..9aaf49ba0 100644 --- a/src/compiler/prioritization/procedure.md +++ b/src/compiler/prioritization/procedure.md @@ -68,7 +68,7 @@ Paste the markdown file of this week [performance triage logs](https://github.co ### Announce the meeting on Zulip -About two hours before the scheduled meeting, create a new topic on the Zulip stream `#t-compiler/meetings` titled "[weekly] YYYY-MM-DD" using the the following message template: +About two hours before the scheduled meeting, create a new topic on the Zulip stream `#t-compiler/meetings` titled "\[weekly] YYYY-MM-DD" using the the following message template: ```text Hi @*T-compiler/meeting*; the triage meeting will happen tomorrow in about 2 hours. diff --git a/src/compiler/steering-meeting/how-to-run-planning.md b/src/compiler/steering-meeting/how-to-run-planning.md index cf1ecb521..b57e79834 100644 --- a/src/compiler/steering-meeting/how-to-run-planning.md +++ b/src/compiler/steering-meeting/how-to-run-planning.md @@ -26,7 +26,7 @@ To actually make the final selection, we recommend * Typical ratio is 2 technical, 1 non-technical, but this is not set in stone * It's ok to have fewer than 3 meetings -[compiler-team]: XXX +[compiler-team]: https://github.com/rust-lang/compiler-team/ ## Announce the meetings diff --git a/src/docs-rs/self-hosting.md b/src/docs-rs/self-hosting.md index 37429e672..562f56be2 100644 --- a/src/docs-rs/self-hosting.md +++ b/src/docs-rs/self-hosting.md @@ -1,6 +1,9 @@ # Self hosting a docs.rs instance -These are instructions for deploying the server in a production environment. For instructions on developing locally without docker-compose, see [Developing without docker-compose](no-docker-compose.html). +These are instructions for deploying the server in a production environment. For instructions on developing locally without docker-compose, see [Developing without docker-compose][no-docker-compose]. + + +[no-docker-compose]: https://github.com/rust-lang/docs.rs/wiki/Developing-without-docker-compose Here is a breakdown of what it takes to turn a regular server into its own version of docs.rs. @@ -249,4 +252,4 @@ Next, we can unlock the builder so it can start checking new crates: $ sudo su - cratesfyi -c "cd ~/docs.rs && cargo run --release -- build unlock" ``` -And we're done! Changes to the site or the build behavior should be visible now. \ No newline at end of file +And we're done! Changes to the site or the build behavior should be visible now. diff --git a/src/infra/docs/bors.md b/src/infra/docs/bors.md index e6c44eeaa..a12a65569 100644 --- a/src/infra/docs/bors.md +++ b/src/infra/docs/bors.md @@ -84,7 +84,7 @@ There are multiple steps needed to add a repository to our Bors instance: [Homu]: https://github.com/rust-lang/homu [bors-config]: https://github.com/rust-lang/homu/blob/master/cfg.production.toml [bors.rust-lang.org]: https://bors.rust-lang.org -[ecs]: ./ecs-service.md +[ecs]: ./ecs-services.md [rust-lang/homu]: https://github.com/rust-lang/homu [team-permissions.rs]: https://github.com/rust-lang/team/blob/52b4370214e1c8eabe483f3a26f22733d94b326f/config.toml#L18-L37 [bors-permission]: https://github.com/rust-lang/team/blob/a1532ec2b08c9d40c0a2c7643ffe72de9671e265/teams/wg-compiler-performance.toml#L25-L26 diff --git a/src/platforms/twitter.md b/src/platforms/twitter.md index 7045b1e7a..9ecc58006 100644 --- a/src/platforms/twitter.md +++ b/src/platforms/twitter.md @@ -10,7 +10,7 @@ currently maintained by the infrastructure team. ## Twitter Guidelines -The project runs the Twitter account [@rustlang] +The project runs the Twitter account `@rustlang`. The account is handled by a small team of volunteers. The account will mostly tweet links to the Rust blog and Rust Insiders blog. diff --git a/src/release/process.md b/src/release/process.md index 662168cea..f1bd20a71 100644 --- a/src/release/process.md +++ b/src/release/process.md @@ -155,7 +155,7 @@ When the release process end you'll be able to install the new nightly with: RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup toolchain install nightly ``` -[awscli]: /infra/docs/aws-access.md#using-the-aws-cli +[awscli]: ../infra/docs/aws-access.md#using-the-aws-cli [rust-lang/rust]: https://github.com/rust-lang/rust [simpleinfra]: https://github.com/rust-lang/simpleinfra [ripgrep]: https://github.com/burntsushi/ripgrep diff --git a/src/triagebot/pr-assignment.md b/src/triagebot/pr-assignment.md index 4bbaaa324..d42f5d63a 100644 --- a/src/triagebot/pr-assignment.md +++ b/src/triagebot/pr-assignment.md @@ -12,7 +12,7 @@ Manual assignment can be done by posting a comment on the PR with the text: * `r? @octocat` --- Assigns a specific user. * `r? octocat` --- The `@` is optional. * `r? libs` --- Chooses a random person from the libs ad-hoc group defined in `triagebot.toml`. - For example, for the [rust-lang/rust] repository, see [`triagebot.toml`](https://github.com/rust-lang/rust/blob/master/triagebot.toml) for a list of ad-hoc group names. + For example, for the [rust-lang/rust](https://github.com/rust-lang/rust) repository, see [`triagebot.toml`](https://github.com/rust-lang/rust/blob/master/triagebot.toml) for a list of ad-hoc group names. * `r? rust-lang/libs` --- The `rust-lang/` org name prefix is optional. * `r? rustdoc` --- Chooses a random person from the rustdoc team. See the [teams database](https://github.com/rust-lang/team/tree/master/teams) for a list of team names.