Severity levels are not always accurately set when issues are first reported and may not have been updated since. Rule #1: The severity of an issue will be decided by the reviewers of a proposed patch. They are not set in stone and are open to revision over time. The following rules will guide how points are awarded from the initial launch of the reward system. That is why regressions are given top priority and critical/blocker/major issues aren’t far behind. The message that we are trying to send is that complexity is secondary to need.
There might be regressions that are trivial to solve, and enhancements that require an extremely complicated fix. Of course, the severity of an issue does not necessarily reflect the complexity of the solution. As such, issues are awarded points based on severity: The scoring is designed to reward contributors based on the importance of the issues they fix, rather than the total number fixed. We think this will be a fun way to reward our contributors, but we will pull the plug if it proves otherwise. Our members are generally friendly and helpful, and we don’t want to do anything that causes tension or proves negatively disruptive. We think we have one of the best online communities out there. There are some negative side effects that are possible with any sort of gamification system, and we’ll be keeping an eye out for them. If, as a side effect, the system motivates people to fix more bugs, that’s great! We won’t complain. The primary reasons: we see this as a means for the D Language Foundation to reward committed contributors and to channel their efforts towards more important bugs. I want to start by saying that the motivation of this system is not to start a fierce competition between contributors to fix as many issues as possible. This blog post covers all of the details regarding the implementation, rules, and prizes of the reward system. The current results can always be seen on the contributor stats page. Each GitHub user who fixes a bug via a merged pull request is awarded a number of points depending on the severity of the issue. It went live for testing on the 2nd of July. The Dlang bot has been updated to track Bugzilla issues
0 kommentar(er)
