You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: using/product/reputation.md
+21-16
Original file line number
Diff line number
Diff line change
@@ -65,16 +65,17 @@ By default, `12` reputation is awarded when a pull request is merged that was op
65
65
66
66
Depending on the content of the pull request, a maintainer can award more (or less) reputation by adding one of the following labels to the pull request:
|`x:rep/tiny`| 3 | <ul><li>Fixing a single typo or link</li><li>Removing a blank line or adding a line break</li><li>Changing/adding a single code comment</li></ul> |
71
-
|`x:rep/small`| 5 | <ul><li>Fixing a single test case, task or example</li><li>Fixing multiple typos or links in a single file</li><li>Clarifying content by adding a few lines to a file</li></ul> |
72
-
|`x:rep/medium`| 12 | <ul><li>Syncing an exercise with problem-specifications (incl. edits)</li><li>Adding one or more test cases from scratch</li><li>Improving multiple files in an exercise</li><li>Adding mentor notes for an exercise from scratch</li><li>Fixing a small bug in a test runner/analyzer/representer</li><li>Adding analyzer comments for a single exericse</li></ul> |
73
-
|`x:rep/large`| 30 | <ul><li>Adding a new concept or practice exercise</li><li>Adding new concept documentation</li><li>Substantial re-writing of an existing concept or exercise</li><li>Adding new CI scripts or other automation</li></ul> |
74
-
|`x:rep/massive`| 100 | <ul><li>Creating a test-runner, analyzer, representer or generator from scratch</li><li>Major refactors to those tools</li><li>Creating major documentation from scratch (e.g. contribution or testing guides)</li></ul> |
|`x:rep/tiny`| 3 (~5 mins)| <ul><li>Fixing a single typo or link</li><li>Removing a blank line or adding a line break</li><li>Changing/adding a single code comment</li></ul> |
71
+
|`x:rep/small`| 5 (~10 mins)| <ul><li>Fixing a single test case, task or example</li><li>Fixing multiple typos or links in a single file</li><li>Clarifying content by adding a few lines to a file</li></ul> |
72
+
|`x:rep/medium`| 12 (~30 mins)| <ul><li>Syncing an exercise with problem-specifications (incl. edits)</li><li>Adding one or more test cases from scratch</li><li>Improving multiple files in an exercise</li><li>Adding mentor notes for an exercise from scratch</li><li>Fixing a small bug in a test runner/analyzer/representer</li><li>Adding analyzer comments for a single exericse</li></ul> |
73
+
|`x:rep/large`| 30 (~2 hrs)| <ul><li>Adding a new concept or practice exercise</li><li>Adding new concept documentation</li><li>Substantial re-writing of an existing concept or exercise</li><li>Adding new CI scripts or other automation</li></ul> |
74
+
|`x:rep/massive`| 100 (~5 hrs)| <ul><li>Creating a test-runner, analyzer, representer or generator from scratch</li><li>Major refactors to those tools</li><li>Creating major documentation from scratch (e.g. contribution or testing guides)</li></ul> |
75
75
76
76
The examples above can serve as rough orientation when to apply which label but maintainers are free to use their own judgement.
77
77
78
+
- The estimated number of time spent should be interpreted as the average time a _maintainer_ would spend on doing the PR.
78
79
- If more than one label is specified, the label with the highest reputation value determines the awarded reputation.
79
80
- If a pull request is still open, no reputation is awarded (yet).
80
81
- If a pull request is closed _without_ merging, no reputation is awarded.
@@ -101,6 +102,9 @@ For each merged or closed pull request reviewed by the user, `5` reputation is a
101
102
|`x:rep/large`| 10 |
102
103
|`x:rep/massive`| 20 |
103
104
105
+
It is _not_ possible to use different reputation "sizes" for a pull request author and reviewer.
106
+
Both are based on the same `x:rep` label.
107
+
104
108
If more than one label is specified, the label with the highest reputation value determines the awarded reputation.
105
109
106
110
_For backwards compatibility purposes, we also support using the `x:size` labels to determine the awarded reputation._
@@ -120,15 +124,16 @@ By default, **no reputation is awarded** when an issue is opened.
120
124
121
125
Depending on the content of the issue, a maintainer can choose to award reputation by adding one of the following labels to the issue:
|`x:rep/tiny`| 3 | <ul><li>Fixing a single typo or link</li><li>Removing a blank line or adding a line break</li><li>Changing/adding a single code comment</li></ul> |
126
-
|`x:rep/small`| 5 | <ul><li>Fixing a single test case, task or example</li><li>Fixing multiple typos or links in a single file</li><li>Clarifying content by adding a few lines to a file</li></ul> |
127
-
|`x:rep/medium`| 12 | <ul><li>Syncing an exercise with problem-specifications (incl. edits)</li><li>Adding one or more test cases from scratch</li><li>Improving multiple files in an exercise</li><li>Adding mentor notes for an exercise from scratch</li><li>Fixing a small bug in a test runner/analyzer/representer</li><li>Adding analyzer comments for a single exericse</li></ul> |
128
-
|`x:rep/large`| 30 | <ul><li>Fully-fleshed out Concept Exercise</li></ul> |
129
-
|`x:rep/massive`| 100 | <ul><li>Designing a track curriculum</li></ul> |
|`x:rep/tiny`| 3 (~5 mins)| <ul><li>Fixing a single typo or link</li><li>Removing a blank line or adding a line break</li><li>Changing/adding a single code comment</li></ul> |
130
+
|`x:rep/small`| 5 (~10 mins)| <ul><li>Fixing a single test case, task or example</li><li>Fixing multiple typos or links in a single file</li><li>Clarifying content by adding a few lines to a file</li></ul> |
131
+
|`x:rep/medium`| 12 (~30 mins)| <ul><li>Syncing an exercise with problem-specifications (incl. edits)</li><li>Adding one or more test cases from scratch</li><li>Improving multiple files in an exercise</li><li>Adding mentor notes for an exercise from scratch</li><li>Fixing a small bug in a test runner/analyzer/representer</li><li>Adding analyzer comments for a single exericse</li></ul> |
132
+
|`x:rep/large`| 30 (~2 hrs)| <ul><li>Fully-fleshed out Concept Exercise</li></ul> |
133
+
|`x:rep/massive`| 100 (~5 hrs)| <ul><li>Designing a track curriculum</li></ul> |
130
134
131
-
The reputation should reflect the amount of effort that went into creating the issue.
132
-
The examples above can serve as rough orientation when to apply which label but maintainers are free to use their own judgement.
135
+
The examples above can serve as rough orientation when to apply which label, but maintainers are free to use their own judgement.
136
+
137
+
- The reputation should reflect the amount of effort that _maintainer_ would spend to create the issue.
133
138
134
139
- If more than one label is specified, the label with the highest reputation value determines the awarded reputation.
0 commit comments