logo objectionary

Programmer / Award Reasonw10w11w12w13w14w15w16w17Run
@l3r8yj@l3r8yj (1 award)+12+12
@xworld21@xworld21 (1 award)+8+8
@senjeyb@senjeyb (1 award)+8+8
@georgysabaev@georgysabaev (1 award)+8+8
@h1alexbel@h1alexbel (36 awards)+44+25+23+32+77+20+221
@xzescha@xzescha (1 award)+4+4
@dirakon@dirakon (1 award)+4+4
@haidarjbeily7@haidarjbeily7 (1 award)+4+4
@marat-tim@marat-tim (1 award)+4+4
@volodya-lombrozo@volodya-lombrozo (36 awards)+48+18+28+11+22+12+139
@catdog905@catdog905 (2 awards)-24-24
@a1kuat@a1kuat (4 awards)-12-12
@vl4ds4m@vl4ds4m (4 awards)+3+4+7
@maxfunproger@maxfunproger (6 awards)+7+17+24
@lgrishin@lgrishin (4 awards)-12+8-12-16
@ivanovmg@ivanovmg (3 awards)-8+8
@yegor256@yegor256 (165 awards)-518-249+100-145-88-28-928
@deemp@deemp (1 award)-16-16
@maxonfjvipon@maxonfjvipon (40 awards)+38+38+32+16+20+24+168
Total (309/415):-417-164+194-98+60+40-385

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

When a bug is reported and accepted by the team, the reporter receives a bonus. Here is how it's calculated: Just award 8 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 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 above 8 made during review, but not more than -16 points. 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 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 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 receives a penalty. Here is how it's calculated: Just deduct -16 points.

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

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

Quality of Service (QoS)

Quantity of Deliverables (QoD)

Earned Value Analysis (EVA)

AC: -689, EV: -118115, PV: -17935, CPI: +171.43, SPI: +6.59.

Dimensions of Terrain (DoT)

Dimensionw10w11w12w13w14w15w16w17
total_active_contributors11121314131414
total_commits27966283032846325534257072583425888
total_contributors11511711986878888
total_files8121815483254723474847054658
total_forks273277279272314316318
total_issues4120415341784048405540784088
total_pulls6072617762135697573357885804
total_releases604610617590592595597
total_repositories52525343434343
total_stars1515153215471510156015581561