If a branch has a name that doesn\'t obey the convention, a penalty is given to the author. Here is how it's calculated: Just deduct -12 points.

When a bug is reported and accepted by the team, the reporter gets a bonus. Here is how it's calculated: Just award 8 points.

When a code contribution is made, the author gets a bonus. Here is how it's calculated: First, assume that hoc is the total number of hits-of-code in the contribution. Then, assume that comments is the total number of comments made by all reviewers. Then, assume that reviews is the number of reviews provided, and award 4 points. Then, add 0.05 points for each hit-of-code, but not more than 16 points. Then, deduct 8 points if more than 200 hits-of-code. Then, deduct 16 points if more than 800 hits-of-code. Then, deduct 16 points if there were no code review. Then, deduct 0.2 points for every comment made during review, but not more than -16 points. Then, deduct 4 points if there were less than 6 comments made during review. Then, deduct 16 points if there were absolutely no comments made by reviewers during the review. Then, deduct 8 points if you contribute less than 20 hits-of-code. Then, make sure the reward is not larger than 24 points and not smaller than 4 points.

An author of every code review gets a bonus. Here is how it's calculated: First, assume that hoc is the total number of hits-of-code in the contribution. Then, assume that comments is the total number of comments made by all reviewers. Then, assume that self is 1 if the review was made for their own code contribution, otherwise zero, and award 4 points. Then, deduct 24 points if they reviewed their own contribution. Then, add 0.01 points for each hit-of-code, but not more than 16 points. Then, deduct 10 points if there were less than 6 comments made during review. Then, deduct 16 points if there were absolutely no comments made during review. Then, add 0.25 points for each comment during the review, but not more than 8 points. Then, deduct 8 points if there were less than 16 hits-of-code. Then, make sure the reward is not larger than 24 points and not smaller than 4 points.

When an issue is submitted but then rejected by the team, the reporter gets a penalty. Here is how it's calculated: Just deduct -16 points.

When an enhancement is suggested and accepted by the team, the reporter gets a bonus. Here is how it's calculated: Just award 8 points.

When a new release is published, everybody who contributed gets a bonus. Here is how it's calculated: First, assume that hoc is how many hits-of-code are in the release. Then, assume that contributors is how many people contributed to the release, and award 24 points. Then, add 0.01 points for each hit-of-code, but not more than 24 points. Then, make sure the reward is not larger than 32 points and not smaller than 4 points.

When someone pushes directly to the default branch, they get a penalty. Here is how it's calculated: Just -16 points.

When a bug is resolved, the person who was assigned to it gets a bonus. Here is how it's calculated: First, assume that hours is how many hours it took to resolve the bug. Then, assume that self is 1 if the bug was reported and resolved by the same person, otherwise zero. Then, set days to hours ÷ 24, and award 4 points. Then, add 4 points if it was resolved in less than 24 hours. Then, deduct 16 points if they resolved the bug earlier reported by themselves. Then, deduct 1.0 points for each day of delay, but no more than -20 points. Then, make sure the reward is not larger than 16 points and not smaller than 4 points.