Re: Bugzilla Reward System
On 9/16/21 4:56 AM, Mike Parker wrote: > This was Razvan Nitu's baby from conception to implementation Thank you, Razvan! Great job and a great article. What I missed in the article is whether we are going to reward all contributors or whether certain people like Walter are excused? :) Also, if a regression is best fixed by the person who caused it in the first place, regressions may become a good thing. ;) Ali
Re: Bugzilla Reward System
On Thursday, 16 September 2021 at 14:35:08 UTC, Paul Backus wrote: In my experience, the only severity settings most people actually use when filing issues on Bugzilla are "enhancement", "normal", and "regression". And when people do use the other settings, there's no consistency to how they get applied. For example, the first two search results for priority "blocker", issues [22283][] and [22148][], have no indication of what (if anything) they block. Meanwhile, issues [14196][] and [13983][] are both enhancement requests but have their priority set to "major", and issue [22136][] is listed as "critical" even though it is actually a regression! Yes of course. Rule #1: Severity levels are not always accurately set when issues are first reported and may not have been updated since. The reviewer of a pull request that closes a Bugzilla issue will evaluate the issue’s severity level and may change it if he or she determines it is inaccurate. I will moderate any disagreements that may arise about severity levels. Obviously, this isn't perfect, but it's the best we've got for the moment. I expect there will be quite a few kinks to work out as time goes by. The initial trial run will surely provide us with lessons we can apply going forward, and we will continue to refine the process as needed. I don't blame anyone who files reports like these. The fact is, there is no official guidance anywhere about what distinguishes a "minor" issue from a "normal" one, or a "normal" issue from a "major" one, so people just guess. But treating the output of this guessing process as though it were meaningful data is probably a mistake. They aren't meaningful because there has been no organized process to make them meaningful. Part of Razvan's job description is to oversee the Bugzilla issues, and this initiative is a product of that. But he's one man, and the issues are legion :-) I predict we'll see the publication of reviewer guidelines down the road, and will eventually ask for a handful of people to assist Razvan in making sure Bugzilla issues have roughly accurate severity levels before a PR is submitted. Those are the most obvious steps I see to improving accuracy.
Re: Bugzilla Reward System
On Thursday, 16 September 2021 at 11:56:21 UTC, Mike Parker wrote: In my summary of last month's D Language Foundation meeting, I mentioned that we discussed a system intended to reward contributors who contribute pull requests that fix Bugzilla issues. This was Razvan Nitu's baby from conception to implementation, and we all think it is a great idea. The system has been running in the background for a few weeks now, quietly gathering data and awarding points, proving that the programming side works as intended. Our first round of point scoring kicks off on September 20th. Razvan has put together a blog post explaining how the system works. We'll revise and adapt the system as needed as time goes by. In the meantime, happy bug fixing! The blog: https://dlang.org/blog/2021/09/16/bugzilla-reward-system/ Reddit: https://www.reddit.com/r/d_language/comments/ppbp7d/bugzilla_reward_system/ This is a good move, I hope it will work so that D will keep contributors that are not already gone and gain new talented ones. Another answer mentions that the lack of "issue triage" might cause problems. I think to the opposite that this system could encourage 1. better triage 2. better reviews But well, we'll see if this works next year. Let's not be negative ;)
Re: Bugzilla Reward System
On Thursday, 16 September 2021 at 11:56:21 UTC, Mike Parker wrote: ... We'll revise and adapt the system as needed as time goes by. In the meantime, happy bug fixing! The blog: https://dlang.org/blog/2021/09/16/bugzilla-reward-system/ ... Nice idea to reward contributors. Happy to see that you just try and see how it works, and adjust if needed. I think the overall positive synergy of the community is important, and this initiative should not damage it. To achieve this, I would suggest to consider giving more than 3 prizes each evaluation period. Furthermore, I would suggest to think about rewarding "rookies" as well... But let's first see how this works.
Re: Bugzilla Reward System
On Thursday, 16 September 2021 at 11:56:21 UTC, Mike Parker wrote: https://dlang.org/blog/2021/09/16/bugzilla-reward-system/ From the post: The scoring is designed to reward contributors based on the importance of the issues they fix, rather than the total number fixed. As such, issues are awarded points based on severity: In my experience, the only severity settings most people actually use when filing issues on Bugzilla are "enhancement", "normal", and "regression". And when people do use the other settings, there's no consistency to how they get applied. For example, the first two search results for priority "blocker", issues [22283][] and [22148][], have no indication of what (if anything) they block. Meanwhile, issues [14196][] and [13983][] are both enhancement requests but have their priority set to "major", and issue [22136][] is listed as "critical" even though it is actually a regression! I don't blame anyone who files reports like these. The fact is, there is no official guidance anywhere about what distinguishes a "minor" issue from a "normal" one, or a "normal" issue from a "major" one, so people just guess. But treating the output of this guessing process as though it were meaningful data is probably a mistake. [22283]: https://issues.dlang.org/show_bug.cgi?id=22283 [22148]: https://issues.dlang.org/show_bug.cgi?id=22148 [14196]: https://issues.dlang.org/show_bug.cgi?id=14196 [13983]: https://issues.dlang.org/show_bug.cgi?id=13983 [22136]: https://issues.dlang.org/show_bug.cgi?id=22136
Re: Bugzilla Reward System
On 16.09.21 13:56, Mike Parker wrote: The blog: https://dlang.org/blog/2021/09/16/bugzilla-reward-system/ From there: Rule #2: A PR fixing a bug may not be merged by the same person that proposed the patch. This is already an unwritten rule that applies to the DLang repositories, so it should not surprise anyone. Someone tell Walter about that unwritten rule. He regularly merges his own PRs.
Bugzilla Reward System
In my summary of last month's D Language Foundation meeting, I mentioned that we discussed a system intended to reward contributors who contribute pull requests that fix Bugzilla issues. This was Razvan Nitu's baby from conception to implementation, and we all think it is a great idea. The system has been running in the background for a few weeks now, quietly gathering data and awarding points, proving that the programming side works as intended. Our first round of point scoring kicks off on September 20th. Razvan has put together a blog post explaining how the system works. We'll revise and adapt the system as needed as time goes by. In the meantime, happy bug fixing! The blog: https://dlang.org/blog/2021/09/16/bugzilla-reward-system/ Reddit: https://www.reddit.com/r/d_language/comments/ppbp7d/bugzilla_reward_system/
