<div dir="ltr"><div>Reviewed-by: Matheus Santana <<a href="mailto:embs@cin.ufpe.br">embs@cin.ufpe.br</a>><br><br></div>It seems a great starting point.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 18, 2018 at 10:42 AM, Pekka Paalanen <span dir="ltr"><<a href="mailto:ppaalanen@gmail.com" target="_blank">ppaalanen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">From: Pekka Paalanen <<a href="mailto:pekka.paalanen@collabora.co.uk">pekka.paalanen@collabora.co.<wbr>uk</a>><br>
<br>
This sets up the standards for patch review, and defines when a patch<br>
can be merged. I believe these are the practises we have been using<br>
already for a long time, now they are just written down explicitly.<br>
<br>
It's not an exhaustive list of criteria and likely cannot ever be, but<br>
it should give a good idea of what level of review we want to have.<br>
<br>
It has been written in general terms, so that we can easily apply the<br>
same text not just to Wayland, but also Weston and other projects as<br>
necessary.<br>
<br>
This addition is not redundant with<br>
<a href="https://wayland.freedesktop.org/reviewing.html" rel="noreferrer" target="_blank">https://wayland.freedesktop.<wbr>org/reviewing.html</a> .<br>
<br>
The web page is a friendly introduction and encouragement for people to<br>
get involved. The guidelines here are more specific and aimed for people<br>
who seek commit rights or maintainership.<br>
<br>
Signed-off-by: Pekka Paalanen <<a href="mailto:pekka.paalanen@collabora.co.uk">pekka.paalanen@collabora.co.<wbr>uk</a>><br>
---<br>
CONTRIBUTING.md | 49 ++++++++++++++++++++++++++++++<wbr>+++++++++++++++++++<br>
1 file changed, 49 insertions(+)<br>
<br>
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md<br>
index 7ad75b8..6e74b6d 100644<br>
--- a/CONTRIBUTING.md<br>
+++ b/CONTRIBUTING.md<br>
@@ -197,5 +197,54 @@ New source code files should specify the MIT Expat license in their<br>
boilerplate, as part of the copyright statement.<br>
<br>
<br>
+Review<br>
+======<br>
+<br>
+All patches, even trivial ones, require at least one positive review<br>
+(Reviewed-by). Additionally, if no Reviewed-by's have been given by<br>
+people with commit access, there needs to be at least one Acked-by from<br>
+someone with commit access. A person with commit access is expected to be<br>
+able to evaluate the patch with respect to the project scope and architecture.<br>
+<br>
+During review, the following matters should be checked:<br>
+<br>
+- The commit message explains why the change is being made.<br>
+<br>
+- The code fits the project's scope.<br>
+<br>
+- The code license is the same MIT licence the project generally uses.<br>
+<br>
+- Stable ABI or API is not broken.<br>
+<br>
+- Stable ABI or API additions must be justified by actual use cases, not only<br>
+by speculation. They must also be documented, and it is strongly recommended to<br>
+include tests excercising the additions in the test suite.<br>
+<br>
+- The code fits the existing software architecture, e.g. no layering<br>
+violations.<br>
+<br>
+- The code is correct and does not ignore corner-cases.<br>
+<br>
+- In a patch series, every intermediate step produces correct code as well.<br>
+<br>
+- The code does what it says in the commit message and changes nothing else.<br>
+<br>
+- The test suite passes.<br>
+<br>
+- The code does not depend on API or ABI which has no working free open source<br>
+implementation.<br>
+<br>
+- The code is not dead or untestable. E.g. if there are no free open source<br>
+software users for it then it is effectively dead code.<br>
+<br>
+- The code is written to be easy to understand, or if code cannot be clear<br>
+enough on its own there are code comments to explain it.<br>
+<br>
+- The code is minimal, i.e. prefer refactor and re-use when possible unless<br>
+clarity suffers.<br>
+<br>
+- The code adheres to the style guidelines.<br>
+<br>
+<br>
[git documentation]: <a href="http://git-scm.com/documentation" rel="noreferrer" target="_blank">http://git-scm.com/<wbr>documentation</a><br>
[notes on commit messages]: <a href="http://who-t.blogspot.de/2009/12/on-commit-messages.html" rel="noreferrer" target="_blank">http://who-t.blogspot.de/2009/<wbr>12/on-commit-messages.html</a><br>
<span class="HOEnZb"><font color="#888888">-- <br>
2.16.4<br>
<br>
______________________________<wbr>_________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.<wbr>freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/wayland-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/wayland-devel</a><br>
</font></span></blockquote></div><br></div>