logo objectionary

You can get a similar report for your project

This week
Programmer / Award Reasonw37w38w39w40w41w42w43w44Run
@yarkivaev@yarkivaev (4 awards)+12+28+52
@pratyushkumar211@pratyushkumar211 (2 awards)+12-6+6
@tihiyn@tihiyn (5 awards)+12+16+9+37
@andreychh@andreychh (2 awards)+12+12+24
@maxim618@maxim618 (1 award)+12+12
@svmukhin@svmukhin (2 awards)+6+6
@morphqdd@morphqdd (5 awards)+36+24+60
@h1alexbel@h1alexbel (35 awards)+20+43+48+57+56+8+240
@volodya-lombrozo@volodya-lombrozo (42 awards)+41+83+56+19+58+14+4+275
@maxonfjvipon@maxonfjvipon (70 awards)-142+91-33+56+24+16+11+4+31
@andreoss@andreoss (1 award)+4+4
@mximp@mximp (1 award)+4+4
@graur@graur (1 award)+4+4
@danilax86@danilax86 (1 award)+4+4
@dirakon@dirakon (1 award)+4+4
@karina5005@karina5005 (1 award)+4+4
@snehakb1219-christ@snehakb1219-christ (1 award)-6-6
@raprogramm@raprogramm (6 awards)+7+4+12+23
@amirbekazimov@amirbekazimov (2 awards)-12-12
@hanmaster@hanmaster (2 awards)-6+12+6
@0xrelogic@0xrelogic (1 award)-6-6
@uchitsa@uchitsa (6 awards)-12-4+8-8
@yegor256@yegor256 (204 awards)+7-68+152+104+120+56+75+48+390
Total (396/2238):-38+193+217+249+270+137+124+82+1154

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)

There is no information about the Earned Value Analysis (EVA).

Dimensions of Terrain (DoT)

Dimensionw37w38w39w40w41w42w43w44
total_active_contributors15141314131414
total_commits41442466294681246987467214687247034
total_contributors448474476476477479479
total_files10739141091412814166141181410014120
total_forks332337343348349356355
total_issues4096412741464107416241744186
total_pulls6764690870096713708671347181
total_releases750527769775785788788
total_repositories37383838373737
total_stars1635165216621670166916721673