logo zerocracy

You can get a similar report for your project

This week
⬇
Programmer / Award Reasonw17w18w19w20w21w22w23w24RunPay
@fruxxxl@fruxxxl (11 awards)—+90+96+18—+20——+224
@vasilevnstas@vasilevnstas (70 awards)——————+754+164+918
@belfil@belfil (2 awards)—+44——————+44
@roman-shaposhnikov@roman-shaposhnikov (2 awards)———+44————+44
@mseheda@mseheda (6 awards)———+92————+92
@akmhatey-ai@akmhatey-ai (25 awards)—————+231+60—+291
@puneetdixit200@puneetdixit200 (1 award)—————+20——+20
@ketpatil77@ketpatil77 (1 award)———————+20+20
@morphqdd@morphqdd (42 awards)+18+296+92+283—+54——+743
@kreinba@kreinba (111 awards)———+108+519+564+468+59+1718
@edmoffo@edmoffo (127 awards)———+36+546+673+542+116+1913
@yegor256@yegor256 (233 awards)+30+246+86+159+120+66+38-40+825-6450
@yegorov@yegorov (2 awards)—+8——————+81116
@bibonix@bibonix (101 awards)-6+224+38+72+376+374+281—+1359
@igor-belousov@igor-belousov (14 awards)—+98—+114————+212
@vitaly-andr@vitaly-andr (19 awards)—+60—+36————+96
@nacnac333@nacnac333 (10 awards)——-30+44+24+44——+82
@ghx5t-sol@ghx5t-sol (91 awards)———-12+24+990+122+76+1200
@say-5@say-5 (3 awards)————-12+20——+8
@thehanslevi@thehanslevi (2 awards)————+14———+14
@resolvicomai@resolvicomai (4 awards)————+36———+36
@will-thom@will-thom (2 awards)————-12———-12
@ajthespidey@ajthespidey (1 award)—————-6——-6
@imedfan@imedfan (2 awards)—————-6+20—+14
@yegorov0725@yegorov0725 (3 awards)+24—+20—————+36
Total (885/2583):+66+1066+302+994+1635+3044+2285+395+9899

Assessment

The average reward per task (13.6 points) is staying still. The average punishment per task (7.0 points) is decreasing (R=-0.31). The average number of builds per week (2760.4) is increasing (R=0.23). The average number of commits per week (89.8) is increasing (R=0.12). The average bugs accepted per month (31.0) is increasing (R=0.65). The average monthly punishment (259 points) is decreasing (R=-0.10). The average monthly wage (16.9 points) is staying still. The average issue cycle time (1w4d) is staying still. The average pull cycle time (3d10h) is staying still. The average quality of service (77%) is decreasing (R=-0.17). The average number of releases per month (6.6) is decreasing (R=-0.45). The average monthly turnover (11.0 developers) is increasing (R=0.29). The average weekly cost of HoC (1.92 points) is decreasing (R=-0.25). The average monthly zents/points ratio (0.69) is decreasing (R=0.48).

Assessment

The average reward per task (13.6 points) is increasing (R=0.11). The average punishment per task (7.0 points) is decreasing (R=-0.30). The average number of builds per week (2883.3) is increasing (R=0.39). The average number of commits per week (90.2) is increasing (R=0.12). The average bugs accepted per month (31.0) is increasing (R=0.65). The average monthly punishment (262 points) is staying still. The average monthly wage (16.9 points) is decreasing (R=0.16). The average issue cycle time (1w4d) is staying still. The average pull cycle time (3d10h) is staying still. The average quality of service (77%) is decreasing (R=-0.17). The average number of releases per month (6.3) is decreasing (R=-0.48). The average monthly turnover (11.0 developers) is increasing (R=0.26). The average weekly cost of HoC (1.90 points) is decreasing (R=-0.26). The average monthly zents/points ratio (0.70) is decreasing (R=0.39).

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: 24740, EV: 41879, PV: 31854, CPI: +1.69, SPI: +1.31.

Dimensions of Terrain (DoT)

Dimensionw17w18w19w20w21w22w23w24
total_active_contributors712121521232222
total_commits2059420823209322102221789219482204822094
total_contributors3236363946505152
total_files30743088310931363204321232193220
total_forks82949789111132147149
total_issues18711905192119492005206521942196
total_pulls49045000505050965190532255145553
total_releases856859860860860861861861
total_repositories1717171819191919
total_stars133140142141141141141141