Add S-Nominated-To-Close to the contributor's guide #1938
Labels
A-Contributing-Guide
C-Content
S-Ready-For-Implementation
The core questions are answered: just add code
X-Blessed
Has a large architectural impact or tradeoffs, but the design has been endorsed by decision makers
The core idea here is that PR backlogs are unwieldy, and community members / triage team members should feel empowered to close out / say no to things that are stale, obsolete or a questionable idea. Historically, while they've had the power to simply close PRs / issues, the triage team has been reluctant to do so.
Main points to hit are:
This label has already been added to the main Bevy repo :)
The text was updated successfully, but these errors were encountered: