This is an automated email from the ASF dual-hosted git repository.
guozhang pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kafka-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1701907 New Committer Guidelines (#161)
1701907 is described below
commit 170190743757cc70cbf36468553eb065a81a547f
Author: Guozhang Wang <[email protected]>
AuthorDate: Thu Sep 6 14:12:12 2018 -0700
New Committer Guidelines (#161)
Reviewers: Jun Rao <[email protected]>
---
contributing.html | 23 ++++++++++++++++++++++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/contributing.html b/contributing.html
index 6d1b80d..a1e4e97 100644
--- a/contributing.html
+++ b/contributing.html
@@ -54,7 +54,28 @@
<h2>Becoming a Committer</h2>
- We are always interested in adding new contributors. What we
look for is a series of contributions, good taste, and an ongoing interest in
the project. If you are interested in becoming a committer, let one of the
existing committers know and they can help guide you through the process.
+ We are always interested in adding new contributors. What we
look for is a series of contributions, good taste, and an ongoing interest in
the project.
+ The following is the guidelines that Kafka PMC is looking for
promoting new committers:
+
+ <ul>
+ <li>Made significant contributions in areas such as
design, code and/or documentation. The following are some examples (list not
exclusive):
+ <ul>
+ <li>Submitted and completed non-trivial
KIPs.</li>
+ <li>Fixed critical bugs (including
performance improvements).</li>
+ <li>Made major tech-debt cleanup.</li>
+ <li>Made major documentation (web docs
and java docs) improvements.</li>
+ </ul>
+ </li>
+ <li>Consistently helped the community in at least one
of the following areas since more than 6 months back (list not exclusive):
+ <ul>
+ <li>Mailing list participation.</li>
+ <li>Code reviews and KIP reviews.</li>
+ <li>Release validations including
testing and benchmarking, etc.</li>
+ <li>Evangelism events: technical talks,
blog posts, etc.</li>
+ </ul>
+ </li>
+ <li>Demonstrated good understanding and exercised good
technical judgement on at least one component of the codebase (e.g. core,
clients, connect, streams, tests) from contribution activities in the above
mentioned areas.</li>
+ </ul>
<script>
// Show selected style on nav item
