This is an automated email from the ASF dual-hosted git repository.
pingsutw pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/submarine.git
The following commit(s) were added to refs/heads/master by this push:
new 2e519d2 SUBMARINE-1086. Page of How to Become a Committer
2e519d2 is described below
commit 2e519d24d7f5000b3d24dd1511d62891511f1e36
Author: featherchen <[email protected]>
AuthorDate: Sat Nov 20 02:17:28 2021 +0800
SUBMARINE-1086. Page of How to Become a Committer
### What is this PR for?
<!-- A few sentences describing the overall goals of the pull request's
commits.
First time? Check out the contributing guide -
https://submarine.apache.org/contribution/contributions.html
-->
Follow the similar page of
[inLong](https://inlong.apache.org/development/how-to-become-a-committer/)
Add more description about how to become a committer.
### What type of PR is it?
Documentation
### Todos
* [ ] - Should I also update the website of version 0.6.0 ?
### What is the Jira issue?
<!-- * Open an issue on Jira
https://issues.apache.org/jira/browse/SUBMARINE/
* Put link here, and add [SUBMARINE-*Jira number*] in PR title, eg.
`SUBMARINE-23. PR title`
-->
https://issues.apache.org/jira/browse/SUBMARINE-1086
### How should this be tested?
<!--
* First time? Setup Travis CI as described on
https://submarine.apache.org/contribution/contributions.html#continuous-integration
* Strongly recommended: add automated unit tests for any new or changed
behavior
* Outline any manual steps to test the PR here.
-->
Please help me double-check whether the article is fluent or not.
### Screenshots (if appropriate)
### Questions:
* Do the license files need updating? No
* Are there breaking changes for older versions? No
* Does this need new documentation? No
Author: featherchen <[email protected]>
Signed-off-by: Kevin <[email protected]>
Closes #805 from featherchen/SUBMARINE-1086 and squashes the following
commits:
0ca4ad05 [featherchen] fixed typo
9d662570 [featherchen] change to a shorter title
7ff9ccb2 [featherchen] delete redulant files
83a237cf [featherchen] add HowToBecomeCommitter Page
---
website/docs/community/HowToBecomeCommitter.md | 43 ++++++++++++++++++++++++++
website/docs/community/README.md | 4 ++-
website/sidebars.js | 1 +
3 files changed, 47 insertions(+), 1 deletion(-)
diff --git a/website/docs/community/HowToBecomeCommitter.md
b/website/docs/community/HowToBecomeCommitter.md
new file mode 100644
index 0000000..5b4932e
--- /dev/null
+++ b/website/docs/community/HowToBecomeCommitter.md
@@ -0,0 +1,43 @@
+---
+title: How to become a Committer
+---
+
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You 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.
+-->
+
+Apache Submarine builds a community completely following Apache’s rules.
Apache Committer is a term used in ASF (Apache Software Foundation) to indicate
the person who submits a specific project. Apache Submarine Committer has
permission to write the Submarine codebase and can merge PR. Anyone who has
made enough contributions to the community and gained enough trust can become
an Apache Submarine Committer.
+
+As long as anyone contributes to the Submarine project, you are the officially
recognized Contributor of the Submarine project. There is no exact standard for
growing from Contributor to Committer, and there is no expected timetable, but
Committer candidates are generally long-term active contributors, becoming
Committer does not require a huge architectural improvement contribution, or
how many lines of code contribution. Contributing to the codebase, contributing
to the documents, part [...]
+
+List of potential contributions (in no particular order):
+
+- Submit the bugs, features, and improvements you found to the issue
+- Update the official documents so that the project documents are the most
recent, the best practices for writing Submarine, and various useful documents
for users to analyze the features.
+- Perform test and report test results.
+- Actively participate in voting when the version is released
+- Participate in the discussion on the mailing list, usually there will be
mails starting with [DISCUSS]
+- Answer questions from users or developers on the mailing list
+- Review the work of others (both code and non-code) and publish your own
suggestions
+- Review the issues on JIRA and maintain the latest status of the issues, such
as closing outdated issues, changing the issue’s error information, etc.
+- Guide new contributors and be familiar with the community process
+- Give speeches and blogs about Submarine, and add these to the official
website of Submarine
+- Any contribution that is beneficial to the development of the Submarine
community
+ ......
+
+More can refer to: [ASF official
documents](https://community.apache.org/contributors/)
+
+Not everyone can complete all (or even any) items on this list. If you want to
contribute in other ways, then just do it (and add them to the list). Pleasant
manners and dedication are all you need to have a positive impact on the
Submarine project. Inviting you to become Committer is the result of your
long-term and stable interaction with the community, and the trust and
recognition of the Submarine community.
+
+Committer is obliged to review and merge PRs submitted by others, test and
vote on candidate versions when the version is released, participate in the
discussion of feature design plans, and other types of project contributions.
When you are active enough and make a bigger contribution to the community, you
can be promoted to a PMC member of the Submarine project.
diff --git a/website/docs/community/README.md b/website/docs/community/README.md
index 7c02a93..182a038 100644
--- a/website/docs/community/README.md
+++ b/website/docs/community/README.md
@@ -54,7 +54,9 @@ First of all, you need to get involved and be a Contributor.
Based on your track-record as a contributor, Per Apache code, PMCs vote on
committership, may invite you to be a committer (after we've called a vote).
When that happens, if you accept, the following process kicks into place...
-Note that becoming a committer is not just about submitting some patches; it‘s
also about helping out on the development and user [Slack
User](https://the-asf.slack.com/submarine-user/), helping with documentation
and the issues.
+Note that becoming a committer is not just about submitting some patches; it‘s
also about helping out on the development and user, helping with documentation
and the issues.
+
+See [How to become an Apache Submarine Committer and
PMC](HowToBecomeCommitter.md) for more details.
## How to commit
diff --git a/website/sidebars.js b/website/sidebars.js
index a9a34e8..3edeb46 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -69,6 +69,7 @@ module.exports = {
"community/Bylaws",
"community/HowToCommit",
"community/contributing",
+ "community/HowToBecomeCommitter",
],
"Design Docs": [
"designDocs/architecture-and-requirements",
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
