This is an automated email from the ASF dual-hosted git repository.
weibin pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-graphar-website.git
The following commit(s) were added to refs/heads/main by this push:
new eaf2668 Add document about how to be/nominate a committer (#25)
eaf2668 is described below
commit eaf26688e374317583289848da0169a3c3b5086b
Author: Weibin Zeng <[email protected]>
AuthorDate: Thu Aug 8 14:02:42 2024 +0800
Add document about how to be/nominate a committer (#25)
Signed-off-by: acezen <[email protected]>
---
community/committers/nominating-a-committer.md | 185 +++++++++++++++++++++++++
community/how-to-become-a-committer.md | 39 ++++++
2 files changed, 224 insertions(+)
diff --git a/community/committers/nominating-a-committer.md
b/community/committers/nominating-a-committer.md
new file mode 100644
index 0000000..4601d2e
--- /dev/null
+++ b/community/committers/nominating-a-committer.md
@@ -0,0 +1,185 @@
+---
+title: Nominating a Committer and PPMC member
+sidebar_position: 3
+---
+
+## Initiate discussion in the community private mailing group
+Any Apache GraphAr (incubating) PPMC member can initiate a voting discussion.
+After PPMC member finds any valuable contributions from community contributors
and obtains the consent of the candidate, they can initiate a discussion on
GraphAr's private mailing list.
+In the discussion email, the proposer should clearly state the candidate's
contribution and give the address for reviewing the corresponding contribution,
so that everyone can discuss and analyze it.
+The discussion email is sent to [email protected]. The discussion
will last at least 72 hours. PPMC members will fully express their views on the
proposed email.
+The following is a template discussion email:
+```shell
+To: [email protected]
+Subject: [DISCUSS] Propose {Candidate_Full_Name} as new {committer or PPMC
member}
+
+Hi, GraphAr PPMC,
+
+I'd like to discuss the proposal to add ${Candidate_Full_Name} as a new
${committer or PPMC member}
+
+<Brief description and links of ${Candidate_Full_Name}'s contributions>
+
+1.
https://github.com/apache/incubator-graphar/issues/created_by/{Candidate_GitHub_ID}
+2.
https://github.com/apache/incubator-graphar/commits?author={Candidate_GitHub_ID}
+```
+
+:::caution
+You can communicate with candidates in advance to obtain his/her full name,
and replace the `${Candidate_Full_Name}`.
+:::
+
+## Initiate vote in the community private mailing group
+If the discussion email does not receive the disagreement information within
the specified time, the poll initiator needs to initiate a committer or PPMC
member election vote on private mailing list.
+The voting email is sent to [email protected] for at least 72 hours,
and at least 3 votes +1 passed; if 0 votes or 1 vote -1 vote, the vote will
fail; if a -1 vote is initiated, the voter needs to EXPLAIN the reason for the
-1 score clearly so that everyone can understand and know.
+The following is a template poll email:
+```shell
+To: [email protected]
+Subject: [VOTE] New {committer or PPMC member}: {Candidate_Full_Name}
+
+Hi, GraphAr PPMC,
+
+ <Brief description and links of {Candidate_Full_Name}'s contributions>
+
+I think making him/her a ${committer or PPMC member} will be a recognition of
his outstanding work for GraphAr. So, I am happy to call VOTE to accept
${Candidate_Full_Name} as an GraphAr ${committer or PPMC member}.
+
+Voting will continue for at least 72 hours or until the required number of
votes is reached.
+
+Please vote accordingly:
+[ ] +1 approve
+[ ] +0 no opinion
+[ ] -1 disapprove with the reason
+
+Here are three links to his contributions to GraphAr:
+1. Issues:
https://github.com/apache/incubator-graphar/pulls?q={Candidate_GitHub_ID}
+2. PRs :
https://github.com/apache/incubator-graphar/issues?q={Candidate_GitHub_ID}
+3. Others: https://xxx.com/xxx/xxx/?q={Candidate_GitHub_ID}
+```
+
+## Feedback on voting results
+After the voting email is over, the initiator of the vote needs to `remind the
voting end` in the second [VOTE] email; at the same time, the initiator of the
vote needs to initiate a vote summary email, and the summary email is sent to
[email protected].
+The following is a template vote summary email:
+```shell
+To: [email protected]
+Subject: [RESULTS][VOTE] New {committer or PPMC member}: {Candidate_Full_Name}
+
+Hi everyone,
+
+The vote has now closed. The results are:
+
+Binding Votes:
++1 [TOTAL BINDING +1 VOTES]
+ 0 [TOTAL BINDING +0/-0 VOTES]
+-1 [TOTAL BINDING -1 VOTES]
+
+
+Vote thread:
+${vote_thread_url}
+
+Then I'm going to invite ${Candidate_Full_Name} to join us.
+
+Thanks for everyone's support!
+```
+
+:::caution
+If it is not passed, the result is "The vote for Candidate_Full_Name as an
GraphAr committer or PPMC member" has FAILED and closed now."
+:::
+
+### Committer Invitation
+
+This is the suggested invitation email to send to the newly elected committer,
sent after a positive result from the vote for a new committer.
+
+```shell
+To: {Candidate_Email}
+Cc: [email protected]
+Subject: Invitation to become Apache GraphAr (incubating) committer:
{Candidate_Full_Name}
+
+Hello {Candidate_Full_Name},
+
+The GraphAr Podling Project Management Committee (PPMC)
+hereby offers you committer privileges to the project.
+These privileges are offered on the understanding that you'll use them
+reasonably and with common sense. We like to work on trust
+rather than unnecessary constraints.
+
+Being a committer enables you to more easily make
+changes without needing to go through the patch
+submission process.
+
+Being a committer does not require you to
+participate any more than you already do. It does
+tend to make one even more committed. You will
+probably find that you spend more time here.
+
+Of course, you can decline and instead remain as a
+contributor, participating as you do now.
+
+This personal invitation is a chance for you to accept or decline in private.
+Please let us know in reply to this message whether you accept or decline.
+
+If you accept, you will need an Apache account (id) with privileges.
+Please follow these instructions.
+
+A. If you already have an ICLA on file:
+
+1. If you already have an Apache account, let us know your id and we
+will grant you privileges on the project repositories.
+
+2. If you have previously sent an ICLA, let us know the email address
+and public name used on the ICLA and your preferred Apache id, and
+we will request your account.
+
+3. If the email address on the previously submitted ICLA is no longer
+valid, let us know the email address and public name used on the new ICLA,
+and your preferred Apache id. Continue to step B below and file your new ICLA.
+
+Look to see if your preferred ID is already taken at
+https://people.apache.org/committer-index.html
+
+B. If there is not already an ICLA on file, you need to submit an ICLA:
+
+1. Details of the ICLA and the forms are found
+through this link: https://www.apache.org/licenses/#clas
+
+2. Instructions for its completion and return to
+the Secretary of the ASF are found at
+https://www.apache.org/licenses/contributor-agreements.html#submitting
+
+Do not copy the project or any other individual on your message
+to Secretary, as the form contains Personally Identifiable Information
+that should be kept private.
+
+3. When you complete the ICLA form, be sure to include in the form
+the Apache GraphAr project and choose a
+unique Apache ID. Look to see if your preferred
+ID is already taken at
+https://people.apache.org/committer-index.html
+This will allow the Secretary to notify the PPMC
+when your ICLA has been recorded.
+
+When recording of your ICLA is noted, you will
+receive a follow-up message with the next steps for
+establishing you as a committer.
+```
+
+### Announcement of the new committer
+This is the email to announce the new committer to graphar-dev once the
account has been created.
+
+```shell
+To: [email protected]
+Subject: [ANNOUNCE] New committer: {Candidate_Full_Name}
+
+The Podling Project Management Committee (PPMC) for Apache GraphAr
+has invited {Candidate_Full_Name} to become a committer and we are pleased
+to announce that they have accepted.
+
+### add specific details here ###
+
+Being a committer enables easier contribution to the
+project since the committer has write access to the repository
+This should enable better productivity.
+```
+
+
+At this point, the entire process is completed, and the candidate officially
becomes the Committer or PMC Member of the project.
+
+---
+The document is based on [apache
newcommitter](https://community.apache.org/newcommitter.html#new-committer-process)
\ No newline at end of file
diff --git a/community/how-to-become-a-committer.md
b/community/how-to-become-a-committer.md
new file mode 100644
index 0000000..866d558
--- /dev/null
+++ b/community/how-to-become-a-committer.md
@@ -0,0 +1,39 @@
+---
+title: How to Become a Committer or PPMC member
+sidebar_position: 3
+---
+
+:::note
+[Apache GraphAr (incubating)](https://graphar.apache.org) is to build a
community in full accordance with Apache’s rules.
+Apache Committer is a term used in ASF (Apache Software Foundation) to refer
to people who submit specific projects.
+Committer has the permission to write the GraphAr code base and can merge PR.
+Anyone who has made enough contributions to the community and gained enough
trust can become an Committer.
+:::
+
+As long as anyone contributes to the GraphAr project, you are the officially
recognized Contributor of the GraphAr project.
+There is no exact standard for growing from Contributor to Committer. There is
also no expected timetable, but Committer candidates are generally long-term
active contributors.
+Becoming Committer does not require considerable contributions to architecture
improvements.
+Or how many lines of code contributions, contributing code, contributing
documents, participating in discussions on the mailing list, helping answer
questions, etc., are all ways to increase your influence.
+
+List of potential contributions (in no particular order):
+- Submit the bugs, features, and improvements you found to the issue.
+- Update the official documentation so that the project documentation is the
most recent, the best practices for writing GraphAr, and various valuable
documents for feature analysis.
+- Perform test and report test results, performance test and performance
comparison test of any modules, etc.
+- 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
suggestions.
+- Review issues on GitHub and maintain the latest status of issues, such as
outdated closing issues, changing issue error information, etc.
+- Guide new contributors and be familiar with the community process.
+- Publish speeches and blogs about GraphAr, and add these to GraphAr's
official website.
+- Any contribution that is beneficial to the development of the InLong
community.
+- ......
+
+For more reference: [ASF official
document](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, do it (and add them to the list).
+Pleasant manners and dedication are all you need to have a positive impact on
the GraphAr project.
+We are inviting you to become Committer results from your long-term and stable
interaction with the community, and it means the trust and recognition of the
GraphAr 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 contribute a lot to the community, you can be
promoted to a PPMC member of the GraphAr project.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
