Point ranking system for developers / triagers




17 years ago
5 years ago


(Reporter: Brian 'netdragon' Bober, Assigned: Nobody's working on this, feel free to take it)






17 years ago
Mozilla 1.0 is coming, and we need more help. I thought of a neat incentive for 
developers/triagers, when I was looking at the old bugathon page. Let's give 
them some recognition! It would be an award system in Mozilla for developers 
and bug triagers.

Basically, it would work like this:

There would be three new fields added to show_bug.cgi:

Rating:  ______
| Patchers:______ |
| Triagers:______ |
The patchers and triagers field could be filled by anyone with bug-altering 
permissions, or by any patcher or triager with a certain ranking.

You should add someone to either patchers or triagers if you believe that they 
have done a significant portion of the work for the bug.


Must have permission.

This is no place to argue. Really, the owner or QA should be the only one 
filling these out unless the owner/QA is too tied up or hasn't done anything 
with the bug. The owner, module owner (if he/she doesn't own the bug) and QA 
automatically get a small amount of points just for owning/QAing a bug. If 
someone feels that they have gone above the call of duty, fixed the bug, etc, 
then they can be added to the list by someone other than themselves.

You cannot add yourself!!!


Small bugs - Maybe only a statement of "Thie belongs in Bugscape" would do.
Large bugs - There might be tons of people added to the list. Anyone who seems 
to have put a lot of effort (more than most) into this bug should be put on the 
list. Inluded are people who changed status and test case makers.


Small bugs - Usually who provided the code and patch. 
Large bugs - Many people - includes the person who put it on CVS, patcher, 
reviewers, people who came up with the ideas of what needs to be fixed, and 
technical guiders. Use your judgement.

There is a limit of 8 people per field.

Any squabbles over who should be added to be settled by QA and owner/module 
owner. The owner/QA and module owner can lock the two contributor's fields so 
no one else can change it except the QA module owner and owner if they think 
its getting out of hand.

Anyone who has contributed a reasonable amount of useful comments can be added

People blatantly adding things to a bug in order to get put on the list should 
be ignored and possibly warned.

The rating could be filled out by ANYONE WHO HAS BUGZILLA ACCESS. It is for a 
number from 1-5 based on a two teir system.

1: Severity
2: Difficulty to fix

If a bug is both difficult and severe, it should get a 4. If it is just 
difficult or just severe, it might get a 2-4. If it is just a wimpy little bug, 
it should get a 1. The current average will be placed next to the field.

Scoring per bug:

based on average rating (which is an integer btw that can't be less than 1).

Each person in the field would be given the average rating.

Owners, QA, and module owners all get 2 points (sometimes in addition to their 
listing score) per bug for triaging fields automatically.

Bonus (3) points are added to each of the listed people if the bug is marked 
mostfeq, or have a certain number of votes

Bonus (2) points for certain keywords such as dogfood, catfood, hang, dataloss 
or if a bug is marked blocker

Bonus (1) point is added to the listed people if the bug is an enhancement bug 
or has the keywords perf or polish.

Each bug has a page (cgi) to show who got what points and what each person 
ranked the bug. A QA or owner can override a person's ranking if they have due 
cause to believe that person is trying to rig the system. If it is overrided, 
then it is the same as if the person never ranked the bug.

A person who is abusing the ranking system can have their ranking abilities 
turned off.

The Bugzilla Recognition Page:

There will be two top-20 lists sorted by points on the front page. There will 
also be a search util to find info about a certain person on bugzilla (i.e. 
what ranks they are).

Rankings will be one of these (change the names if you like):

Triaging ranks:
Newbie >= 25 points
Flyswatter >= 50 points
Bugzapper >= 125 points
Anteater >= 450 points
Exterminator >= 900 points

Developing ranks:
Newbie >= 10 points
Coder >= 25 points
XPWizard >= 75 points
Hacker >= 200 points
Goatmaster >= 500 points

People with at least a newbie ranking can also add a link to their personal 
home page.

There will be a list of the last 20 people to attain a new rank and what rank 
they attained.

Comment 1

17 years ago
Hey, who am I to comment, but mozilla aint a game is it? Did you see the
about:credits page? And don't go look for my name on it because i'm not on that
list :)
Target Milestone: --- → Future
I prefer Pong.
-> Bugzilla product
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Version: Bugzilla 2.13 → 2.13
Reassigning all of my "future" targetted bugs to indicate that I'm not presently
working on them, and someone else could feel free to work on them. (sorry for
the spam if you got this twice, it didn't take right the first time)
Assignee: justdave → nobody

Comment 5

15 years ago
don't think any QA has time playing this game. suggest wontfix
Summary: [RFE] Award system for developers / triagers → Point ranking system for developers / triagers

Comment 6

15 years ago
After thinking long and hard, I see a point system as a possible liability for
the project. For instance, Boris Zbarsky has just recently gone as far to say
that I have done absolutely nothing for the project on Mozillazine. Since this
is not true, and there are some Mozilla developers and triagers getting into a
bit of unhealthy politics and battles, I think that this would be a system that
might be abused.
Last Resolved: 15 years ago
Resolution: --- → WONTFIX

Comment 7

15 years ago
I guess since its my bug, I can verify it wontfix.
clearing target on INVALID/WORKSFORME/WONTFIX/DUPLICATE so they'll show up as
untriaged if they get reopened.
Target Milestone: Future → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.