Tracking issue for reorganizing labels in the rustfmt repo

[jieyouxu]

Context: #t-rustfmt > Triage labels. We should do a survey pass of open issues and PRs to assess current situation. This is the subtask of assessing and reorganizing what labels we have, to make triaging easier.

Warning

Work-in-progress, will be continuously updated.

Planned reorganizations

• Introduce a F-* (expected impact on formatting output and configuration) family of labels.
  • F-impacts-default-format-config Expected impact on formatting: affects default format configuration (caution)
  • F-impacts-stable-formatted-code Expected impact on formatting: affects stable + formatted code (caution)
  • F-impacts-stable-unformatted-code Expected impact on formatting: affects stable + unformatted code (caution)
  • F-impacts-unstable-code Expected impact on formatting: affects only unstable code
  • F-no-formatting-impact Expected impact on formatting: none or not applicable
  • F-untriaged-formatting-impact Expected impact on formatting: unclear, needs further triage
• Introduce a C-* ("category") family of labels (mirroring r-l/r) for categorizing issue kinds.
• Introduce a B-* ("blocked") family of labels to split https://github.com/rust-lang/rustfmt/labels/blocked more specific block reasons.
  • B-prerequisite-rustc-changes Blocked: needs prerequisite rustc changes
  • https://github.com/rust-lang/rustfmt/labels/B-has-concerns (FIXME: S-has-concerns)
  • https://github.com/rust-lang/rustfmt/labels/B-prerequisite-changes
  • https://github.com/rust-lang/rustfmt/labels/B-needs-style-edition-gate
  • B-t-style-decision Blocked: on style team decision(s)
• Introduce I-* ("indicator"/"important") family of labels (not intended to fully mirror r-l/r): I-lang-stabilization (for lang feature stabilizations), I-rustfmt-nominated (for rustfmt team discussion)
• Check if we can use S-waiting-on-{author,reviewer} binary label like r-l/r instead of pr-{not-reviewed,follow-up-review-pending} + s-waiting-on-author.
• Split pr-on-hold into more specific reasons. (Survey what the common reasons are first.)
• Mirror needs-rfc This issue/PR is controversial/complex enough to warrant an RFC approved before it can be accepted.

Planned cleanups

• Reassess current area A-* family of labels.

Other tasks

• Document label families as part of issue / PR triaging in Tracking issue for beefing up contribution docs #6686.
• Investigate how priorities are determined, and if P-* family of labels have different meanings for issues vs PRs.
• Investigate community driven Issues the rustfmt team will not work on directly. Intended for contributors! label.
• Investigate https://github.com/rust-lang/rustfmt/labels/help%20wanted label.

Remarks on current labels

Pending.