This is an automated email from the ASF dual-hosted git repository.
vinoth pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-hudi.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 27bf4b5 [HUDI-196] First draft of committership guidelines (#823)
27bf4b5 is described below
commit 27bf4b568079dda0591d10157a795acf35be011d
Author: vinoth chandar <[email protected]>
AuthorDate: Wed Aug 7 04:37:55 2019 -0700
[HUDI-196] First draft of committership guidelines (#823)
- Minor details on JIRA usage
- Updated html files
---
content/community.html | 19 +++++++++++++++++--
content/contributing.html | 6 ++++--
docs/community.md | 14 ++++++++++++++
docs/contributing.md | 5 +++--
4 files changed, 38 insertions(+), 6 deletions(-)
diff --git a/content/community.html b/content/community.html
index af2263a..853a5f6 100644
--- a/content/community.html
+++ b/content/community.html
@@ -46,7 +46,7 @@
<script
src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js";></script>
<![endif]-->
-<link rel="alternate" type="application/rss+xml" title=""
href="http://localhost:4000feed.xml";>
+<link rel="alternate" type="application/rss+xml" title=""
href="http://0.0.0.0:4000feed.xml";>
<script>
$(document).ready(function() {
@@ -389,6 +389,21 @@ Apache Hudi follows the typical Apache vulnerability
handling <a href="https://a
<li>Contributing code to the project (<a
href="https://issues.apache.org/jira/issues/?jql=project+%3D+HUDI+AND+component+%3D+newbie";>newbie
JIRAs</a>)</li>
</ul>
+<h2 id="become-a-committer">Become a Committer</h2>
+
+<p>We are always looking for strong contributors, who can become <a
href="https://www.apache.org/dev/committers.html";>committers</a> on the
project.
+Committers are chosen by a majority vote of the Apache Hudi <a
href="https://www.apache.org/foundation/how-it-works.html#pmc-members";>PMC</a>,
after a discussion on their candidacy based on the following criteria (not
exclusive/comprehensive).</p>
+
+<ul>
+ <li>Embodies the ASF model code of <a
href="https://www.apache.org/foundation/policies/conduct.html";>conduct</a></li>
+ <li>Has made significant technical contributions such as submitting PRs,
filing bugs, testing, benchmarking, authoring HIPs, providing feedback/code
reviews (+ more).</li>
+ <li>Has helped the community over a few months, by answering questions on
support channels above and triaging issues/jiras.</li>
+ <li>Demonstrates clear code/design ownership of a component or code area
(eg: Delta Streamer, Hive/Presto Integration etc).</li>
+ <li>Brought thought leadership and new ideas into the project and
evangelized them with the community via conference talks, blog posts.</li>
+ <li>Great citizenship in helping with all peripheral (but very critical)
work like site maintenance, wiki/jira cleanups and so on.</li>
+ <li>Proven commitment to the project by way of upholding all agreed upon
processes, conventions and principles of the community.</li>
+</ul>
+
<h3 id="code-contributions">Code Contributions</h3>
<p>Useful resources for contributing can be found under the “Developers” top
menu.
@@ -455,4 +470,4 @@ Specifically, please refer to the detailed <a
href="contributing.html">contribut
</body>
-</html>
\ No newline at end of file
+</html>
diff --git a/content/contributing.html b/content/contributing.html
index 034dd1c..62d54ac 100644
--- a/content/contributing.html
+++ b/content/contributing.html
@@ -46,7 +46,7 @@
<script
src="https://oss.maxcdn.com/libs/respond.js/1.4.2/respond.min.js";></script>
<![endif]-->
-<link rel="alternate" type="application/rss+xml" title=""
href="http://localhost:4000feed.xml";>
+<link rel="alternate" type="application/rss+xml" title=""
href="http://0.0.0.0:4000feed.xml";>
<script>
$(document).ready(function() {
@@ -362,6 +362,7 @@ These instructions have been tested on IntelliJ. We also
recommend setting up th
<li>[Optional] If you want to get involved, but don’t have a project in
mind, please check JIRA for small, quick-starters.</li>
<li>[Optional] Familiarize yourself with internals of Hudi using content on
this page, as well as <a
href="https://cwiki.apache.org/confluence/display/HUDI";>wiki</a></li>
<li>Once you finalize on a project/task, please open a new JIRA or assign an
existing one to yourself. (If you don’t have perms to do this, please email the
dev mailing list with your JIRA id and a small intro for yourself. We’d be
happy to add you as a contributor)</li>
+ <li>Almost all PRs should be linked to a JIRA. Before you begin work, click
“Start Progress” on the JIRA, which tells everyone that you are working on the
issue actively.</li>
<li>Make your code change
<ul>
<li>Every source file needs to include the Apache license header. Every
new dependency needs to
@@ -380,6 +381,7 @@ where you replace HUDI-XXX with the appropriate JIRA
issue.</li>
<li>If you don’t hear back within 3 days on the PR, please send an email to
dev @ mailing list.</li>
<li>Address code review comments & keep pushing changes to your
fork/branch, which automatically updates the PR</li>
<li>Before your change can be merged, it should be squashed into a single
commit for cleaner commit history.</li>
+ <li>As courtesy, if you are unable to continue working on a JIRA, please
move it back to “OPEN” state and unassign yourself.</li>
</ul>
<h2 id="releases">Releases</h2>
@@ -387,7 +389,7 @@ where you replace HUDI-XXX with the appropriate JIRA
issue.</li>
<ul>
<li>Apache Hudi community plans to do minor version releases every 6 weeks
or so.</li>
<li>If your contribution merged onto <code
class="highlighter-rouge">master</code> branch after the last release, it will
become part of next release.</li>
- <li>Website changes are regenerated once a week (until automation in place
to reflect immediately)</li>
+ <li>Website changes are regenerated on-demand basis (until automation in
place to reflect immediately)</li>
</ul>
<h2 id="accounts-and-permissions">Accounts and Permissions</h2>
diff --git a/docs/community.md b/docs/community.md
index 76b276b..aba54b2 100644
--- a/docs/community.md
+++ b/docs/community.md
@@ -36,6 +36,20 @@ Here are few ways, you can get involved.
- Share new ideas/directions to pursue or propose a new HIP
- Contributing code to the project ([newbie
JIRAs](https://issues.apache.org/jira/issues/?jql=project+%3D+HUDI+AND+component+%3D+newbie))
+## Become a Committer
+
+We are always looking for strong contributors, who can become
[committers](https://www.apache.org/dev/committers.html) on the project.
+Committers are chosen by a majority vote of the Apache Hudi
[PMC](https://www.apache.org/foundation/how-it-works.html#pmc-members), after a
discussion on their candidacy based on the following criteria (not
exclusive/comprehensive).
+
+ - Embodies the ASF model code of
[conduct](https://www.apache.org/foundation/policies/conduct.html)
+ - Has made significant technical contributions such as submitting PRs, filing
bugs, testing, benchmarking, authoring HIPs, providing feedback/code reviews (+
more).
+ - Has helped the community over a few months, by answering questions on
support channels above and triaging issues/jiras.
+ - Demonstrates clear code/design ownership of a component or code area (eg:
Delta Streamer, Hive/Presto Integration etc).
+ - Brought thought leadership and new ideas into the project and evangelized
them with the community via conference talks, blog posts.
+ - Great citizenship in helping with all peripheral (but very critical) work
like site maintenance, wiki/jira cleanups and so on.
+ - Proven commitment to the project by way of upholding all agreed upon
processes, conventions and principles of the community.
+
+
### Code Contributions
Useful resources for contributing can be found under the "Developers" top menu.
diff --git a/docs/contributing.md b/docs/contributing.md
index c8c505d..02c6375 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -35,6 +35,7 @@ Here's a typical lifecycle of events to contribute to Hudi.
- [Optional] If you want to get involved, but don't have a project in mind,
please check JIRA for small, quick-starters.
- [Optional] Familiarize yourself with internals of Hudi using content on
this page, as well as [wiki](https://cwiki.apache.org/confluence/display/HUDI)
- Once you finalize on a project/task, please open a new JIRA or assign an
existing one to yourself. (If you don't have perms to do this, please email the
dev mailing list with your JIRA id and a small intro for yourself. We'd be
happy to add you as a contributor)
+ - Almost all PRs should be linked to a JIRA. Before you begin work, click
"Start Progress" on the JIRA, which tells everyone that you are working on the
issue actively.
- Make your code change
- Every source file needs to include the Apache license header. Every new
dependency needs to
have an open source license
[compatible](https://www.apache.org/legal/resolved.html#criteria) with Apache.
@@ -50,13 +51,13 @@ Here's a typical lifecycle of events to contribute to Hudi.
- If you don't hear back within 3 days on the PR, please send an email to dev
@ mailing list.
- Address code review comments & keep pushing changes to your fork/branch,
which automatically updates the PR
- Before your change can be merged, it should be squashed into a single
commit for cleaner commit history.
-
+ - As courtesy, if you are unable to continue working on a JIRA, please move
it back to "OPEN" state and unassign yourself.
## Releases
- Apache Hudi community plans to do minor version releases every 6 weeks or
so.
- If your contribution merged onto `master` branch after the last release, it
will become part of next release.
- - Website changes are regenerated once a week (until automation in place to
reflect immediately)
+ - Website changes are regenerated on-demand basis (until automation in place
to reflect immediately)
## Accounts and Permissions
