This is an automated email from the ASF dual-hosted git repository.
dockerzhang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/inlong-website.git
The following commit(s) were added to refs/heads/master by this push:
new 088b848f09 [INLONG-647][Doc] Update the community guide (#648)
088b848f09 is described below
commit 088b848f099e9d48002b5d1e6a4c32b6e754af7a
Author: Charles Zhang <[email protected]>
AuthorDate: Wed Dec 14 15:20:26 2022 +0800
[INLONG-647][Doc] Update the community guide (#648)
---
community/how-to-become-a-committer.md | 12 +-
.../how-to-maintain-3rd-party-dependencies.md | 2 +-
community/how-to-report-issues.md | 24 +-
community/how-to-subscribe.md | 62 +++--
community/how-to-verify.md | 2 +-
community/how-to-vote-a-committer-pmc.md | 253 +++++++++++----------
.../current/how-to-become-a-committer.md | 36 +--
.../current/how-to-contribute.md | 77 ++++---
.../current/how-to-report-issues.md | 20 +-
.../current/how-to-subscribe.md | 65 +++---
.../current/how-to-vote-a-committer-pmc.md | 248 ++++++++++----------
11 files changed, 409 insertions(+), 392 deletions(-)
diff --git a/community/how-to-become-a-committer.md
b/community/how-to-become-a-committer.md
index bcf82bc66e..7b38e2a7ac 100644
--- a/community/how-to-become-a-committer.md
+++ b/community/how-to-become-a-committer.md
@@ -3,10 +3,12 @@ title: How to Become a Committer or PMC
sidebar_position: 4
---
-> [Apache InLong](https://inlong.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.
-> Apache InLong Committer has the permission to write the InLong code base and
can merge PR.
-> Anyone who has made enough contributions to the community and gained enough
trust can become an Apache InLong Committer.
+:::note
+[Apache InLong](https://inlong.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.
+Apache InLong Committer has the permission to write the InLong code base and
can merge PR.
+Anyone who has made enough contributions to the community and gained enough
trust can become an Apache InLong Committer.
+:::
As long as anyone contributes to the InLong project, you are the officially
recognized Contributor of the InLong 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.
@@ -18,7 +20,7 @@ List of potential contributions (in no particular order):
- Update the official documentation so that the project documentation is the
most recent, the best practices for writing InLong, 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].
+- 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.
diff --git a/community/how-to-maintain-3rd-party-dependencies.md
b/community/how-to-maintain-3rd-party-dependencies.md
index 1e58118e6a..68c8ab564b 100644
--- a/community/how-to-maintain-3rd-party-dependencies.md
+++ b/community/how-to-maintain-3rd-party-dependencies.md
@@ -1,5 +1,5 @@
---
-title: How to maintain third-party dependencies in a project
+title: How to Maintain Third-party Dependencies
sidebar_position: 9
---
diff --git a/community/how-to-report-issues.md
b/community/how-to-report-issues.md
index abf8c4eccf..3fb64c9e59 100644
--- a/community/how-to-report-issues.md
+++ b/community/how-to-report-issues.md
@@ -29,18 +29,18 @@ Make sure the Project is set to InLong. Set the issue type
field appropriately b
- Improvement
- Umbrella
-For Summary, please provide a detailed title e.g. `[Bug][Dataproxy] Repeated
registration jmx metric bean` instead of `Dataproxy registration error`.
-
-| Component |
Description
|
-|:----------------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------:|
-| InLong Agent | data collection agent, supports reading
regular logs from specified directories or files and reporting data one by one.
In the future, DB collection capabilities will also be expanded.
|
-| InLong Dataproxy | a Proxy component based on Flume-ng,
supports data transmission blocking, placing retransmission, and has the
ability to forward received data to different MQ (message queues).
|
-| InLong TubeMQ | Tencent's self-developed message queuing service,
focuses on high-performance storage and transmission of massive data in big
data scenarios and has a relatively good core advantage in mass practice and
low cost. |
-| InLong Sort | after consuming data from
different MQ services, perform ETL processing, and then aggregate and write
the data into Apache Hive, ClickHouse, Hbase, IceBerg, etc.
|
-| InLong Manager | provides
complete data service management and control capabilities, including metadata,
OpenAPI, task flow, authority, etc.
|
-| InLong Dashboard | a
front-end page for managing data access, simplifying the use of the entire
InLong control platform.
|
-| InLong Audit | performs real-time
audit and reconciliation on the incoming and outgoing traffic of the Agent,
DataProxy, and Sort modules of the InLong system.
|
-| InLong SDK |
include DataProxy SDK, Sort SDK etc.
|
+For Summary, please provide a detailed title e.g. `[Bug][DataProxy] Repeated
registration jmx metric bean` instead of `Dataproxy registration error`.
+
+| Component | Description
|
+|:---------------:|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Agent | data collection agent, supports reading regular logs from
specified directories or files and reporting data one by one. In the future,
DB collection capabilities will also be expanded. |
+| DataProxy | a Proxy component based on Flume-ng, supports data
transmission blocking, placing retransmission, and has the ability to forward
received data to different MQ (message queues).
|
+| TubeMQ | Tencent's self-developed message queuing service, focuses
on high-performance storage and transmission of massive data in big data
scenarios and has a relatively good core advantage in mass practice and low
cost. |
+| Sort | after consuming data from different MQ services, perform
ETL processing, and then aggregate and write the data into Apache Hive,
ClickHouse, Hbase, IceBerg, etc.
|
+| Manager | provides complete data service management and control
capabilities, including metadata, OpenAPI, task flow, authority, etc.
|
+| Dashboard | a front-end page for managing data access, simplifying
the use of the entire InLong control platform.
|
+| Audit | performs real-time audit and reconciliation on the
incoming and outgoing traffic of the Agent, DataProxy, and Sort modules of the
InLong system.
|
+| SDK | include DataProxy SDK, Sort SDK etc.
|
The Affects Versions/s field can be set to the earliest version of InLong
where you have seen the bug. If you are not sure then just leave it empty.
diff --git a/community/how-to-subscribe.md b/community/how-to-subscribe.md
index fa0c3e24b7..0c42e99110 100644
--- a/community/how-to-subscribe.md
+++ b/community/how-to-subscribe.md
@@ -1,32 +1,30 @@
----
-title: How to subscribe mail list
-sidebar_position: 3
----
-
-Mailing lists are a form of communication used by the Apache
community，Generally speaking，Many things in the Apache community are hosted by
mailing lists，For example: project q&A, technical discussion, transaction
decision, release vote, etc，By subscribing, you can get the first update of the
InLong community and keep up with the community.
-
-## Mail list
-
-|name|description|Subscribe|Unsubscribe|archive|
-|:-----|:--------|:------|:-------|:-----|
-| [[email protected]](mailto:[email protected]) | community activity
information | [subscribe](mailto:[email protected]) |
[unsubscribe](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/inlong-dev) |
-| [[email protected]](mailto:[email protected]) | Code repo
update information | [subscribe](mailto:[email protected]) |
[unsubscribe](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/inlong-commits) |
-
-## Subscribe to the mail list
-**For example,Take subscribing to the [email protected] mailing list**
-
-The steps are as follows：
- 1. Send an email without any content or subject:
`[email protected]`
- 2. Wait until you receive an email with the subject line `confirm subscribe
to [email protected]` (if you have not received it for a long time, please
confirm whether the email is blocked by your email, if you have not been
blocked and will receive a reply for a long time, return to step 1)
- 3. Reply directly to the email without changing the subject line or adding
the email content.
- 4. Wait until you receive an email with the subject line `WELCOME to
[email protected]` .
- 5. If you receive an email from (4), you have successfully subscribed to the
email. To initiate a discussion, you can send an email directly to
`[email protected]`, which will be sent to everyone who subscribed to the
mailing list.
-
-## Unsubscribe from the mail list
-The steps for unsubscribing to a mailing list are similar to those for
subscribing to a mailing list:：
-1. Send an email without any content or subject to:
`[email protected]`
-2. Wait until you receive an email with the subject line `confirm unsubscribe
from [email protected]`
-3. Reply directly to the email without changing the subject line or adding the
email content
-4. Wait until you receive an email with the subject line `GOODBYE from
[email protected]`
-5. Unsubscribe success
-
+---
+title: How to Subscribe Mail List
+sidebar_position: 3
+---
+
+Mailing lists are a form of communication used by the Apache
community，Generally speaking，Many things in the Apache community are hosted by
mailing lists，For example: project q&A, technical discussion, transaction
decision, release vote, etc，By subscribing, you can get the first update of the
InLong community and keep up with the community.
+
+## Mail list
+
+| name |
description | Subscribe
| Unsubscribe |
archive |
+|:---------------------------------------------------------------:|:--------------------------------:|:---------------------------------------------------------:|:-------------------------------------------------------------:|:----------------------------------------------------------------------:|
+| [[email protected]](mailto:[email protected]) |
community activity information |
[subscribe](mailto:[email protected]) |
[unsubscribe](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/inlong-dev) |
+| [[email protected]](mailto:[email protected]) | Code
repo update information |
[subscribe](mailto:[email protected]) |
[unsubscribe](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/inlong-commits) |
+
+## Subscribe to the mail list
+For example,Take subscribing to the [email protected] mailing list, the
steps are as follows：
+- Send an email without any content or subject:
`[email protected]`
+- Wait until you receive an email with the subject line `confirm subscribe to
[email protected]` (if you have not received it for a long time, please
confirm whether the email is blocked by your email, if you have not been
blocked and will receive a reply for a long time, return to step 1)
+- Reply directly to the email without changing the subject line or adding the
email content.
+- Wait until you receive an email with the subject line `WELCOME to
[email protected]` .
+- If you receive an email from `dev`, you have successfully subscribed to the
email. To initiate a discussion, you can send an email directly to
`[email protected]`, which will be sent to everyone who subscribed to the
mailing list.
+
+## Unsubscribe from the mail list
+The steps for unsubscribing to a mailing list are similar to those for
subscribing to a mailing list:：
+- Send an email without any content or subject to:
`[email protected]`
+- Wait until you receive an email with the subject line `confirm unsubscribe
from [email protected]`
+- Reply directly to the email without changing the subject line or adding the
email content
+- Wait until you receive an email with the subject line `GOODBYE from
[email protected]`
+- Unsubscribe success
+
diff --git a/community/how-to-verify.md b/community/how-to-verify.md
index 5e23bb926c..74491d319f 100644
--- a/community/how-to-verify.md
+++ b/community/how-to-verify.md
@@ -1,5 +1,5 @@
---
-title: How to verify release candidate
+title: How to Verify Release Candidate
sidebar_position: 7
---
diff --git a/community/how-to-vote-a-committer-pmc.md
b/community/how-to-vote-a-committer-pmc.md
index afe3abb78a..9c402efffb 100644
--- a/community/how-to-vote-a-committer-pmc.md
+++ b/community/how-to-vote-a-committer-pmc.md
@@ -1,151 +1,160 @@
---
-title: How to vote a Committer or PMC
+title: How to Vote a Committer or PMC Member
sidebar_position: 5
---
## Initiate discussion in the community private mailing group
- Any InLong PMC member can initiate a voting discussion.
- After PMC finds any valuable contributions from community contributors and
obtains the consent of the candidate, they can initiate a discussion on
InLong'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. PMC members will fully express their views on the
proposed email.
- The following is a sample discussion email:
- ```shell
- [DISCUSS] YYYYY as an InLong XXXXXX
-
- I nominate YYYYY as an InLong XXXXXX
-
- Judging from the contributions in recent months, YYYYY has submitted many
implementations[1],[2] to the project and improved the management module for
the project. During the optimization and improvement period of the project, it
is hoped that more people will participate in the actual project optimization
and improvement, to let the project more perfect and easier to use.
-
- So I nominated YYYYY as XXXXXX of the InLong project.
-
- 1. https://github.com/apache/inlong/issues/created_by/YYYYY
- 2. https://github.com/apache/inlong/commits?author=YYYYY
- ```
-
+Any InLong PMC member can initiate a voting discussion.
+After PMC finds any valuable contributions from community contributors and
obtains the consent of the candidate, they can initiate a discussion on
InLong'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. PMC members will fully express their views on the
proposed email.
+The following is a template discussion email:
+```shell
+[DISCUSS] ${Candidate_Full_Name} as an InLong a ${Committer or PMC Member}
+
+I nominate ${Candidate_Full_Name} as an InLong a ${Committer or PMC Member}
+
+Judging from the contributions in recent months, ${Candidate_Full_Name} has
submitted many implementations[1],[2] to the project and improved the
management module for the project. During the optimization and improvement
period of the project, it is hoped that more people will participate in the
actual project optimization and improvement, to let the project more perfect
and easier to use.
+
+So I nominated ${Candidate_Full_Name} as a ${Committer or PMC Member} of the
InLong project.
+
+1. https://github.com/apache/inlong/issues/created_by/${Candidate_GitHub_ID}
+2. https://github.com/apache/inlong/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
PMC election vote on InLong's 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 sample poll email:
- ```shell
- [VOTE] YYYYY as an InLong XXXXXX
-
- Judging from the contributions in recent months, YYYYY has submitted many
implementations[1],[2],[3] to the project and improved the management module
for the project. During the optimization and improvement period of the project,
it is hoped that more people will participate in the actual project
optimization and improvement, to let the project more perfect and easier to use.
- I think making him a XXXXXX will be a recognition of his outstanding work
for InLong. So, I am happy to call VOTE to accept YYYYY as an InLong XXXXXX.
-
- 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 InLong:
- 1. Issues: https://github.com/apache/inlong/pulls?q=YYYYY
- 2. PRs : https://github.com/apache/inlong/issues?q=YYYYY
- 3. Others: https://xxx.com/xxx/xxx/?q=YYYYY
- ```
+If the discussion email does not receive the disagreement information within
the specified time, the poll initiator needs to initiate a Committer or PMC
Member election vote on InLong's 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
+[VOTE] ${Candidate_Full_Name} as an InLong a ${Committer or PMC Member}
+
+Judging from the contributions in recent months, ${Candidate_Full_Name} has
submitted many implementations[1],[2],[3] to the project and improved the
management module for the project. During the optimization and improvement
period of the project, it is hoped that more people will participate in the
actual project optimization and improvement, to let the project more perfect
and easier to use.
+I think making him a a ${Committer or PMC Member} will be a recognition of his
outstanding work for InLong. So, I am happy to call VOTE to accept
${Candidate_Full_Name} as an InLong a ${Committer or PMC 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 InLong:
+1. Issues: https://github.com/apache/inlong/pulls?q=${Candidate_GitHub_ID}
+2. PRs : https://github.com/apache/inlong/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 sample vote summary email:
- ```shell
- [RESULTS][VOTE] YYYYY as an InLong XXXXXX
-
- Hi everyone,
+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
+[RESULTS][VOTE] ${Candidate_Full_Name} as an InLong a ${Committer or PMC
Member}
- The vote for "YYYYY as an InLong XXXXXX" has PASSED and closed now.
+Hi everyone,
- The result is as follows:
+The vote for "${Candidate_Full_Name} as an InLong a ${Committer or PMC
Member}" has PASSED and closed now.
- 3 PMC +1 Votes
- - aaa
- - bbb
- - ccc
+The result is as follows:
- Vote thread:
- https://lists.apache.org/thread/aaaaaxxxx
+3 PMC Member +1 Votes
+- ${the name 1 of PMC Member}
+- ${the name 2 of PMC Member}
+- ${the name 3 of PMC Member}
- Then I'm going to invite YYYYY to join us.
+Vote thread:
+${vote_thread_url}
- Thanks for everyone's support!
- ```
- Note: If it is not passed, the result is "The vote for "YYYYY as an InLong
XXXXXX" has FAILED and closed now."
+Then I'm going to invite ${Candidate_Full_Name} to join us.
-## Newly added PMC notification email
- This step is only processed for the PMC that passed the vote. If the
election is Committer, this step is skipped and not executed.
- Voting initiators need to send notification emails to Board’s mailing group
and wait at least 72 hours; email owners send [email protected] and CC
[email protected]; Board will analyze compliance Until there is no
doubt.
- The following is an example of a new PMC notification email:
- ```shell
- [NOTICE] YYYYY for Apache InLong PMC
-
- Hi everyone,
+Thanks for everyone's support!
+```
- Apache InLong proposes to invite YYYYY to join the PMC.
+:::caution
+If it is not passed, the result is "The vote for "${Candidate_GitHub_ID} as an
InLong a ${Committer or PMC Member}" has FAILED and closed now."
+:::
- The vote result is available here: https://lists.apache.org/...
-
- Thanks!
- ```
+## Newly added PMC Member notification email
+This step is only processed for the PMC Member that passed the vote. If the
election is Committer, this step is skipped and not executed.
+Voting initiators need to send notification emails to Board’s mailing group
and wait at least 72 hours; email owners send [email protected] and CC
[email protected]; Board will analyze compliance Until there is no
doubt.
+The following is an example of a new PMC Member notification email:
+```shell
+[NOTICE] ${Candidate_Full_Name} for Apache InLong PMC
-## Initiate invitation email
- After the result summary email is sent, the poll initiator must send an
invitation email to the candidates.
- The invitation email is sent to the invitee with a CC to
[email protected]; the invited candidate must reply to accept or
decline the invitation through the specified email address.
- The following is an example of an email inviting candidates:
- ```shell
- [Invitation] Invitation to join Apache InLong as a XXXXXX
-
- Hi YYYYY,
-
- In recognition of your contributions to Apache InLong, the InLong PMC
- has recently voted to add you as a XXXXXX. The XXXXXX role gives
- you access to merge patches into Apache InLong and is also a
- stepping-stone towards membership in the
- Project Management Committee (PMC). We hope that you accept
- this invitation and continue to help us make Apache InLong better.
-
- If you'd like to accept, you will need to send an Individual
- Contributor License Agreement (ICLA) to [email protected], CCing
- [email protected], and request an Apache account name as
- described at http://www.apache.org/dev/new-committers-guide.html if
- you don’t already have one, once you get an account name, or if you
- have one already, please email it to me.
-
- NOTICE: when you fill out ICLA file, the value of preferred Apache id(s)
- needs to be a valid ID, including:
- 1. The ID must not already be in use in
https://people.apache.org/committer-index.html;
- 2. The characters "-" and "_" are not allowed in id;
- 3. The id must consist of lowercase alphanumeric characters only,
- start with an alphabetic character, have a minimum length of 3
characters,
- and have no special characters.
+Hi everyone,
+
+Apache InLong proposes to invite ${Candidate_Full_Name} to join the PMC.
- With the expectation of your acceptance, welcome!
+The vote result is available here: ${vote_thread_url}
- The Apache InLong PMC
- ```
+Thanks!
+```
+
+## Initiate invitation email
+After the result summary email is sent, the poll initiator must send an
invitation email to the candidates.
+The invitation email is sent to the invitee with a CC to
[email protected]; the invited candidate must reply to accept or
decline the invitation through the specified email address.
+The following is an example of an email inviting candidates:
+```shell
+[Invitation] Invitation to join Apache InLong as a a ${Committer or PMC Member}
+
+Hi ${Candidate_Full_Name},
+
+In recognition of your contributions to Apache InLong, the InLong PMC
+has recently voted to add you as a a ${Committer or PMC Member}. The a
${Committer or PMC Member} role gives
+you access to merge patches into Apache InLong and is also a
+stepping-stone towards membership in the
+Project Management Committee (PMC). We hope that you accept
+this invitation and continue to help us make Apache InLong better.
+
+If you'd like to accept, you will need to send an Individual
+Contributor License Agreement (ICLA) to [email protected], CCing
[email protected], and request an Apache account name as
+described at http://www.apache.org/dev/new-committers-guide.html if
+you don’t already have one, once you get an account name, or if you
+have one already, please email it to me.
+
+NOTICE: when you fill out ICLA file, the value of preferred Apache id(s)
+ needs to be a valid ID, including:
+ 1. The ID must not already be in use in
https://people.apache.org/committer-index.html;
+ 2. The characters "-" and "_" are not allowed in id;
+ 3. The id must consist of lowercase alphanumeric characters only,
+ start with an alphabetic character, have a minimum length of 3
characters,
+ and have no special characters.
+
+With the expectation of your acceptance, welcome!
+
+The Apache InLong PMC
+```
+
+:::note
+When signing the ICLA, the candidate needs to write the project name of
“Apache InLong” in the "notify project:" column, so that the candidate account
will be added to the list of corresponding project personnel by Apache.
+:::
## Processing after accepting the invitation
- Create an Apache account and add the candidate account to the project.
- After the candidate accepts the invitation, if the candidate does not have
an apache email account, the voting initiator needs to assist the candidate to
create an apache account according to the guidelines.
- When signing the ICLA, the candidate needs to write the project name of
“Apache InLong” in the "notify project:" column, so that the candidate account
will be added to the list of corresponding project personnel by Apache.
- The voting initiator needs to add project team members, open a permission
account for the apache project, and confirm that the candidate’s Apache account
has been added to the project address:
http://people.apache.org/phonebook.html?project=inlong.
+Create an Apache account and add the candidate account to the project.
+After the candidate accepts the invitation, if the candidate does not have an
apache email account, the voting initiator needs to assist the candidate to
create an apache account according to the guidelines.
+The voting initiator needs to add project team members, open a permission
account for the apache project, and confirm that the candidate’s Apache account
has been added to the project address:
http://people.apache.org/phonebook.html?project=inlong.
## ANNOUNCE to the community
- After the above steps are completed, the vote initiator must send a
notification email to the [email protected] mail group. The following is a
sample notification email:
+After the above steps are completed, the vote initiator must send a
notification email to the [email protected] mail group. The following is a
template notification email:
+```shell
+[ANNOUNCE] New a ${Committer or PMC Member}: ${Candidate_Full_Name}
- ```shell
- [ANNOUNCE] New XXXXXX: YYYYY
-
- Hi everyone,
-
- The Project Management Committee(PMC) for Apache InLong has invited YYYYY
to become a XXXXXX and we are pleased to announce that he has accepted.
+Hi everyone,
- YYYYY is being active in the InLong community, and we are glad to see his
more interactions with the community in the future.
-
- Welcome YYYYY, and please enjoy your journey.:)
+The Project Management Committee(PMC) for Apache InLong has invited
${Candidate_Full_Name} to become a a ${Committer or PMC Member} and we are
pleased to announce that he has accepted.
+
+${Candidate_Full_Name} is being active in the InLong community, and we are
glad to see his more interactions with the community in the future.
- Thanks!
-
- ```
+Welcome ${Candidate_Full_Name}, and please enjoy your journey.:)
+
+Thanks!
+
+```
-At this point, the entire process is completed, and the candidate officially
becomes the Committer or PMC of the project.
+At this point, the entire process is completed, and the candidate officially
becomes the Committer or PMC Member of the project.
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-become-a-committer.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-become-a-committer.md
index 3d114645dd..e21d36dde9 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-become-a-committer.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-become-a-committer.md
@@ -1,34 +1,36 @@
---
-title: 如何成为Committer
+title: 如何成为 Committer
sidebar_position: 4
---
-> Apache InLong是完全按照Apache的规则来构建社区的，Apache
Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
-Apache InLong
Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong
Committer。
+:::note
+[Apache InLong](https://inlong.apache.org) 是完全按照 Apache 的规则来构建社区的，Apache
Committer 是 ASF（Apache 软件基金会）中用来表示提交特定项目的人的术语，
+Apache InLong Committer 拥有 InLong 代码库的写权限，可以合并
PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为 Apache InLong Committer。
+:::
-任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
-也没有任何预期的时间表，但是Committer的候选人一般都是长期活跃的贡献者，成为Committer并没有要求必须有巨大的架构改进贡献，
+任何人只要对 InLong 项目做了贡献，那你就是官方承认的 InLong 项目的 Contributor 了，从 Contributor 成长为
Committer 并没有一个确切的标准，
+也没有任何预期的时间表，但是 Committer 的候选人一般都是**长期活跃的贡献者**，成为 Committer 并没有要求必须有巨大的架构改进贡献，
或者多少行的代码贡献，贡献代码、贡献文档、参与邮件列表的讨论、帮助回答问题等等都提升自己影响力的方式。
潜在贡献清单（无特定顺序）：
-- 提交自己发现的Bug、特性、改进到issue
-- 更新官方文档使项目的文档是最近的、撰写InLong的最佳实践、特性剖析的各种对用户有用的文档
-- 执行测试并报告测试结果，性能测试与其他Agent、MQ等模块的性能对比测试等
+- 提交自己发现的 Bug、特性、改进到 Issue
+- 更新官方文档使项目的文档是最近的、撰写 InLong 的最佳实践、特性剖析的各种对用户有用的文档
+- 执行测试并报告测试结果，性能测试与其他项目性能对比测试等
- 发布版本时，积极参与投票
-- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
+- 参与邮件列表中的讨论，一般会有以 `[DISCUSS]` 开头的邮件
- 回答用户或开发人员在邮件列表中的提问
-- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
-- 对GitHub上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
+- 审查(Review) 其他人的工作（包括代码和非代码）并发表你自己的建议
+- 对 GitHub 上的 Issue 进行审查，维护 Issue 为最新状态，比如：关闭过时的 Issue、更改 Issue 的错误信息等
- 指导新加入的贡献者，熟悉社区流程
-- 发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站
-- 有利于InLong社区发展的任何贡献
+- 发表关于 InLong 的演讲和博客，并将这些添加到 Issue 的官方网站
+- 有利于 Issue 社区发展的任何贡献
- ......
更多可以参考：[ASF官方文档](https://community.apache.org/contributors/)
并不是每个人都能完成这个清单上的所有（甚至任何）项目。如果你想用其他方式来做贡献，那就去做吧（并把它们添加到列表中）。
-愉快的举止和乐于奉献的精神是您对InLong项目产生积极影响所需要的全部。
-邀请您成为Committer是您与社区长期稳定互动的结果，是InLong社区对您的信任和认可。
+愉快的举止和乐于奉献的精神是您对 InLong 项目产生积极影响所需要的全部。
+邀请您成为 Committer 是您与社区长期稳定互动的结果，是 InLong 社区对您的信任和认可。
-Committer有义务审查(Review)和合并(merge)其他人提交的PR，版本发布时测试和投票候选版本，参与特性设计方案的讨论以及其他类型的项目贡献。
-当你足够活跃且对社区的贡献比较大后，就可以晋升为InLong项目的PMC成员。
+Committer 有义务审查(Review)和合并(Merge)其他人提交的
PR，版本发布时测试和投票候选版本，参与特性设计方案的讨论以及其他类型的项目贡献。
+当你足够活跃且对社区的贡献比较大后，就可以晋升为 InLong 项目的 PMC 成员。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute.md
index 913819cd56..bcc64b31e8 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-contribute.md
@@ -3,70 +3,69 @@ title: 如何参与贡献
sidebar_position: 1
---
-Apache InLong社区欢迎大家为Apache InLong做贡献，您可以通过很多方式为InLong项目成长贡献一份力量：
- -
贡献文档：浏览文档可以加深您对InLong的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或[联系我们](mailto:[email protected])
- - 贡献代码：欢迎大家为InLong社区贡献代码
- -
欢迎您认领Open状态的[Issues](https://github.com/apache/inlong/issues)和未完成的特性，提交PR，成为贡献者之一
- - 如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在Issues中记录
- - 参与邮件讨论：您可以参与dev邮件列表的任何讨论，或者发送任何疑问到dev邮件列表
- - 参与Issue讨论：您可以在任一[Issues](https://github.com/apache/inlong/issues)下发表您的建议
- -
Review代码：您可以在[GitHub](https://github.com/apache/inlong/pulls)上看到所有贡献者提交的PR，您可以Review他们的代码并发表您的建议
-> 欢迎大家提交Bug反馈、改进、新功能及PR，具体参与贡献流程可参考该指引。
+Apache InLong 社区欢迎大家参与贡献，您可以通过很多方式为 InLong 项目贡献一份力量：
+ - 贡献文档：浏览文档可以加深您对 InLong
的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或[联系我们](mailto:[email protected])
+ - 贡献代码：欢迎大家为 InLong 社区贡献代码
+ - 欢迎您认领 Open 状态的 [Issues](https://github.com/apache/inlong/issues)
和未完成的特性，提交 PR，成为贡献者之一
+ - 如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在 Issues 中记录
+ - 参与邮件讨论：您可以参与 dev 邮件列表的任何讨论，或者发送任何疑问到 dev 邮件列表
+ - 参与 Issue 讨论：您可以在任一 [Issues](https://github.com/apache/inlong/issues) 下发表您的建议
+ - Review 代码：您可以在 [GitHub](https://github.com/apache/inlong/pulls) 上看到所有贡献者提交的
PR，您可以 Review 他们的代码并发表您的建议
## 主要链接
- 官网：https://inlong.apache.org/
- 代码库：https://github.com/apache/inlong
- 官网代码库：https://github.com/apache/inlong-website
-- GitHub Issue任务管理：https://github.com/apache/inlong/issues
+- GitHub Issue 任务管理：https://github.com/apache/inlong/issues
-## 订阅InLong邮件列表
- 详见[如何订阅邮件列表](how-to-subscribe.md)
+## 订阅 InLong 邮件列表
+详见[如何订阅邮件列表](how-to-subscribe.md)
-## 提交Bug反馈/特性/改进/文档
+## 提交 Bug 反馈/特性/改进/文档
+Apache InLong 使用 GitHub 对 InLong
相关的任务进行管理，详见：https://github.com/apache/inlong/issues
-> Apache
InLong使用GitHub对InLong相关的任务进行管理，详见：https://github.com/apache/inlong/issues
+### 创建 Issue
+详见 [GitHub Issue 使用指南](https://github.com/apache/inlong/issues/new/choose)
-### 创建issue
-详见[GitHub Issue使用指南](https://github.com/apache/inlong/issues/new/choose)
-
-### 如何提交Bug/特性/改进
+### 如何提交 Bug/特性/改进
在您提交特性/改进前，应该注意以下几点：
- - 请先确认该特性/改进是否被其他人已经提交
- - 一个通俗易懂的标题来阐述你提交的Bug/提交特性/改进
- - 如果是Bug则详细描述该bug产生的原因，如果能够复现，请尽量提供完整的重现步骤
- - 如果是特性，那么该特性应该有广泛的适用性，适用于大部分用户，最好能够提供详尽的设计文档
- - 如果是改进，尽可能描述清楚此改进所带来的益处
- -
如果新增模块或者修改pom.xml文件内容，需要进行第三方依赖的LICENSE维护，详情参考[如何维护第三方依赖](how-to-maintain-3rd-party-dependencies.md)
+- 请先确认该特性/改进是否被其他人已经提交
+- 一个通俗易懂的标题来阐述你提交的 Bug/提交特性/改进
+- 如果是Bug则详细描述该 Bug 产生的原因，如果能够复现，请尽量提供完整的重现步骤
+- 如果是特性，那么该特性应该有广泛的适用性，适用于大部分用户，最好能够提供详尽的设计文档
+- 如果是改进，尽可能描述清楚此改进所带来的益处
+- 如果新增模块或者修改 pom.xml 文件内容，需要进行第三方依赖的 LICENSE
维护，详情参考[如何维护第三方依赖](how-to-maintain-3rd-party-dependencies.md)
具体步骤：
-- 创建issue，描述清楚问题
-- 如果你要解决该issue则将issue assign到自己名下，如果你仅仅是提交Bug/特性/改进，并没有时间去贡献代码，则assignne设置为空
-- 如果是比较大的特性/改进，尽量先输出设计文档，供其他人review
+- 创建 Issue，描述清楚问题
+- 如果你要解决该 Issue 则将 Issue Assign 到自己名下，如果你仅仅是提交 Bug/特性/改进，并没有时间去贡献代码，则
Assignees 设置为空
+- 如果是比较大的特性/改进，尽量先输出设计文档，供其他人 Review
- 编码，编码完成后，提交代码，参考：[代码提交指南](how-to-commit.md)
### 如何贡献文档
-InLong项目的所有文档将在[官网](https://inlong.apache.org/)展示，所有的文档都保存在官网代码库的[docs](https://github.com/apache/inlong-website/tree/master/docs)文件夹下。
+InLong 项目的所有文档将在[官网](https://inlong.apache.org/)展示，所有的文档都保存在官网代码库的
[Docs](https://github.com/apache/inlong-website/tree/master/docs) 文件夹下。
贡献的文档包括：
-- 编写与InLong相关的文档
+- 编写与 InLong 相关的文档
- 将中文文档翻译成英文文档
- 将英文文档翻译成中文文档
具体步骤：
- 查看官网，确认你认为需要补充的文档，包含中英文文档
-- 创建issue，描述清楚问题, Component请选择：website
+- 创建 [Issue](https://github.com/apache/inlong-website/issues)，描述清楚问题,
Component 请选择：`Doc`
- 撰写文档，完成后提交文档，参考：[代码提交指南](how-to-commit.md)
-## 如何认领Bug/特性/改进/文档
-
-在InLong的issue列表中，有很多由其他人创建的issue并未被修复，如果你感兴趣的话，可以认领这些issue。认领步骤如下：
- - 在该issue下留言，表达想认领该任务的想法
- - 如果提交者没有意见，则将该issue assign到自己名下并及时更新进度
- - 如果是比较大的特性，尽量先输出设计文档，供其他人review
- - 开发代码并提交代码至github，提交代码流程参考：[代码提交指南](how-to-commit.md)
+## 如何认领 Bug/特性/改进/文档
+在 InLong 的 [Issue](https://github.com/apache/inlong-website/issues)
列表中，有很多由其他人创建的 Issue 并未被修复，如果你感兴趣的话，可以认领这些 Issue。认领步骤如下：
+- 在该 Issue 下留言，表达想认领该任务的想法
+- 如果提交者没有意见，则将该 Issue Assign 到自己名下并及时更新进度
+- 如果是比较大的特性，尽量先输出设计文档，供其他人 Review
+- 开发代码并提交代码至 GitHub，提交代码流程参考：[代码提交指南](how-to-commit.md)
-**如果你是第一次参与InLong项目，可能该issue无法Assign给自己，此时你可以发邮件至：[email protected]或联系InLong的PMC申请加入InLong的contributor列表，加入后即可Assign其他issue给自己**
+:::note
+如果你是第一次参与 InLong 项目，可能该 Issue 无法 Assign 给自己，此时你可以发邮件至：[email protected]
或联系 InLong 的 PMC 申请加入 InLong 的 Contributor 列表，加入后即可 Assign 其他 Issue 给自己
+:::
-您的任何贡献都可以帮助Apache InLong项目成长，如果您刚接触InLong，您可以先从简单的任务入手，循序渐进，甚至可以逐渐成长为Apache
InLong的Committer；
+您的任何贡献都可以帮助 Apache InLong 项目成长，如果您刚接触 InLong，您可以先从简单的任务入手，循序渐进，甚至可以逐渐成长为
Apache InLong 的 Committer。
## 如何报告安全问题
InLong 社区非常关心安全问题，并将积极解决任何安全问题作为重中之重。 我们遵循 Apache 安全指南来处理安全问题，请参阅 Apache 文档关于
[处理安全问题](https://www.apache.org/security/)。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-report-issues.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-report-issues.md
index dfc162a7a0..e8c77c517e 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-report-issues.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-report-issues.md
@@ -32,16 +32,16 @@ Apache InLong 项目使用 GitHub Issues 来跟踪所有问题。 这些包括
对于摘要，请提供详细的标题，例如 `[Bug][Dataproxy] Repeated registration jmx metric bean` 而不是
`Dataproxy registration error`。
-| 组件 | 描述
|
-|:----------------:|:---------------------------------------------------------------------:|
-| InLong Agent | 数据采集 Agent，支持从指定目录或文件读取常规日志、逐条上报。后续也将扩展 DB
采集等能力。 |
-| InLong Dataproxy | 一个基于 Flume-ng 的 Proxy 组件，支持数据发送阻塞和落盘重发，拥有将接收到的数据转发到不同
MQ（消息队列）的能力。 |
-| InLong TubeMQ |
腾讯自研的消息队列服务，专注于大数据场景下海量数据的高性能存储和传输，在海量实践和低成本方面有着良好的核心优势。 |
-| InLong Sort | 对从不同的 MQ 消费到的数据进行 ETL 处理，然后汇聚并写入
Hive、ClickHouse、Hbase、Iceberg 等存储系统。 |
-| InLong Manager | 提供完整的数据服务管控能力，包括元数据、任务流、权限，OpenAPI等。
|
-| InLong Dashboard | 用于管理数据接入的前端页面，简化整个 InLong 管控平台的使用。
|
-| InLong Audit | 对 InLong 系统的 Agent、DataProxy、Sort
模块的入流量、出流量进行实时审计对账。 |
-| InLong SDK | 包括 DataProxy SDK, Sort SDK 等
|
+| 组件 | 描述
|
+|:---------------:|:----------------------------------------------------------------------|
+| Agent | 数据采集 Agent，支持从指定目录或文件读取常规日志、逐条上报。后续也将扩展 DB 采集等能力。
|
+| DataProxy | 一个基于 Flume-ng 的 Proxy 组件，支持数据发送阻塞和落盘重发，拥有将接收到的数据转发到不同
MQ（消息队列）的能力。 |
+| TubeMQ | 腾讯自研的消息队列服务，专注于大数据场景下海量数据的高性能存储和传输，在海量实践和低成本方面有着良好的核心优势。
|
+| Sort | 对从不同的 MQ 消费到的数据进行 ETL 处理，然后汇聚并写入
Hive、ClickHouse、Hbase、Iceberg 等存储系统。 |
+| Manage | 提供完整的数据服务管控能力，包括元数据、任务流、权限，OpenAPI 等。
|
+| Dashboard | 用于管理数据接入的前端页面，简化整个 InLong 管控平台的使用。
|
+| Audit | 对 InLong 系统的 Agent、DataProxy、Sort 模块的入流量、出流量进行实时审计对账。
|
+| SDK | 包括 DataProxy SDK, Sort SDK 等
|
影响版本字段可以设置为您发现错误的 InLong 的最早版本。 如果您不确定，则将其留空。
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md
index bc59375963..454c76d989 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md
@@ -1,34 +1,31 @@
----
-title: 订阅邮件列表
-sidebar_position: 3
----
-
-邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，
-订阅邮件后，你可以第一时间获取InLong社区的动态，可以与社区保持同步。
-
-## 邮件列表
-
-|名称|描述|订阅邮件|退订邮件|邮件归档|
-|:-----|:--------|:------|:-------|:-----|
-| [[email protected]](mailto:[email protected]) | 社区活动信息 |
[订阅](mailto:[email protected]) |
[退订](mailto:[email protected]) |
[归档](http://mail-archives.apache.org/mod_mbox/inlong-dev) |
-| [[email protected]](mailto:[email protected]) | 代码库更新信息 |
[订阅](mailto:[email protected]) |
[退订](mailto:[email protected]) |
[归档](http://mail-archives.apache.org/mod_mbox/inlong-commits) |
-
-
-
-## 订阅邮件列表
-**以订阅[email protected]邮件列表为例**
-
-具体步骤如下：
- 1. 发送一封不包含任何内容或主题的邮件到: `[email protected]`
- 2. 等待直到收到一封主题为 `confirm subscribe to [email protected]`
的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
- 3. 直接回复该邮件，不用修改主题和添加邮件内容。
- 4. 等待直到收到一封主题为 `WELCOME to [email protected]` 的邮件。
- 5.
收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往`[email protected]`发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
-
-## 退订邮件列表
-退订邮件列表的步骤与订阅邮件列表类似，具体步骤如下：
-1. 发送一封不包含任何内容或主题的邮件到: `[email protected]`
-2. 等待直到收到一封主题为 `confirm unsubscribe from [email protected]` 的邮件
-3. 直接回复该邮件，不用修改主题和添加邮件内容
-4. 等待直到收到一封主题为 `GOODBYE from [email protected]`的邮件
-5. 退订成功
+---
+title: 如何订阅邮件列表
+sidebar_position: 3
+---
+
+邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，
+订阅邮件后，你可以第一时间获取InLong社区的动态，可以与社区保持同步。
+
+## 邮件列表
+
+| 名称 |
描述 | 订阅邮件 |
退订邮件 |
邮件归档 |
+|:-------------------------------------------------------------:|:------------------------------:|:-------------------------------------------------------:|:-----------------------------------------------------------:|:------------------------------------------------------------------:|
+| [[email protected]](mailto:[email protected]) | community
activity information | [subscribe](mailto:[email protected])
| [unsubscribe](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/inlong-dev) |
+| [[email protected]](mailto:[email protected]) | Code repo
update information | [subscribe](mailto:[email protected]) |
[unsubscribe](mailto:[email protected]) |
[archive](http://mail-archives.apache.org/mod_mbox/inlong-commits) |
+
+
+## 订阅邮件列表
+以订阅 [email protected] 邮件列表为例，具体步骤如下：
+- 发送一封不包含任何内容或主题的邮件到: `[email protected]`
+- 等待直到收到一封主题为 `confirm subscribe to [email protected]`
的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
+- 直接回复该邮件，不用修改主题和添加邮件内容。
+- 等待直到收到一封主题为 `WELCOME to [email protected]` 的邮件。
+- 收到 `dev` 的邮件后，就说明订阅邮件成功，若想发起讨论，直接往 `[email protected]`
发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
+
+## 退订邮件列表
+退订邮件列表的步骤与订阅邮件列表类似，具体步骤如下：
+- 发送一封不包含任何内容或主题的邮件到: `[email protected]`
+- 等待直到收到一封主题为 `confirm unsubscribe from [email protected]` 的邮件
+- 直接回复该邮件，不用修改主题和添加邮件内容
+- 等待直到收到一封主题为 `GOODBYE from [email protected]`的邮件
+- 退订成功
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-pmc.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-pmc.md
index e7fa522c75..1a15dfb4bf 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-pmc.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-pmc.md
@@ -1,149 +1,159 @@
---
-title: 成为 InLong Committer 或 PMC 的投票过程
+title: 如何投票 Committer 或 PMC 成员
sidebar_position: 5
---
## 发起社区 Private 邮件组投票讨论
- 任何 InLong 的 PMC 成员都可以发起投票讨论，PMC 在发现社区贡献者任何有价值的贡献并取得候选人本人同意后，可以在 InLong 的
private 邮件列表发起讨论。
- 讨论邮件里提议者要把候选人的贡献说清楚，并且给出复核对应贡献的地址，便于大家讨论分析。
- 讨论邮件主送 [email protected] 邮箱，讨论将持续至少72个小时，项目 PMC 成员会针对提议邮件充分发表自己的看法。
- 如下是讨论邮件样例，其中 YYYYY 为候选人的 github ID，XXXXXX 为希望候选人成为的角色，包括
Committer，PMC，候选人也可以直接被提名为PMC：
- ```shell
- [DISCUSS] YYYYY as an InLong XXXXXX
-
- I nominate YYYYY as an InLong XXXXXX
-
- Judging from the contributions in recent months, YYYYY has submitted many
implementations[1],[2] to the project and improved the management module for
the project. During the optimization and improvement period of the project, it
is hoped that more people will participate in the actual project optimization
and improvement, to let the project more perfect and easier to use.
-
- So I nominated YYYYY as XXXXXX of the InLong project.
-
- 1. https://github.com/apache/inlong/issues/created_by/YYYYY
- 2. https://github.com/apache/inlong/commits?author=YYYYY
- ```
-
+任何 InLong 的 PMC 成员都可以发起投票讨论，PMC 在发现社区贡献者任何有价值的贡献并取得候选人本人同意后，可以在 InLong 的
Private 邮件列表发起讨论。
+讨论邮件里提议者要把候选人的贡献阐述清楚，并且给出复核对应贡献的地址，便于大家讨论分析。
+讨论邮件主送 [email protected] 邮箱，讨论将持续至少 72 个小时，项目 PMC 成员会针对提议邮件充分发表自己的看法。
+如下是讨论邮件模板：
+```shell
+[DISCUSS] ${Candidate_Full_Name} as an InLong a ${Committer or PMC Member}
+
+I nominate ${Candidate_Full_Name} as an InLong a ${Committer or PMC Member}
+
+Judging from the contributions in recent months, ${Candidate_Full_Name} has
submitted many implementations[1],[2] to the project and improved the
management module for the project. During the optimization and improvement
period of the project, it is hoped that more people will participate in the
actual project optimization and improvement, to let the project more perfect
and easier to use.
+
+So I nominated ${Candidate_Full_Name} as a ${Committer or PMC Member} of the
InLong project.
+
+1. https://github.com/apache/inlong/issues/created_by/${Candidate_GitHub_ID}
+2. https://github.com/apache/inlong/commits?author=${Candidate_GitHub_ID}
+```
+
+:::caution
+可以向候选人提前沟通获得其全名（Full_Name），替换模板中的 `${Candidate_Full_Name}`。
+:::
+
## 发起社区 Private 邮件组投票
- 如果讨论邮件在规定时间内没有收到分歧信息，投票发起者需要在 InLong 的 private 邮件列表发起 Committer 或 PMC 的选举投票。
- 投票邮件主送
[email protected]，至少持续72小时，至少要3票+1通过；如果0票或者有1票-1投票票则整个投票失败；如果发起-1投票，投票人需要把打分-1的原因说清楚，便于大家理解和知晓。
- 如下是投票邮件样例，其中 YYYYY 为候选人的 github ID，XXXXXX 为希望候选人成为的角色，包括
Committer，PMC，候选人也可以直接被提名为PMC：
- ```shell
- [VOTE] YYYYY as an InLong XXXXXX
-
- Judging from the contributions in recent months, YYYYY has submitted many
implementations[1],[2],[3] to the project and improved the management module
for the project. During the optimization and improvement period of the project,
it is hoped that more people will participate in the actual project
optimization and improvement, to let the project more perfect and easier to use.
- I think making him a XXXXXX will be a recognition of his outstanding work
for InLong. So, I am happy to call VOTE to accept YYYYY as an InLong XXXXXX.
-
- 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 InLong:
- 1. Issues: https://github.com/apache/inlong/pulls?q=YYYYY
- 2. PRs : https://github.com/apache/inlong/issues?q=YYYYY
- 3. Others: https://xxx.com/xxx/xxx/?q=YYYYY
- ```
+如果讨论邮件在规定时间内没有收到分歧信息，投票发起者需要在 InLong 的 Private 邮件列表发起 Committer 或 PMC 成员的选举投票。
+投票邮件主送 [email protected]，至少持续 72 小时，至少要 3 票 +1 通过；如果 0 票或者有 1 票 -1
投票票则整个投票失败；如果发起 -1 投票，投票人需要把打分 -1 的原因说清楚，便于大家理解和知晓。
+如下是投票邮件模板：
+```shell
+[VOTE] ${Candidate_Full_Name} as an InLong a ${Committer or PMC Member}
+
+Judging from the contributions in recent months, ${Candidate_Full_Name} has
submitted many implementations[1],[2],[3] to the project and improved the
management module for the project. During the optimization and improvement
period of the project, it is hoped that more people will participate in the
actual project optimization and improvement, to let the project more perfect
and easier to use.
+I think making him a a ${Committer or PMC Member} will be a recognition of his
outstanding work for InLong. So, I am happy to call VOTE to accept
${Candidate_Full_Name} as an InLong a ${Committer or PMC 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 InLong:
+1. Issues: https://github.com/apache/inlong/pulls?q=${Candidate_GitHub_ID}
+2. PRs : https://github.com/apache/inlong/issues?q=${Candidate_GitHub_ID}
+3. Others: https://xxx.com/xxx/xxx/?q=${Candidate_GitHub_ID}
+```
## 投票结果反馈
-投票邮件结束后，投票发起者需要在上一封 [VOTE] 邮件里提醒投票结束；同时，投票发起者需要发起邮票总结邮件，总结邮件主送
[email protected]。
-如下是投票总结邮件样例：
- ```shell
- [RESULTS][VOTE] YYYYY as an InLong XXXXXX
-
- Hi everyone,
+投票邮件结束后，投票发起者需要在上一封 [VOTE] 邮件里`提醒投票结束`；同时，投票发起者需要发起邮票总结邮件，总结邮件主送
[email protected]。
+如下是投票总结邮件模板：
+```shell
+[RESULTS][VOTE] ${Candidate_Full_Name} as an InLong a ${Committer or PMC
Member}
- The vote for "YYYYY as an InLong XXXXXX" has PASSED and closed now.
+Hi everyone,
- The result is as follows:
+The vote for "${Candidate_Full_Name} as an InLong a ${Committer or PMC
Member}" has PASSED and closed now.
- 3 PMC +1 Votes
- - aaa
- - bbb
- - ccc
+The result is as follows:
- Vote thread:
- https://lists.apache.org/thread/aaaaaxxxx
+3 PMC Member +1 Votes
+- ${the name 1 of PMC Member}
+- ${the name 2 of PMC Member}
+- ${the name 3 of PMC Member}
- Then I'm going to invite YYYYY to join us.
+Vote thread:
+${vote_thread_url}
- Thanks for everyone's support!
- ```
- 备注：如果是未通过，结果是 "The vote for "YYYYY as an InLong XXXXXX" has FAILED and
closed now."
+Then I'm going to invite ${Candidate_Full_Name} to join us.
-## 新增 PMC 通知邮件
-该步骤只针对投票通过的 PMC 进行处理，如果选举的是 Committer，该步跳过不执行。
-投票发起者需要向 Board 邮件组发送知会邮件，并等待至少72小时；邮件主送 [email protected]，抄送
[email protected]。
-Board 们会分析合规性，直到没有疑义。如下是新增 PMC 通知邮件样例：
- ```shell
- [NOTICE] YYYYY for Apache InLong PMC
-
- Hi everyone,
+Thanks for everyone's support!
+```
- Apache InLong proposes to invite YYYYY to join the PMC.
+:::caution
+如果是未通过，结果是 "The vote for "${Candidate_Full_Name} as an InLong a ${Committer or
PMC Member}" has FAILED and closed now."
+:::
- The vote result is available here: https://lists.apache.org/...
-
- Thanks!
- ```
+## 新增 PMC 成员通知邮件
+该步骤只针对投票通过的 PMC 成员进行处理，如果选举的是 Committer，该步跳过不执行。
+投票发起者需要向 Board 邮件组发送知会邮件，并等待至少 72 小时；邮件主送 [email protected]，抄送
[email protected]。
+Board 们会分析合规性，直到没有疑义。如下是新增 PMC 成员通知邮件模板：
+```shell
+[NOTICE] ${Candidate_Full_Name} for Apache InLong PMC
+
+Hi everyone,
+
+Apache InLong proposes to invite ${Candidate_Full_Name} to join the PMC.
+
+The vote result is available here: ${vote_thread_url}
+
+Thanks!
+```
## 发起邀请邮件
-投票总结邮件发出后，或者 PMC 选举的周知邮件到期后，投票发起人要给候选人发送邀请邮件。
+投票总结邮件发出后，或者 PMC 成员选举的周知邮件到期后，投票发起人要给候选人发送邀请邮件。
邀请邮件主送被邀请人，抄送 [email protected]；被邀请的候选人必须通过指定的邮箱地址回复接受或者拒绝该邀请。
-如下是邀请候选人邮件样例：
- ```shell
- [Invitation] Invitation to join Apache InLong as a XXXXXX
-
- Hi YYYYY,
-
- In recognition of your contributions to Apache InLong, the InLong PMC
- has recently voted to add you as a XXXXXX. The XXXXXX role gives
- you access to merge patches into Apache InLong and is also a
- stepping-stone towards membership in the
- Project Management Committee (PMC). We hope that you accept
- this invitation and continue to help us make Apache InLong better.
-
- If you'd like to accept, you will need to send an Individual
- Contributor License Agreement (ICLA) to [email protected], CCing
- [email protected], and request an Apache account name as
- described at http://www.apache.org/dev/new-committers-guide.html if
- you don’t already have one, once you get an account name, or if you
- have one already, please email it to me.
-
- NOTICE: when you fill out ICLA file, the value of preferred Apache id(s)
- needs to be a valid ID, including:
- 1. The ID must not already be in use in
https://people.apache.org/committer-index.html;
- 2. The characters "-" and "_" are not allowed in id;
- 3. The id must consist of lowercase alphanumeric characters only,
- start with an alphabetic character, have a minimum length of 3
characters,
- and have no special characters.
-
- With the expectation of your acceptance, welcome!
-
- The Apache InLong PMC
- ```
+如下是邀请候选人邮件模板：
+```shell
+[Invitation] Invitation to join Apache InLong as a a ${Committer or PMC Member}
+
+Hi ${Candidate_Full_Name},
+
+In recognition of your contributions to Apache InLong, the InLong PMC
+has recently voted to add you as a a ${Committer or PMC Member}. The a
${Committer or PMC Member} role gives
+you access to merge patches into Apache InLong and is also a
+stepping-stone towards membership in the
+Project Management Committee (PMC). We hope that you accept
+this invitation and continue to help us make Apache InLong better.
+
+If you'd like to accept, you will need to send an Individual
+Contributor License Agreement (ICLA) to [email protected], CCing
[email protected], and request an Apache account name as
+described at http://www.apache.org/dev/new-committers-guide.html if
+you don’t already have one, once you get an account name, or if you
+have one already, please email it to me.
+
+NOTICE: when you fill out ICLA file, the value of preferred Apache id(s)
+ needs to be a valid ID, including:
+ 1. The ID must not already be in use in
https://people.apache.org/committer-index.html;
+ 2. The characters "-" and "_" are not allowed in id;
+ 3. The id must consist of lowercase alphanumeric characters only,
+ start with an alphabetic character, have a minimum length of 3
characters,
+ and have no special characters.
+
+With the expectation of your acceptance, welcome!
+
+The Apache InLong PMC
+```
+
+:::note
+在签署 ICLA 时，候选人需要在 “notify project:” 栏目写上 Apache InLong 项目名，这样候选人帐号才会被 Apache
正确的加入对应项目人员名单。
+:::
## 接受邀请后处理
创建 Apache 帐号并将候选人帐号加入项目。
-候选人接受邀请后，如果候选人没有 apache 邮箱帐号，投票发起人需要协助候选人按照指引创建好 apache 帐号。
-在签署 ICLA 时，候选人需要在 “notify project:” 栏目写上 Apache InLong 项目名，这样候选人帐号才会被 Apache
正确的加入对应项目人员名单，确认候选人的 Apache
帐号已加入项目的地址：http://people.apache.org/phonebook.html?project=inlong。
+候选人接受邀请后，如果候选人没有 Apache 邮箱帐号，投票发起人需要协助候选人按照指引创建好 Apache 帐号，确认候选人的 Apache
帐号已加入项目的地址：http://people.apache.org/phonebook.html?project=inlong。
## 向社区发布申明邮件
如上步骤都完成后，投票发起人向 [email protected] 邮件组发通知邮件。
-如下是通知邮件样例：
- ```shell
- [ANNOUNCE] New XXXXXX: YYYYY
-
- Hi everyone,
-
- The Project Management Committee(PMC) for Apache InLong has invited YYYYY
to become a XXXXXX and we are pleased to announce that he has accepted.
+如下是通知邮件模板：
+```shell
+[ANNOUNCE] New a ${Committer or PMC Member}: ${Candidate_Full_Name}
- YYYYY is being active in the InLong community, and we are glad to see his
more interactions with the community in the future.
-
- Welcome YYYYY, and please enjoy your journey.:)
+Hi everyone,
+
+The Project Management Committee(PMC) for Apache InLong has invited
${Candidate_Full_Name} to become a a ${Committer or PMC Member} and we are
pleased to announce that he has accepted.
+
+${Candidate_Full_Name} is being active in the InLong community, and we are
glad to see his more interactions with the community in the future.
- Thanks!
-
- ```
+Welcome ${Candidate_Full_Name}, and please enjoy your journey.:)
+
+Thanks!
+
+```
-到此，整个流程才算走完，候选人才正式的成为项目的 Committer 或者 PMC。
+到此，整个流程才算走完，候选人才正式的成为项目的 Committer 或者 PMC 成员。
