Commit Graph

78 Commits

Author SHA1 Message Date
Jakub Beránek 77735079cc
Add run-make port initiative to the Recurring work section (#1992) 2024-06-09 09:57:13 +01:00
Jakub Beránek 6f60d12b01 Add note about how to pick up abandoned PRs 2024-05-15 19:59:36 +02:00
Emanuel Czirai e5c5fc3a13 typo traige->triage 2024-04-28 20:31:21 +02:00
Yuki Okushi 3329715501
Fix some links (#1865) 2024-01-28 19:44:41 -03:00
Santiago Pastorino 2d11bd67d4 Replace experts map with reviewers from triagebot 2023-12-05 18:40:26 +02:00
Aneesh 4d43a3b780 emphasize that the experts map is not up to date 2023-11-22 08:13:00 +02:00
zahash 1f77525b1b move placement of std-dev-guide link (#1699) 2023-08-29 10:45:38 +02:00
zahash 6ec5335b07 link std-dev-guide from landing page (#1699) 2023-08-29 10:45:38 +02:00
İsmail Arılık c7d6710791
Fix a bug in getting-started.md (#1726) 2023-07-09 19:22:22 +09:00
jyn 7267158f9d include rustc-dev-guide's own issues in suggested search 2023-06-29 18:21:18 +02:00
jyn ee5285347d
filter out S-blocked issues in the "Getting Started" search (#1687) 2023-05-15 05:24:31 +09:00
Ohad Ravid 0ff2326425 Fix extra slash 2023-04-16 13:30:24 +02:00
Joshua Nelson 516194c5e8 Link to governance page
It has links to the specific channel/stream for each team.
2023-04-09 22:38:15 +02:00
jyn 8bf09013c0 Apply suggestions from code review
Thank you JohnTitor for finding these!

Co-authored-by: Yuki Okushi <jtitor@2k36.org>
2023-04-09 22:38:15 +02:00
jyn 177ca5e602 Add a "What should I work on?" section
This is the first question I get from nearly all contributors. So far
I've been giving links to individual issues, but they quickly go out of
date or get fixed, and then I have more work to do to help people find
an issue. Add some suggestions for work people can find themselves,
without having to first consult an expert.

This also moves the "Cloning and Building" stub to the bottom of the
page.
2023-04-09 22:38:15 +02:00
jyn 2d2ef1329a Make the "Asking Questions" section more useful
- Update outdated chat platforms
- Link to the community page
- Suggest `git shortlog` for finding experts
2023-04-09 22:38:15 +02:00
Joshua Nelson 2ff743c00b Rearrange the "getting started" and contributing.md sections
There was a lot of information duplicated between the two, and it wasn't
clear which one to look. This commit changes `contributing.md` to be
strictly for contribution procedures, and moves "what should I work on"
sections to "Getting Started".

This also consolidates the links in `about-this-guide.md` rather than
spreading them between about-this-guide, getting-started, and
contributing.

I suggest using https://rustc-dev-guide.org/git.html#moving-large-sections-of-code to review this commit.
2023-04-03 06:42:31 -05:00
Joshua Nelson 33c6ea1e8c Move some info from "Getting Started" to "How to build and run"
"Getting Started" is already *very* long; this shrinks it a bit, and
puts similar info closer together.
2023-04-03 06:42:31 -05:00
Tshepang Mbambo 64f1af18f5 lower-case "Compiler" in headings, for consistency (and looks) 2023-02-18 05:04:44 +02:00
ozkanonur 472188e1b9 extend bootstrap related documentations
Signed-off-by: ozkanonur <work@onurozkan.dev>
2023-01-31 12:42:30 -06:00
Eric Huss 7f426da358 Update for highfive transition. 2022-10-27 06:07:59 +02:00
pierwill 5e38eb64bf
Link to The Rust Performance Book (#1300) 2022-02-17 17:46:20 -03:00
Nicholas Nethercote acc6718c51 Address review comments in #1286. 2022-01-05 23:26:43 -06:00
Nicholas Nethercote a992723654 Streamline "Getting Started" some more.
This is a follow-up to #1279.

The "Getting Started" chapter is, TBH, pretty bad when it comes to the
stuff about building and testing. It has far too much detail and lots of
repetition, which would be overwhelming to a newcomer.

This commit removes most of it, leaving behind just quick mentions of
the most common `x.py` commands: `check`, `build`, `test`, `fmt`, with
links to the appropriate chapters for details. There were a few
interesting details that weren't covered elsewhere, so I moved those
into other chapters.
2022-01-05 23:26:43 -06:00
Nicholas Nethercote a11e5f4e15
Streamline "Getting Started" (#1279)
* Move `x.py` intro section before first use, and shorten it.

* Improve `x.py setup` docs.

In "Getting Started", strip it back to the bare minimum. Some of this is
moved into the later section.

In the later section, add notable details like config.toml.example how
and `profile` works. Also make the config.toml example more concise.

* Move details about the repository.

Less detail in "Getting Started", more in the later sections.

* Move details about the prereqs.

Less detail in "Getting Started", more in the later sections.
2021-12-24 12:52:31 -03:00
Lucas Kent 0c0e4f2e44 Update src/getting-started.md
Co-authored-by: Joshua Nelson <github@jyn.dev>
2021-12-09 09:09:36 -06:00
Lucas Kent 3df5cc9fe5 Improve documentation on r? 2021-12-09 09:09:36 -06:00
Ken Matsui 24132faa13
Unify `x.py` usage (#1258) 2021-11-16 07:44:50 +09:00
Noah Lev ceec906a31 Recommend `rustfmt --edition=2021` 2021-10-10 08:28:12 -05:00
Oli Scherer 013c8892dd Move log/tracing instructions to its own file 2021-10-08 15:41:06 -05:00
Frank Steffahn 60ef9da723 Suggests `--edition=2018` argument when using stage0/bin/rustfmt directly 2021-09-17 14:53:44 -05:00
Camelid 1f68820307 Document how to enable CI LLVM without using `x.py setup` 2021-02-26 15:38:01 -05:00
Camelid 761f92f390 Remove some unrelated changes 2021-02-26 15:38:01 -05:00
Camelid b932cf20cf Fix typos 2021-02-26 15:38:01 -05:00
Camelid 07b5693a90 Update some out-of-date information 2021-02-26 15:38:01 -05:00
Daniel Santos 033a1ea771 Fixes typo in getting started guide 2021-02-24 21:20:36 -05:00
Iñaki Garay bee2fd52ce
Add mdbook-toc, markers, and documentation (#1028)
* Add mdbook-toc to travis, book.toml  and documentation

* Add toc markers

* Whitespace cleanup and some punctuation

* Addressed comments
2021-01-20 14:33:11 -03:00
ashosive 93fcae6322 improved the readablity of a line 2021-01-16 12:04:07 -05:00
saki-osive c87ef62351 Fixed a grammatical error in hardawre requirements section 2021-01-16 10:03:23 -05:00
Ryan Levick 11b83ebb5a Add link to rust-analyzer docs on getting started page 2021-01-04 10:09:49 -05:00
Yuki Okushi 47893bacd8
Add reference PRs for `r?` and `r+` comments (#928) 2020-10-21 23:53:32 +02:00
Yuki Okushi 97eebb9adb Replace links to `buildbot2.r-l.o` with `bors.r-l.o` 2020-10-21 17:34:07 -04:00
Stu e912d1904b Fix broken "system LLVM" link 2020-10-08 11:47:32 -04:00
LeSeulArtichaut 47ce12a4c8 Fix time periods for Triage WG procedure 2020-10-03 19:25:05 -05:00
Tshepang Lekhonkhobe f833b8bcdf Update src/getting-started.md
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
2020-10-03 19:25:05 -05:00
Tshepang Lekhonkhobe 080b0c8aad Update src/getting-started.md
Co-authored-by: Camelid <37223377+camelid@users.noreply.github.com>
2020-10-03 19:25:05 -05:00
LeSeulArtichaut 3d6d0e04ed Add a paragraph about reviewers and review latency in Getting Started chapter 2020-10-03 19:25:05 -05:00
Roman fdd5946d58 add the last missing code highlight to t-compiler in the docs 2020-10-02 12:37:27 +02:00
Joshua Nelson 5f39b8131f Add docs for x.py setup 2020-09-27 04:24:18 +02:00
follower ea7ee3a503 Add link from "Writing Documentation" suggestion
A link to the relevant section of the contributing documentation makes it easier for contributors to locate the relevant information. (e.g. via an in-page search for "doc".)

This is particularly important currently as 85072e3303/CONTRIBUTING.md links directly to the (currently `rustc`-focused) "Getting Started" guide rather than the general Rust contribution content to which it used to point.
2020-09-26 11:52:14 -04:00