Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create chapter about rust-lang/rust issue triaging #716

Merged
merged 2 commits into from
Dec 26, 2023

Conversation

Nilstrieb
Copy link
Member

This explains some of the existing processes around triage, and how I do it. If you have different opinions, please leave them here (though it would be nice for this not to drown in bikeshedding :3)

Some people that come to my mind here (that I remember being involved in discussions or that I see doing triage in the wild):
@saethlin @Enselic @kpreid @jackh726 @pnkfelix @apiraino @matthiaskrgr @aDotInTheVoid

some discussion:
https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/Removing.20.60needs-triage.60
https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/needs-triage.20update
https://rust-lang.zulipchat.com/#narrow/stream/242269-t-release.2Ftriage/topic/E-needs-repro
https://rust-lang.zulipchat.com/#narrow/stream/122651-general/topic/Clarifying.20E-needs-mcve

This explains some of the existing processes around triage, and how I do
it.
@rustbot
Copy link
Collaborator

rustbot commented Dec 24, 2023

r? @Mark-Simulacrum

(rustbot has picked a reviewer for you, use r? to override)

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Dec 24, 2023
src/release/issue-triaging.md Show resolved Hide resolved
src/release/issue-triaging.md Show resolved Hide resolved
src/release/issue-triaging.md Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
src/release/issue-triaging.md Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
@Nilstrieb
Copy link
Member Author

I just saw #463 and one part I like there is the part about redirecting feature requests, I'll also add a note about that here.

src/SUMMARY.md Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
src/release/issue-triaging.md Outdated Show resolved Hide resolved
Copy link
Member

@jackh726 jackh726 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some good comments here. I think we should get the obvious and easy ones applied, then merge this. We can Iterate after.

src/release/issue-triaging.md Outdated Show resolved Hide resolved
src/release/issue-triaging.md Show resolved Hide resolved
@Nilstrieb
Copy link
Member Author

I addressed the simple feedback and created an issue for the remaining questions.

@jackh726
Copy link
Member

jackh726 commented Dec 26, 2023

Realizing that technically maybe someone from t-release (or wg-triage) should merge (since that's where this chapter is) but I'm going to error on the side of "this is useful and reversible, and better to have than delay on technicalities" and merge.

@jackh726 jackh726 merged commit b144add into rust-lang:master Dec 26, 2023
1 check passed
@Nilstrieb Nilstrieb deleted the how-do-i-triage-issues branch December 26, 2023 15:21
It's okay if not all of these are always considered; treat it as a guideline, not a hard checklist. It is also not exhaustive.

- 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd probably explicitate the links (adding the references)

Suggested change
- For example, if an issue is a question about Rust in general, the issue should be closed and the user redirected to URLO/Discord.
- For example, if an issue is a question about Rust in general, the issue should be closed and the user redirected to [URLO] / [Discord] support forums.
[URLO]: https://users.rust-lang.org
[Discord]: https://discord.gg/rust-lang

- If the issue contains no reproduction but needs one, ask for one and add the `S-needs-repro` label
- The issue is the wrong place for some kinds of feature requests. Tell the author about it.
- Library API requests should follow [its processes](https://std-dev-guide.rust-lang.org/development/feature-lifecycle.html).
- Language changes should be redirected to [IRLO](https://internals.rust-lang.org/) or Zulip (t-lang).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Language changes should be redirected to [IRLO](https://internals.rust-lang.org/) or Zulip (t-lang).
- Language changes should be redirected to [IRLO](https://internals.rust-lang.org/) or Zulip ([t-lang](https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang)).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet