logo objectionary

You can get a similar report for your project

This week
⬇
Programmer / Award Reasonw20w21w22w23w24w25w26w27Run
@roman-shaposhnikov@roman-shaposhnikov (2 awards)—+16+16—————+32
@kreinba@kreinba (10 awards)—+16——+12+10+52+4+94
@asmirnov-backend@asmirnov-backend (11 awards)————+16+80+36+12+144
@bibonix@bibonix (16 awards)+80+12-2+32+20——-8+134
@sherenkov@sherenkov (10 awards)+64+40——————+104
@morphqdd@morphqdd (52 awards)+96-8+36—+29+52+36+344+585
@favixx@favixx (1 award)———+12————+12
@mrdarkside@mrdarkside (1 award)———+12————+12
@nacnac333@nacnac333 (1 award)———+12————+12
@thayorns@thayorns (31 awards)———+112+104—+102+48+366
@999axel999@999axel999 (2 awards)———+24————+24
@edmoffo@edmoffo (13 awards)———+24+40+6—+42+112
@gemshrine@gemshrine (1 award)—————+12——+12
@deyna256@deyna256 (1 award)—————+12——+12
@lesbass@lesbass (1 award)—————+12——+12
@andreychh@andreychh (2 awards)———————+24+24
@volodya-lombrozo@volodya-lombrozo (104 awards)+107+56+161+88+180+60+196+64+912
@maxonfjvipon@maxonfjvipon (114 awards)-1+20+4+96+76+50+206+182+633
@akmhatey-ai@akmhatey-ai (15 awards)——+36+36+8———+80
@ghx5t-sol@ghx5t-sol (20 awards)——+73+4+28———+105
@algojogacor@algojogacor (2 awards)+6———————+6
@stegruslan@stegruslan (1 award)-6———————-6
@say-5@say-5 (1 award)—-6——————-6
@nanookclaw@nanookclaw (2 awards)———+6————+6
@jah-yee@jah-yee (1 award)—————-6——-6
@circuito-suman@circuito-suman (1 award)——————-6—-6
@arnabnandy7@arnabnandy7 (2 awards)——————+6—+6
@mirletti@mirletti (5 awards)——————-24+12-12
@dragonfsky@dragonfsky (4 awards)——————-12+32+20
@yegor256@yegor256 (582 awards)+125+582+111+69+185+64+772+702+2610
@h1alexbel@h1alexbel (2 awards)————+4———+4
@ext11n7@ext11n7 (8 awards)———————+16+16
Total (1019/3086):+471+728+435+527+702+352+1364+1474+6053

Assessment

The average reward per task (8.1 points) is staying still. The average punishment per task (7.0 points) is decreasing (R=-0.29). The average number of builds per week (5123.9) is increasing (R=0.83). The average number of commits per week (142.0) is increasing (R=0.70). The average bugs accepted per month (16.0) is increasing (R=0.47). The average monthly punishment (295 points) is increasing (R=0.27). The average monthly wage (9.7 points) is increasing (R=0.76). The average issue cycle time (1w) is staying still. The average pull cycle time (4d11h) is staying still. The average quality of service (83%) is decreasing (R=0.50). The average number of releases per month (19.2) is increasing (R=0.71). The average monthly turnover (16.0 developers) is increasing (R=0.72). The average weekly cost of HoC (5.94 points) is staying still. The average monthly zents/points ratio (0.32) is decreasing (R=0.53).

Assessment

The average reward per task (8.2 points) is staying still. The average punishment per task (7.0 points) is decreasing (R=-0.28). The average number of builds per week (5123.9) is increasing (R=0.83). The average number of commits per week (142.0) is increasing (R=0.70). The average bugs accepted per month (17.0) is increasing (R=0.64). The average monthly punishment (298 points) is increasing (R=0.30). The average monthly wage (9.8 points) is increasing (R=0.79). The average issue cycle time (1w) is staying still. The average pull cycle time (4d12h) is staying still. The average quality of service (83%) is decreasing (R=0.50). The average number of releases per month (19.2) is increasing (R=0.71). The average monthly turnover (16.0 developers) is increasing (R=0.70). The average weekly cost of HoC (6.01 points) is staying still. The average monthly zents/points ratio (0.33) is decreasing (R=0.45).

Repositories where the work is happening

Bylaws

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 bug is reported and accepted by the team, the reporter receives a bonus. Here is how it's calculated: Just award 12 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 16 points. Then, add 0.05 points for each hit-of-code, but not more than 16 points. Then, deduct 4 points if more than 100 hits-of-code. Then, deduct 8 points if more than 400 hits-of-code. Then, deduct 8 points if there were no code review. Then, deduct 0.1 points for every comment above 4 made during review, but not more than -16 points. Then, deduct 4 points if you contribute less than 40 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 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 12 points. Then, deduct 12 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 5 points if there were less than 12 comments made during review. Then, deduct 8 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 4 points if there were less than 32 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 receives a penalty. Here is how it's calculated: Just deduct -8 points.

When an enhancement is suggested and accepted by the team, the reporter receives a bonus. Here is how it's calculated: Just award 12 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 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 -8 points.

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 8 points. Then, add 4 points if it was resolved in less than 12 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.

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: 21567, EV: 39005, PV: 63951, CPI: +1.81, SPI: +0.61.

Dimensions of Terrain (DoT)

Dimensionw20w21w22w23w24w25w26w27
total_active_contributors1313131820232324
total_commits4966349935500575030450588506625086451162
total_contributors491492492499500503504508
total_files1449014750146491476914844146381465814702
total_forks393405415428435447451459
total_issues44834521453845934656470847904872
total_pulls84718631873088759106922293669535
total_releases852856857863877882892913
total_repositories3939394040393939
total_stars17761778178117851788178717861788