You are here: Hackfest Scoring
| Activity | Score | - |
|---|---|---|
| +1 | +250 | (up to a maximum of 750) |
| -1 | -250 | (but cannot go below 0) |
| verified | 750 | (overrides any +1 or -1 points) |
| changeset | 5000 | (overrides any +1, -1 , or verified points) |
| Activity | Points | - |
|---|---|---|
| +1 | +250 | (up to a maximum of 750) |
| -1 | -250 | (but cannot go below 0) |
| verified | 750 | (overrides any +1 or -1 points) |
| changeset | 5000 | (overrides any +1, -1 , or verified points) |
In addition the following activities have a score attached which count towards each contributor's overall ranking:
100: accepted patches
60: accepted documentation
40: open patches
20: untested patches
15: tiny patches
10: denied patches
10: reporting a new ticket
5: resolving a ticket
1: commenting
See scoring details for more information.
Tickets related to the following are currently filtered out of the main scoring: prototype, script.aculo.us, capistrano, spinoffs
A contributor is given credit in a changeset by a core team member. They are usually listed within square brackets within the changeset description. If this is not the case the then the original contributor of the patch is awarded the points.
It's worth noting that ticket / changeset scores are not carried through from month to month. For example a +1 given in September does not carry through to October.
See the guide on contributing and the contributor zone of this site.
Feel free to drop a line with your questions, comments, and suggestions
The maximum a contributor can receive for any single ticket is 5000 points. This applies when a member of the core team commits the patch through a changeset.
If a ticket is marked as verified then it is awarded 750 points.
The original contributor is awarded 250 points for each +1 they
receive as comment by another contributor (up to a maximum of 750 points.)

Find your next Ruby on Rails project or job.
Exclusive content,
regularly updated - onsite and tele-working positions listed.