logo zerocracy

You can get a similar report for your project

This week
⬇
Programmer / Award Reasonw31w32w33w34w35w36w37w38RunPay
@palliep@palliep (1 award)—————+24——+24
@vasilevnstas@vasilevnstas (32 awards)—————+620+48—+668
@morphqdd@morphqdd (641 awards)—————+4954+3200+3690+11844
@ghx5t-sol@ghx5t-sol (1 award)—————+20——+20
@opusstudiohq-max@opusstudiohq-max (4 awards)——————+68+18+86
@sdghsdkjlas27-dotcom@sdghsdkjlas27-dotcom (18 awards)—————+324——+324
@maxonfjvipon@maxonfjvipon (1 award)—————+18——+18
@thayorns@thayorns (146 awards)—————+1870+162+698+2730
@agorlov@agorlov (1 award)—————+18——+18
@artur-intech@artur-intech (26 awards)—————+468——+468
@favixx@favixx (6 awards)—————+108——+108
@ext11n7@ext11n7 (3 awards)—————+58——+58
@gemshrine@gemshrine (256 awards)——————+2586+1928+4514
@twaldin@twaldin (3 awards)——————+58—+58
@yegor256@yegor256 (106 awards)-18+72+66+18+42+433+74+114+801-7363
@eugene-chernyshenko@eugene-chernyshenko (1 award)———————-6-6
@voyagerroc-lab@voyagerroc-lab (1 award)———————-6-6
Total (1247/3930):-18+72+66+18+42+8915+6196+6436+21727

Assessment

The average reward per task (16.0 points) is increasing (R=0.30). The average punishment per task (7.0 points) is staying still. The average number of builds per week (4778.4) is increasing (R=0.30). The average number of commits per week (89.4) is decreasing (R=-0.20). The average bugs accepted per month (126.0) is increasing (R=0.61). The average monthly punishment (269 points) is staying still. The average monthly wage (17.3 points) is increasing (R=0.36). The average issue cycle time (1w4d) is staying still. The average pull cycle time (1w1d) is increasing (R=0.16). The average number of releases per month (4.7) is staying still. The average monthly turnover (14.0 developers) is increasing (R=0.81). The average weekly cost of HoC (1.30 points) is decreasing (R=-0.39). The average monthly zents/points ratio (0.76) is decreasing (R=0.63).

Assessment

The average reward per task (16.0 points) is increasing (R=0.30). The average punishment per task (7.0 points) is staying still. The average number of builds per week (4778.4) is increasing (R=0.30). The average number of commits per week (89.4) is decreasing (R=-0.20). The average bugs accepted per month (128.0) is increasing (R=0.61). The average monthly punishment (269 points) is staying still. The average monthly wage (17.3 points) is increasing (R=0.36). The average issue cycle time (1w4d) is staying still. The average pull cycle time (1w1d) is increasing (R=0.16). The average number of releases per month (4.7) is staying still. The average monthly turnover (14.0 developers) is increasing (R=0.82). The average weekly cost of HoC (1.31 points) is decreasing (R=-0.40). The average monthly zents/points ratio (0.76) is decreasing (R=0.63).

Repositories where the work is happening

Bylaws

When a bug is resolved, the person who was assigned to it receives 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 12 points. Then, add 6 points if it was resolved in less than 16 hours. Then, deduct 8 points if they resolved the bug earlier reported by themselves. Then, deduct 0.5 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.

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

An author of every code review receives 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 18 points. Then, deduct 12 points if they reviewed their own contribution. Then, add 0.015 points for each hit-of-code, but not more than 16 points. Then, deduct 5 points if there were less than 9 comments made during review. Then, deduct 8 points if there were absolutely no comments made during review. Then, add 0.375 points for each comment during the review, but not more than 8 points. Then, deduct 4 points if there were less than 24 hits-of-code. Then, make sure the reward is not larger than 24 points and not smaller than 4 points.

When a code contribution is made, the author receives 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 24 points. Then, add 0.075 points for each hit-of-code, but not more than 16 points. Then, deduct 4 points if more than 133 hits-of-code. Then, deduct 8 points if more than 533 hits-of-code. Then, deduct 8 points if there were no code review. Then, deduct 0.1 points for every comment above 5 made during review, but not more than -16 points. Then, deduct 4 points if you contribute less than 30 hits-of-code. Then, make sure the reward is not larger than 24 points and not smaller than 4 points.

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

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 -6 points.

When a new release is published, everyone who contributed receives 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 36 points. Then, add 0.015 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 an enhancement is suggested and accepted by the team, the reporter receives a bonus. Here is how it's calculated: Just award 18 points.

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

Oversized pull requests get penalized. Here is how it's calculated: Just deduct -4 points.

Quality of Service (QoS)

Quantity of Deliverables (QoD)

Earned Value Analysis (EVA)

AC: 51183, EV: 155795, PV: 179548, CPI: +3.04, SPI: +0.87.

Dimensions of Terrain (DoT)

Dimensionw31w32w33w34w35w36w37w38
total_active_contributors138433101313
total_commits1705217064170771708817095173751748217529
total_contributors5555555655576060
total_files23702370237023702370240224232438
total_forks165165165166162166183191
total_issues21342137214521462146244928573161
total_pulls53285355536453785385567659686282
total_releases877877877877877878879879
total_repositories1818181818181818
total_stars141141141141141142142142