This is an automated email from the ASF dual-hosted git repository.
ulyssesyou pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-kyuubi-website.git
The following commit(s) were added to refs/heads/master by this push:
new 19df1f9 Become A Committer of Apache Kyuubi (#48)
19df1f9 is described below
commit 19df1f9f5cba730d54beeae04cefeb890da2d4a1
Author: Kent Yao <[email protected]>
AuthorDate: Thu Mar 10 09:35:32 2022 +0800
Become A Committer of Apache Kyuubi (#48)
* Become A Committer of Apache Kyuubi
* Become A Committer of Apache Kyuubi
---
config.toml | 1 +
src/become_committer.md | 81 +++++++++++++++++++++++++++++++++++++++++++++++++
src/issue_tracking.md | 3 +-
src/mailing_lists.md | 2 +-
src/pull_request.md | 17 ++++++-----
5 files changed, 94 insertions(+), 10 deletions(-)
diff --git a/config.toml b/config.toml
index 3d6a751..662a32c 100644
--- a/config.toml
+++ b/config.toml
@@ -47,6 +47,7 @@ publishDir = "content"
name = "Code of Conduct"
url = "https://www.apache.org/foundation/policies/conduct"
parent = "community"
+ weight = 1
[[menu.main]]
name = "Development"
diff --git a/src/become_committer.md b/src/become_committer.md
new file mode 100644
index 0000000..93a58b4
--- /dev/null
+++ b/src/become_committer.md
@@ -0,0 +1,81 @@
+---
+title: Become A Committer of Apache Kyuubi
+menu:
+ main:
+ name: "Become A Committer"
+ parent: "community"
+---
+<!---
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License. See accompanying LICENSE file.
+-->
+
+<img
src="https://svn.apache.org/repos/asf/comdev/project-logos/originals/kyuubi-1.svg"
alt="Kyuubi logo" width="30%" align="right" />
+
+Anyone being supportive of the community and working in any of the
+CoPDoC areas can become an Apache Kyuubi committer. The CoPDoC is an
+acronym from ASF to describe how we recognize your contributions not
+only by code.
+
+- **Co**mmunity - You can join us via our mailing list, issue
+ trackers, discussions page to interact with community members, and
+ share vision and knowledge
+- **P**roject - a clear vision and consensus are needed
+- **Do**cumentation - without it, the stuff remains only in the minds
+ of the authors
+- **C**ode - discussion goes nowhere without code
+
+Apache Kyuubi community strives to be meritocratic. Thus, once someone
+has contributed sufficiently to any area of CoPDoC they can be a
+candidate for committer-ship and at last voted in as a Kyuubi
+committer. Being an Apache Kyuubi committer does not necessarily mean
+you must commit code with your commit privilege to the codebase; it
+means you are committed to the Kyuubi project and are productively
+contributing to our community's success.
+
+## Committer requirements:
+
+There are no strict rules for becoming a committer or PPMC member.
+Candidates for new committers are typically people that are active
+contributors and community members. Anyway, if the rules can be
+clarified a little bit, it can somehow clear the doubts in the minds
+of contributors and make the community more transparent, reasonable,
+and fair.
+
+### Continuous contributions
+
+Committer candidates should have a decent amount of continuous
+engagements and contributions (fixing bugs, adding new features,
+writing documentation, maintaining issues boards, code review, or answering
+community questions) to Kyuubi either by contributing to the codebase
+of the main website or Kyuubi's GitHub repositories.
+
+- +3 months with light activity and engagement.
+- +2 months of medium activity and engagement.
+- +1 month with solid activity and engagement.
+
+### Quality of contributions
+- A solid general understanding of the project
+- Well tested, well-designed, following Apache Kyuubi coding
+ standards, and simple patches.
+- Well-organized and detailed user-oriented documentation.
+
+### Community involvement
+
+- Be active, courteous, and respectful on the dev mailing list and
+ help mentor newer contributors
+ and users.
+- Be active, courteous, and respectful on the issue tracker for
+ project maintenance
+- Be active, courteous, and respectful for pull requests reviewing
+- Be involved in the design road map discussions with a professional
+ and diplomatic approach even if there is a disagreement
diff --git a/src/issue_tracking.md b/src/issue_tracking.md
index b00b3dd..cf23197 100644
--- a/src/issue_tracking.md
+++ b/src/issue_tracking.md
@@ -3,7 +3,8 @@ title: Issue Tracker
menu:
main:
name: "Issue Tracker"
- parent: "community"
+ parent: "development"
+ weight: 1
---
<!---
Licensed under the Apache License, Version 2.0 (the "License");
diff --git a/src/mailing_lists.md b/src/mailing_lists.md
index 1e599a6..9b1eea7 100644
--- a/src/mailing_lists.md
+++ b/src/mailing_lists.md
@@ -2,7 +2,7 @@
title: Kyuubi Mailing Lists
menu:
main:
- name: "Mailing Lists"
+ name: "Join the Mailing Lists"
parent: "community"
---
<!---
diff --git a/src/pull_request.md b/src/pull_request.md
index 42c29b0..5f24de7 100644
--- a/src/pull_request.md
+++ b/src/pull_request.md
@@ -1,9 +1,10 @@
---
-title: Contributing
+title: Guide for Pull Requests
menu:
- main:
- name: "Pull Request"
- parent: "community"
+ main:
+ name: "Pull Request"
+ parent: "development"
+ weight: 3
---
<!---
Licensed under the Apache License, Version 2.0 (the "License");
@@ -19,14 +20,14 @@ menu:
limitations under the License. See accompanying LICENSE file.
-->
-# Review pull requests
+## Review pull requests
Kyuubi encourage to help review pull requests of other developers which makes
code more robust.
The review guide can see [Google’s Engineering Practices
documentation](https://google.github.io/eng-practices/review/).
-# Submit your pull requests
+## Submit your pull requests
-## Before
+### Before
Before proceeding, it's better to search the issues and pull requests history
first. Likely, the problem or request has been discussed.
@@ -64,7 +65,7 @@ A developer can convey proposed code changes and their
purposes either through d
They're also a great way to help track things that should be done for every
change, such as testing, adding unit tests, and updating documentation in the
git log.
See [Pull Request
Template](https://github.com/apache/incubator-kyuubi/blob/master/.github/PULL_REQUEST_TEMPLATE).
-## After
+### After
It may take some time to wait other developer to review. Feel free to ping any
committer who has worked on the similar area.
In general, You can find out the right people to review your code through git
commit history.