This document is a proposal for a Bug Hunting Week within the Bevy contributor community.
This proposal is currently put on hold. If you're interested in helping run this event, please reach out to BD103!
Bevy is largely volunteer-driven, meaning most changes are implemented because a developer wants them as compared to the engine needing them. While these views mostly overlap, certain categories of changes go underappreciated. (Mainly bug fixes, code quality, testing, and infrastructure.)
This event aims to encourage more bug fixes, shrink the ever-growing issue tracker, and increase engine stability.
In order to encourage contributors to participate, this event will be a competition with a public leaderboard. Competitors will earn points and can view their ranking online[1]. The top 3 developers with the most points will win bragging rights and Bevy merch[2]!
To score a points a contestant must open and successfully merge a pull request that closes an issue labeled C-Bug
. For this PR to qualify, it must:
C-Bug
that does not also have S-Needs-Triage
.bevyengine/bevy
repository.M-Bug-Hunt-Accepted
label by a member of the triage team to signal that it follows the above qualifications.main
branch. (There will be a window of time after the event officially ends where this can still be merged, before the final winner is announced, in order to give more time to the maintainers.)Each merged pull request is worth 3 points, which will be reflected on the leaderboard.
In addition to fixing bugs, contestants can also earn points by reviewing other pull requests. In order for the review to qualify, it must:
M-Bug-Hunt-Accepted
.S-Ready-For-Final-Review
label is applied or the PR receives two approvals.bevyengine/bevy
repository.main
branch. (See comment above on the extended window of time.)Each review is worth 1 point, which will be reflected on the leaderboard.
Note
Because reviews only count if the pull request is merged, reviewers are encouraged to help the PR author work through suggestions and polish off their changes. Both will benefit from doing so!
D-Complex
or related tags, especially if you specialize in a specific area of the engine. Those could be bugs that only you are qualified to fix, and will have far less competition than D-Trivial
bugs.S-Adopt-Me
.
Likely through a website hosted by TheBevyFlock
or the bevyengine
organization. ↩︎
Unfortunately I can't guarantee this, since I personally own no Bevy merch. (My Bevy socks
cart
generously relinquishes some from his private stores. As such, the larger prize is light-hearted fun and fame. ↩︎
So why must the issue author and PR author be different? Wouldn't the person who opened the issue be best equipped to fix it? While that is true, it could end up in competitors opening and immediately fixing their own bugs. Instead, contributors are encouraged to work together in sharing and fixing bugs. ↩︎