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

Reorganize issue labels #13164

Merged
merged 9 commits into from
May 2, 2024
Merged

Conversation

alice-i-cecile
Copy link
Member

Objective

The existing labels are inadequate for keeping track of the state of work at a glance. They're also inadequate for finding work that's at an appropriate difficulty level to either implement or review.

Solution

  • Add a complete set of difficulty labels
  • Move S-Controversial into its own category
  • Adding a complete set of controversiality labels, adding X-Uncontroversial and X-Contentious
  • Add a complete set of status labels: adding S-Needs-Testing, S-Needs-Review and S-Waiting-On-Author
  • Update CONTRIBUTING.md to reflect the new scheme

@alice-i-cecile alice-i-cecile added C-Usability A simple quality-of-life change that makes Bevy easier to use A-Meta About the project itself labels May 1, 2024
CONTRIBUTING.md Outdated Show resolved Hide resolved
Copy link
Contributor

@cBournhonesque cBournhonesque left a comment

Choose a reason for hiding this comment

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

I really like this!
Should we still keep D-Good-First-Issue? Isn't it a special label from github to help users discover issues?

@alice-i-cecile
Copy link
Member Author

alice-i-cecile commented May 1, 2024

I really like this! Should we still keep D-Good-First-Issue? Isn't it a special label from github to help users discover issues?

good first issue is: we're already breaking convention so it doesn't work. IIRC Hacktoberfest allows us to specify our own label instead. I think that being able to unify this across issues and PRs is valuable enough to swap away.

CONTRIBUTING.md Outdated Show resolved Hide resolved
@BD103
Copy link
Member

BD103 commented May 2, 2024

  • Adding a complete set of controversiality labels, adding X-Uncontroversial and X-Contentious

Could you add one more, X-Resolved? This could be used to specify a previously controversial PR / issue that either Cart made a final decision on or the community came to a consensus on.

Co-authored-by: Joona Aalto <jondolf.dev@gmail.com>
CONTRIBUTING.md Outdated Show resolved Hide resolved

The rules for how PRs get merged depend on their classification by controversy and difficulty.
More difficult PRs will require more careful review from experts,
while more controversial PRs will require rewrites to reduce the costs involved and/or sign-off from Subject Matter Experts and Maintainers.
Copy link
Member

Choose a reason for hiding this comment

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

Nit: Should we link to the SME page?

Copy link
Member Author

Choose a reason for hiding this comment

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

I think that's not worth it here. When we split this out into a proper book I'll do a pass on cross-linking though.

CONTRIBUTING.md Outdated Show resolved Hide resolved
@alice-i-cecile
Copy link
Member Author

@BD103 I've added your suggestion in the form of X-Blessed: I think that's clearer in the cases where there's an endorsed design doc or RFC that we're working off of.

@alice-i-cecile alice-i-cecile added the S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it label May 2, 2024
@alice-i-cecile
Copy link
Member Author

We have no objections from the other maintainers and a broad sign off from @cart, so I'm going to merge this now and start tweaking the labels to match.

@alice-i-cecile alice-i-cecile added this pull request to the merge queue May 2, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 2, 2024
@alice-i-cecile alice-i-cecile added this pull request to the merge queue May 2, 2024
@alice-i-cecile alice-i-cecile removed this pull request from the merge queue due to a manual request May 2, 2024
@BD103
Copy link
Member

BD103 commented May 2, 2024

I think CI is failing because Rust 1.78 just got released, stabilizing a new lint. I'll make a quick PR fixing this.

Edit: Alice beat me to it :P

@BD103 BD103 mentioned this pull request May 2, 2024
@alice-i-cecile alice-i-cecile added this pull request to the merge queue May 2, 2024
Merged via the queue into bevyengine:main with commit ff8a9b2 May 2, 2024
28 checks passed
@mockersf
Copy link
Member

mockersf commented May 6, 2024

this removed the "good first issue" label, which is a standard and something GitHub trains people to search for. it was already a downgraded experience because we used "D-Good-First-Issue", but at least it was matching when people were searching for the label

@alice-i-cecile
Copy link
Member Author

Perhaps we can swap to D-Good-First-Contribution?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Meta About the project itself C-Usability A simple quality-of-life change that makes Bevy easier to use S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

7 participants