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 9664475 SUBMARINE-1087. Page of How to Vote a Committer or PMC
9664475 is described below
commit 966447524e67eaa8156d231d67fabf9ccdf6291f
Author: featherchen <[email protected]>
AuthorDate: Tue Nov 23 14:18:24 2021 +0800
SUBMARINE-1087. Page of How to Vote a Committer or PMC
### 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
-->
Refer to https://inlong.apache.org/development/how-to-become-a-committer/
Create a new page in the website and add some description about the process
of voting a committer or PMC.
### What type of PR is it?
Documentation
### Todos
### 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-1087
### 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 english is right.
### 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]>
Author: Kevin Su <[email protected]>
Signed-off-by: Kevin <[email protected]>
Closes #806 from featherchen/SUBMARINE-1087 and squashes the following
commits:
7247934a [Kevin Su] Merge branch 'master' into SUBMARINE-1087
fcb5994f [featherchen] fix typo
2eead1b5 [featherchen] translate it from inLong
---
website/docs/community/HowToVoteCommitterOrPMC.md | 54 +++++++++++++++++++++++
website/sidebars.js | 1 +
2 files changed, 55 insertions(+)
diff --git a/website/docs/community/HowToVoteCommitterOrPMC.md
b/website/docs/community/HowToVoteCommitterOrPMC.md
new file mode 100644
index 0000000..6829101
--- /dev/null
+++ b/website/docs/community/HowToVoteCommitterOrPMC.md
@@ -0,0 +1,54 @@
+---
+title: How to vote a Committer or PMC
+---
+
+<!--
+ 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.
+-->
+
+### The voting process of becoming a Submarine Committer or PMC
+
+1. After the PMC members of Submarine discover any valuable contributions from
the community contributors and obtain the consent of the candidate, they
initiate a discussion on the private mailing list of Submarine:
+
+ > [DISCUSS] YYYYY as a Submarine XXXXXX
+
+ In the email, the source of the candidate’s contributions should be clearly
stated, so that everyone can discuss and analyze. The discussion email will
last at least 72 hours, and the project team members, including the mentors,
will fully express their views on the proposed email.
+
+2. Regardless of whether there is a disagreement, after the discussion email,
the vote initiator needs to initiate a Committer or PMC vote on the private
mailing list of Submarine;
+
+ > [VOTE] YYYYY as a Submarine XXXXXX
+
+ The voting mail should last for at least 72 hours, and there should be at
least 3 +1 votes to pass the vote. If there are 0 votes or one -1 vote, the
entire vote will fail. If voting -1, you need to clarify the question so that
everyone can understand.
+
+3. After the voting email is over, the vote initiator should summarize it on
the voting line, remind the end of voting, and send it to the voting summary
email.
+
+ > [RESULTS][vote] YYYYY as a Submarine XXXXXX
+
+4. After the vote summary email is sent, if the vote passed, the vote
initiator must send an invitation email to the candidate, and the invitation
email needs the candidate to reply to accept or decline through the designated
mailbox.
+
+ > [Invitation] Invitation to join Apache Submarine as a XXXXXX
+
+ The email should be sent to the candidate, and the copy is sent to
[email protected]
+
+5. After the candidate accepts the invitation, if the candidate does not have
an apache email account, the vote initiator needs to assist the candidate to
create an apache account according to the guidelines.
+
+6. If the above content is completed, the vote initiator still needs to do the
following two things:
+
+ 6.1 Apply to the project leader to add project team members, and open the
authority accounts for the jira and apache projects.
+
+ 6.2 Send a notification email to the [email protected] mail group:
+
+ > [ANNOUNCE] New XXXXXX: YYYYY
+
+So far, the entire process is completed, then the candidate officially becomes
the Committer or PMC of Submarine.
diff --git a/website/sidebars.js b/website/sidebars.js
index 2d893e7..6679baa 100644
--- a/website/sidebars.js
+++ b/website/sidebars.js
@@ -70,6 +70,7 @@ module.exports = {
"community/Bylaws",
"community/HowToCommit",
"community/contributing",
+ "community/HowToVoteCommitterOrPMC",
"community/HowToBecomeCommitter",
],
"Design Docs": [
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
