aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-12-14 12:44:13 +0100
committerWladimir J. van der Laan <laanwj@gmail.com>2015-12-14 12:44:27 +0100
commitea0f5a2b04bbbc80448e883824448acb3c5d1921 (patch)
tree3268439262d36b0e70a2f98706f54fd6e72d812e
parentb7c704abab4e4f32deef0541544421f348804d86 (diff)
parente1030dddab11553d2854c1f466e5757d9815bfb8 (diff)
Merge pull request #7185
e1030dd Note that reviewers should mention the commit hash of the commits they reviewed. (Patrick Strateman)
-rw-r--r--CONTRIBUTING.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1d42dea843..53d6527d40 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -95,6 +95,8 @@ Anyone may participate in peer review which is expressed by comments in the pull
- Concept ACK means "I agree in the general principle of this pull request";
- Nit refers to trivial, often non-blocking issues.
+Reviewers should include the commit hash which they reviewed in their comments.
+
Project maintainers reserve the right to weigh the opinions of peer reviewers using common sense judgement and also may weight based on meritocracy: Those that have demonstrated a deeper commitment and understanding towards the project (over time) or have clear domain expertise may naturally have more weight, as one would expect in all walks of life.
Where a patch set affects consensus critical code, the bar will be set much higher in terms of discussion and peer review requirements, keeping in mind that mistakes could be very costly to the wider community. This includes refactoring of consensus critical code.