[linkis-website] branch dev updated: [feat:4085] Modify PPMC to PMC (#648)

Wed, 04 Jan 2023 02:17:31 -0800 

This is an automated email from the ASF dual-hosted git repository.

casion pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/linkis-website.git


The following commit(s) were added to refs/heads/dev by this push:
     new a5142479dd [feat:4085] Modify PPMC to PMC (#648)
a5142479dd is described below

commit a5142479dd0f5b2ceac1d9b927c228221bc44a43
Author: aiceflower <[email protected]>
AuthorDate: Wed Jan 4 18:17:17 2023 +0800

    [feat:4085] Modify PPMC to PMC (#648)
---
 community/how-to-email.md                          |  12 +-
 community/how-to-sign-apache-icla.md               |   5 +-
 community/how-to-verify.md                         |   7 +-
 ...tter-ppmc.md => how-to-vote-a-committer-pmc.md} | 112 +++++++++------
 ....md => pmc-related-permission-configuration.md} |  12 +-
 community/site-map.md                              |   2 +-
 discuss/project-hisotry.md                         | 155 ---------------------
 .../current/how-to-email.md                        |  18 +--
 .../current/how-to-sign-apache-icla.md             |   5 +-
 .../current/how-to-verify.md                       |   6 +-
 ...tter-ppmc.md => how-to-vote-a-committer-pmc.md} |  94 ++++++-------
 ....md => pmc-related-permission-configuration.md} |  12 +-
 .../current/site-map.md                            |   2 +-
 src/pages/team/config.json                         |  12 +-
 src/pages/team/index.js                            |  10 +-
 15 files changed, 166 insertions(+), 298 deletions(-)

diff --git a/community/how-to-email.md b/community/how-to-email.md
index 7964d5f97a..fcc356c83c 100644
--- a/community/how-to-email.md
+++ b/community/how-to-email.md
@@ -44,7 +44,7 @@ For more information, please refer to the official [Mail 
Etiquette](https://infr
 ** Reply **
 
 - At the end of the email content, it is best to bring your own signature 
(English)
-- If it is a reply to a voting email, it is best to bring a binding mark 
(votes cast by PPMC/IPMC members are binding, you can add a binding suffix such 
as: `+1 approve(binding)`;
+- If it is a reply to a voting email, it is best to bring a binding mark 
(votes cast by PMC members are binding, you can add a binding suffix such as: 
`+1 approve(binding)`;
 Votes cast by ordinary members, non-binding, can be added with non-binding 
suffix such as: `+1 approve(non-binding)` )
 - When some mailboxes such as: 163/sina reply to emails, the default is to 
bring the Chinese `reply`, which will cause the apache email to be recognized 
as a new thread email
 For example: https://lists.apache.org/thread/otfftdtbq0z9xsddnl7wb8tgzkhqcnof, 
the threads of the entire mail cannot be connected in series,
@@ -92,13 +92,13 @@ Therefore, it is necessary to modify the configuration of 
the email reply. For d
 ** \[HELP] Example**
 - For help: https://lists.apache.org/thread/br03lmd3n73lbc6n0lzcmqjbvy960wvf
 
-## 4. Mail usage of PPMC
+## 4. Mail usage of PMC
 
 From the determination of a version to the release, it may involve specific 
common scenarios of using email
 1. The new version needs to organize PMC and developers to discuss, record the 
minutes of the meeting, determine the function points of this version, the 
general release time of the plan, and the release manager of this time, etc., 
and send the meeting minutes [email protected] Email list.
 2. For the scope of the feature list of the new version, you need to send a 
voting email to [email protected], and 3+ PMCs are required to agree and 
the yes votes are greater than the negative votes.
 3. For the weekly regular meeting hosted, the meeting invitation reminder 
email needs to be released before the meeting / the meeting minutes email 
should be sent to the [email protected] mailbox after the meeting
-4. New committer/ppmc votes need to be sent to [email protected]. See 
https://community.apache.org/newcommitter.html for the new committee/ppmc 
selection process
+4. New committer/PMC votes need to be sent to [email protected]. See 
https://community.apache.org/newcommitter.html for the new committee/PMC 
selection process
 
 
 ## 5. How to reply to version release voting emails
@@ -108,10 +108,10 @@ If you initiate a posting vote, you can refer to this 
response example to reply
 <font color="red">
 When replying to the email, you must bring the information that you have 
checked by yourself. Simply replying to `+1 approve` is invalid.
 
-PPMC/IPMC member voting is best with the binding suffix, indicating a binding 
vote, which is convenient for counting voting results
+PMC member voting is best with the binding suffix, indicating a binding vote, 
which is convenient for counting voting results
 </font>
 
-Non-PPMC/Non-IPMC member
+Non-PMC member
 ```html
 +1 (non-binding)
 I checked:
@@ -122,7 +122,7 @@ I checked:
      5.  
 ````
 
-PPMC/IPMC member
+PMC member
 ```html
 +1 (binding)
 I checked:
diff --git a/community/how-to-sign-apache-icla.md 
b/community/how-to-sign-apache-icla.md
index 5b8c802fd3..88bd2edaba 100644
--- a/community/how-to-sign-apache-icla.md
+++ b/community/how-to-sign-apache-icla.md
@@ -36,11 +36,12 @@ Apache only accept hand-written signature or [PDF signature 
software](https://sm
 
 ```html
 To: [email protected]
+Cc: [email protected]
 Subject: Accept to become a linkis committer
 Content:
 
-Hello Apache Incubator:
-    I have accepted the Apache Linkis(Incubator) PPMC 
+Hello everyone:
+    I have accepted the Apache Linkis PMC 
 invitation to become linkis committer, the attachment 
 is my ICLA information.
 Thanks!
diff --git a/community/how-to-verify.md b/community/how-to-verify.md
index f2fa39fbea..54915de8cc 100644
--- a/community/how-to-verify.md
+++ b/community/how-to-verify.md
@@ -17,9 +17,10 @@ If the network is poor, downloading may be time-consuming. 
The download is compl
 :::
 ```shell
 #If there is svn locally, you can clone to the local
-$ svn co 
https://dist.apache.org/repos/dist/dev/incubator/linkis/${release_version}-${rc_version}/
+
+$ svn co 
https://dist.apache.org/repos/dist/dev/linkis/${release_version}-${rc_version}/
 #or download the material file directly
-$ wget 
https://dist.apache.org/repos/dist/dev/incubator/linkis/${release_version}-${rc_version}/xxx.xxx
+$ wget 
https://dist.apache.org/repos/dist/dev/linkis/${release_version}-${rc_version}/xxx.xxx
 
 ```
 ## 2. Verify that the uploaded version is compliant
@@ -38,7 +39,7 @@ First import the publisher's public key. Import KEYS from the 
svn repository to
 
 #### 2.2.1 Import public key
 ```shell
-$ curl  https://downloads.apache.org/incubator/linkis/KEYS > KEYS # Download 
KEYS
+$ curl  https://downloads.apache.org/linkis/KEYS > KEYS # Download KEYS
 $ gpg --import KEYS # Import KEYS to local
 ```
 #### 2.2.2 Trust the public key
diff --git a/community/how-to-vote-a-committer-ppmc.md 
b/community/how-to-vote-a-committer-pmc.md
similarity index 65%
rename from community/how-to-vote-a-committer-ppmc.md
rename to community/how-to-vote-a-committer-pmc.md
index 160f264952..5396012bbb 100644
--- a/community/how-to-vote-a-committer-ppmc.md
+++ b/community/how-to-vote-a-committer-pmc.md
@@ -1,11 +1,11 @@
 ---
-title: How to Vote New Committer/PPMC
+title: How to Vote New Committer/PMC
 sidebar_position: 6
 ---
-> Introduce the selection requirements and process for Committer and PPMC. 
Official guidelines can be found at: 
https://incubator.apache.org/guides/ppmc.html
+> Introduce the selection requirements and process for Committer and PMC. 
Official guidelines can be found at: 
https://community.apache.org/newcommitter.html
 
 ## 1. Candidate requirements
-When voting, all PPMC members need to decide for themselves whether candidates 
should be approved as committers. This can be done by searching the [mailing 
list](https://lists.apache.org/[email protected])/[ISSUES/PR](https://github.com/apache/linkis/issues
 )/[Official Website Documentation 
Contribution](https://github.com/apache/linkis-website) to understand how 
candidates interact with others, and the contributions they make (code or 
documentation patches, suggestions, partici [...]
+When voting, all PMC members need to decide for themselves whether candidates 
should be approved as committers. This can be done by searching the [mailing 
list](https://lists.apache.org/[email protected])/[ISSUES/PR](https://github.com/apache/linkis/issues
 )/[Official Website Documentation 
Contribution](https://github.com/apache/linkis-website) to understand how 
candidates interact with others, and the contributions they make (code or 
documentation patches, suggestions, particip [...]
 
 Below are some points to consider when evaluating candidates for commitment 
eligibility.
 1. Ability to develop collaboration with the community?
@@ -22,40 +22,40 @@ Below are some points to consider when evaluating 
candidates for commitment elig
    - Have a solid general understanding of the project
    - Quality of discussions in emails
    - Are their patches (if applicable) easy to apply with just a cursory review
-5. PPMC competency requirements
+5. PMC competency requirements
    - Have a more comprehensive understanding of the project
    - Ability to control project progress and version quality
    - Actively participate in/lead the construction of the community, promote 
the healthy development of the community, and take the initiative to undertake 
the responsibility and governance of the project
    - Respond proactively to questions raised by the ASF Board and take 
necessary action
    - Familiar with the release process of ASF
 
-In most cases, new PPMC members are nominated from the Committer team. But it 
is also possible to become a member of the PPMC directly, as long as the PPMC 
agrees to the nomination and is confident that the candidate is ready. This can 
be demonstrated, for example, by the fact that he/she was an Apache member, an 
Apache official, or a PPMC member of another project.
+In most cases, new PMC members are nominated from the Committer team. But it 
is also possible to become a member of the PMC directly, as long as the PMC 
agrees to the nomination and is confident that the candidate is ready. This can 
be demonstrated, for example, by the fact that he/she was an Apache member, an 
Apache official, or a PMC member of another project.
 
 ## 2. Detailed process of recommendation
 
 :::tip
 ${Candidate Name}: represents the electee eg: Joe Bloggs
 
-${Committer/PPMC}: represents the type of Committer/PPMC
+${Committer/PMC}: represents the type of Committer/PMC
 :::
 
 ### 2.1 Initiate community mail discussion
 
->Any linkis PPMC member can initiate a voting discussion. After PPMC finds any 
valuable contributions from community contributors and obtains the consent of 
the candidate, they can initiate a discussion on the linkis private mailing 
list. In the discussion email, the proposer should clarify the candidate's 
contribution and give the address for reviewing the corresponding contribution, 
so that everyone can discuss and analyze. The discussion email should be sent 
to [email protected] [...]
+>Any linkis 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 the linkis private mailing 
list. In the discussion email, the proposer should clarify the candidate's 
contribution and give the address for reviewing the corresponding contribution, 
so that everyone can discuss and analyze. The discussion email should be sent 
to [email protected] [...]
 
 Here is a sample discussion email:
 
 ```html
 To: [email protected]
-Subject: [DISCUSS] ${Candidate Name} as an Linkis ${Committer/PPMC} candidate
+Subject: [DISCUSS] ${Candidate Name} as an Linkis ${Committer/PMC} candidate
 Content:
 
 Hi all:
-    I nominate ${Candidate Name} as an Linkis ${Committer/PPMC} candidate
+    I nominate ${Candidate Name} as an Linkis ${Committer/PMC} candidate
  
     Judging from the contributions in recent months, ${Candidate 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 in the 
actual project optimization and improvement, to let the project more perfect 
and easier to use.
   
-    So I nominated ${Candidate Name} as ${Committer/PPMC} of the Linkis 
project.
+    So I nominated ${Candidate Name} as ${Committer/PMC} of the Linkis project.
   
     1. https://github.com/apache/linkis/issues/created_by/${Candidate 
Githubid} 
     2. https://github.com/apache/linkis/commits?author=${Candidate Githubid} 
@@ -65,17 +65,17 @@ Thanks!
 ````
     
 ### 2.2 Initiate a community mail poll
->If the discussion email does not receive any disagreement information within 
the specified time, the vote initiator needs to initiate a Committer or PPMC 
election vote on the linkis private mailing list. The main voting email is sent 
to [email protected], which lasts for at least 72 hours, and requires 
at least 3 votes + 1 to pass; if there is 1 -1 vote, the entire vote will fail; 
if a -1 vote is initiated, the voter needs to put -1 The reasons are clearly 
stated so that everyon [...]
+>If the discussion email does not receive any disagreement information within 
the specified time, the vote initiator needs to initiate a Committer or PMC 
election vote on the linkis private mailing list. The main voting email is sent 
to [email protected], which lasts for at least 72 hours, and requires 
at least 3 votes + 1 to pass; if there is 1 -1 vote, the entire vote will fail; 
if a -1 vote is initiated, the voter needs to put -1 The reasons are clearly 
stated so that everyone [...]
 
 Here is a sample poll email:
 ```html
 To: [email protected]
-Subject: [VOTE] ${Candidate Name} as an Linkis ${Committer/PPMC} candidate
+Subject: [VOTE] ${Candidate Name} as an Linkis ${Committer/PMC} candidate
 Content:
 Hi all:
     Judging from the contributions in recent months, ${Candidate 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 ${Committer/PPMC} will be a recognition of his 
outstanding work for Linkis. So, I am happy to call VOTE to accept ${Candidate 
Name} as an Linkis ${Committer/PPMC}.
+    I think making him a ${Committer/PMC} will be a recognition of his 
outstanding work for Linkis. So, I am happy to call VOTE to accept ${Candidate 
Name} as an Linkis ${Committer/PMC}.
   
     Voting will continue for at least 72 hours or until the required number of 
votes is reached.
  
@@ -97,15 +97,15 @@ Thanks!
 Here is an example of voting results:
 ```html
 To: [email protected]
-Subject: [RESULTS][VOTE] ${Candidate Name} as an Linkis ${Committer/PPMC}
+Subject: [RESULTS][VOTE] ${Candidate Name} as an Linkis ${Committer/PMC}
 Content:
 
 Hi all:
-    The vote for "${Candidate Name} as an Linkis ${Committer/PPMC}" has PASSED 
and closed now.
+    The vote for "${Candidate Name} as an Linkis ${Committer/PMC}" has PASSED 
and closed now.
 
     The result is as follows:
 
-    3 PPMC +1 Votes
+    3 PMC +1 Votes
     - aaa
     - bbb
     - ccc
@@ -118,24 +118,22 @@ Hi all:
     Thanks for everyone's support!
 Thanks!
 ````
-**Note: If it is not passed, the result is "The vote for "${Candidate Name} as 
an Linkis ${Committer/PPMC}" has FAILED and closed now."**
+**Note: If it is not passed, the result is "The vote for "${Candidate Name} as 
an Linkis ${Committer/PMC}" has FAILED and closed now."**
    
-### 2.4 Added PPMC notification email
-> This step is only for the new PPMC election process. If the Committer is 
elected, this step is skipped and not executed.
-> The initiator of the vote needs to send a notification email to the IPMC 
[email protected] mailing group and wait for at least 72 hours;
-> Email to [email protected], cc [email protected]; IPMCs 
will analyze compliance until there is no objection.
+### 2.4 Added PMC notification email
+> his step is only for the new PMC election process. If the Committer is 
elected, this step is skipped and not executed.
+> The initiator of the vote needs to send a notification email to the 
[email protected] mailing group and wait at least 72 hours;
+> Email [email protected], cc [email protected]; board will analyze 
compliance until there is no objection.
 
-Send to IPMC [email protected] cc [email protected] . There 
is a 72-hour grace period between the notification by the PPMC to the IPMC and 
the formal invitation by the PPMC to the proposed member
-
-The following is a sample notification email for adding a PPMC:
+The following is a sample notification email for adding a PMC:
 ```html
-To: [email protected]
+To: [email protected]
 Cc: [email protected]
-Subject: [NOTICE] ${Candidate Name} for Linkis PPMC
+Subject: [NOTICE] ${Candidate Name} for Linkis PMC
 Content:
 Hi everyone,
 
-    ${Candidate Name} has been voted as a new member of the Linkis PPMC.
+    ${Candidate Name} has been voted as a new member of the Linkis PMC.
 
     The vote thread is at:
     https://lists.apache.org/thread/xx
@@ -143,7 +141,7 @@ Hi everyone,
 Thanks!
 ````
 
-After 72 hours, if the IPMC has no objection to the nomination (which in most 
cases will not), an invitation may be sent to the candidate.
+After 72 hours, if the board has no objection to the nomination (which in most 
cases will not), an invitation may be sent to the candidate.
 
 ### 2.5 Send email invitations to candidates
 > After announcing the voting results, the voting initiator should send an 
 > invitation email to the candidates. The invitation email is sent to the 
 > invitees, cc [email protected]; the invited candidates must reply to 
 > accept or reject the invitation through the specified email address.
@@ -157,16 +155,16 @@ Subject: Invitation to become Linkis committer: Joe Bloggs
     
 Hello Joe Bloggs,
 
-    The Linkis Podling Project Management Committee] (PPMC)
+    The Linkis Podling Project Management Committee] (PMC)
     hereby offers you committer privileges to the project
-    [as well as membership in the PPMC]. These privileges are
+    [as well as membership in the PMC]. 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 PPMC member enables you
+    submission process. [Being a PMC member enables you
     to guide the direction of the project.]
     
     Being a committer does not require you to
@@ -195,7 +193,7 @@ Hello Joe Bloggs,
         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
+        This will allow the Secretary to notify the PMC
         when your iCLA has been recorded.
     
     When recording of your iCLA is noted, you will
@@ -204,21 +202,21 @@ Hello Joe Bloggs,
 
     With the expectation of your acceptance, welcome!
 
-The Apache Linkis PPMC
+The Apache Linkis PMC
 ````
 
 ### 2.6 Invitation acceptance process
 >Requires candidates for processing
 
 The new Committer should reply to `[email protected]` (select `reply 
all`) and express his/her acceptance of the invitation.
-The invitation will then be considered accepted by the project's PPMC. Of 
course, new committers can also choose to decline the invitation.
+The invitation will then be considered accepted by the project's PMC. Of 
course, new committers can also choose to decline the invitation.
 
 Once the invitation is accepted, new submitters must take the following steps:
 - Subscribe to `[email protected]`. Usually this is already done.
 - Choose an Apache ID that has not been used [apache committers list 
page](http://people.apache.org/committer-index.html).
 - Download [ICLA](https://www.apache.org/licenses/icla.pdf 
org/licenses/cla-corporate.pdf) is expected).
 - After filling in the correct information in `icla.pdf` (or `ccla.pdf`), 
print it, sign it by hand, scan it into PDF, and send it as an attachment to 
[[email protected]] (email: [email protected]). (If electronic signatures 
are preferred, follow the steps on [this 
page](http://www.apache.org/licenses/contributor-agreements.html#submitting))
-- PPMC will wait for the Apache Secretary to confirm ICLA (or CCLA) filing. 
New submitters and PPMC will receive the following email:
+- PMC will wait for the Apache Secretary to confirm ICLA (or CCLA) filing. New 
submitters and PMC will receive the following email:
 
 
 ```html
@@ -233,12 +231,12 @@ Please refer to 
https://www.apache.org/foundation/how-it-works.html#developers
 for more information about roles at Apache.
 ````
 
-In the unlikely event that the account has not been processed, PPMC members 
should contact the project [Apache Incubator's 
VP](https://www.apache.org/foundation/), which can be accessed through the 
[Apache Account Submission Helper Form](https://whismy. 
apache.org/officers/acreq) request.
+In the unlikely event that the account has not been processed, PMC members 
should contact the project [Apache Incubator's 
VP](https://www.apache.org/foundation/), which can be accessed through the 
[Apache Account Submission Helper Form](https://whismy. 
apache.org/officers/acreq) request.
 
 In a few days, new committers will receive an email confirming account 
creation with the title `Welcome to the Apache Software Foundation (ASF)!`.
 
-After receiving the notification email that the account was created 
successfully, you can reply to the previous invitation email again to inform 
Linkis PPMC that your Apache Id account has been created, and request that your 
Apache Id be added to Linkis' official submitter list.
-(Inform the PPMC responsible for nominating you to add the new committer to 
the official committer list via the 
[Roster](https://whismy.apache.org/roster/committee/linkis) page)
+After receiving the notification email that the account was created 
successfully, you can reply to the previous invitation email again to inform 
Linkis PMC that your Apache Id account has been created, and request that your 
Apache Id be added to Linkis' official submitter list.
+(Inform the PMC responsible for nominating you to add the new committer to the 
official committer list via the 
[Roster](https://whismy.apache.org/roster/committee/linkis) page)
 
 ### 2.7 Setting up apache id and development environment
 >Requires candidates for processing
@@ -250,7 +248,7 @@ After receiving the notification email that the account was 
created successfully
 - [linkis-website](https://linkis.apache.org/team) related page update
 
 
-For detailed instructions, see [PPMC/Committer Related Permission 
Configuration](ppmc-related-permission-configuration.md)
+For detailed instructions, see [PMC/Committer Related Permission 
Configuration](pmc-related-permission-configuration.md)
 
 If you want to make a public appearance in the Apache GitHub organization, you 
need to go to the [Apache GitHub people 
page](https://github.com/orgs/apache/people),
 Search for yourself, then select `Organization visibility` for `Public`.
@@ -261,24 +259,48 @@ Search for yourself, then select `Organization 
visibility` for `Public`.
 The following is a sample notification email:
 ```html
 To: [email protected]
-Subject: [ANNOUNCE] New ${Committer/PPMC}: ${Candidate Name}
+Subject: [ANNOUNCE] New ${Committer/PMC}: ${Candidate Name}
 Content:
 Hi all:
      Hi everyone,
 
-     The Project Management Committee(PMC) for Apache Linkis has invited 
${Candidate Name} to become a ${Committer/PPMC} and we are pleased to announce 
that he has accepted.
+     The Project Management Committee(PMC) for Apache Linkis has invited 
${Candidate Name} to become a ${Committer/PMC} and we are pleased to announce 
that he has accepted.
 
      ${Candidate Name} is being active in the Linkis community, and we are 
glad to see his more interactions with the community in the future.
 
      Welcome ${Candidate Name}, and please enjoy your journey. :)
 
 Thanks!
-The Apache Linkis PPMC
+The Apache Linkis PMC
 ````
    
-At this point, the whole process is over, and the candidate officially becomes 
the Committer or PPMC of the project.
-
-## 4 Workflow summary
+At this point, the whole process is over, and the candidate officially becomes 
the Committer or PMC of the project.
+
+## 4 Update project status
+step1 clong status record file 
+```shell script
+svn co https://svn.apache.org/repos/asf/public/trunk/content/projects/
+```
+
+step2 update news infomation in linkis.xml
+add committer information record 
+```shell script
+<section id="News">
+      <title>News</title>
+      <ul>
+<!--    <li>YYYY-MM-DD New committer: Fred Hampton</li>    -->
+        <li>2021-08-02 Project enters incubation.</li>
+        <li>2022-02-19 First Apache Linkis release v1.0.3</li>
+        <li>2022-02-24 New Committer: Chen Xia</li>
+        <li>2022-04-15 Apache Linkis release v1.1.0</li>
+
+      </ul>
+    </section>
+```
+step3 the information show in follow file after update 
+https://incubator.apache.org/projects/linkis.html
+
+## 5 Workflow summary
 
 1. Send emails with ICLA attachments
 
diff --git a/community/ppmc-related-permission-configuration.md 
b/community/pmc-related-permission-configuration.md
similarity index 89%
rename from community/ppmc-related-permission-configuration.md
rename to community/pmc-related-permission-configuration.md
index 80d0b71827..0b6228f2bb 100644
--- a/community/ppmc-related-permission-configuration.md
+++ b/community/pmc-related-permission-configuration.md
@@ -1,9 +1,9 @@
 ---
-title: PPMC/Committer Related Permission Configuration
+title: PMC/Committer Related Permission Configuration
 sidebar_position: 8
 ---
 
-> PPMC (Podling Project Management Committee)/Committer member, bind github 
account process/and main email subscription
+> PMC (Podling Project Management Committee)/Committer member, bind github 
account process/and main email subscription
 
 ## 1. Binding github account process
 
@@ -101,13 +101,13 @@ Server: mail-relay.apache.org Port: 587 (STARTTLS), 465 
(SSL) User/Pass: {Your L
 ![image](/img/community/mail-relay.png)
 
 ### 2.2 Subscribe to related mailing lists
-As a member of PPMC, you need to actively participate in community 
construction, promote the healthy development of the community, undertake the 
responsibility and governance of the project, and this part of the work is 
often carried out by email (discussion/voting/answering questions, etc.),
-Every PPMC member is required to subscribe to the following mailing lists:
+As a member of PMC, you need to actively participate in community 
construction, promote the healthy development of the community, undertake the 
responsibility and governance of the project, and this part of the work is 
often carried out by email (discussion/voting/answering questions, etc.),
+Every PMC member is required to subscribe to the following mailing lists:
 
 |Name|Description|Subscribe Mail|Unsubscribe Mail|Mail Archive|
 |:-----|:-------|:------|:-------|:-----|
 | [[email protected]](mailto:[email protected]) | Linkis community 
activity information, project discussion announcements, etc. | 
[Subscribe](mailto:[email protected]) | 
[unsubscribe](mailto:[email protected]) | 
[archive](http://mail-archives.apache.org/mod_mbox/linkis-dev) |
-| [[email protected]](mailto:[email protected]) |This mailing 
list is private, visible inside PPMC, mainly for internal discussions | 
[Subscribe](mailto:private-subscribe@ linkis.apache.org) | 
[unsubscribe](mailto:[email protected]) | 
[archive](http://mail-archives.apache.org/mod_mbox/linkis-private) |
+| [[email protected]](mailto:[email protected]) |This mailing 
list is private, visible inside PMC, mainly for internal discussions | 
[Subscribe](mailto:private-subscribe@ linkis.apache.org) | 
[unsubscribe](mailto:[email protected]) | 
[archive](http://mail-archives.apache.org/mod_mbox/linkis-private) |
 | [[email protected]](mailto:[email protected]) | Public 
emails from the incubator community, mainly related to incubation projects | 
[Subscribe](mailto:[email protected]. org) | 
[unsubscribe](mailto:[email protected]) | 
[archive](http://mail-archives.apache.org/mod_mbox/general) |
 
 Subscription operations can be found in the guide [Subscribe to the mailing 
list](how-to-subscribe.md)
@@ -119,4 +119,4 @@ If the above subscription is unsuccessful, you can try to 
use the web-side tool:
 ![image](/img/community/subscribe.png)
 
 
-Mailing list subscriptions, PPMC members can view here: 
https://whismy.apache.org/roster/ppmc/linkis
\ No newline at end of file
+Mailing list subscriptions, PMC members can view here: 
https://whimsy.apache.org/roster/committee/linkis#pmc 
\ No newline at end of file
diff --git a/community/site-map.md b/community/site-map.md
index 3a7f138c48..58441ac390 100644
--- a/community/site-map.md
+++ b/community/site-map.md
@@ -51,7 +51,7 @@ sidebar_position: 12
 - Linkis name application jira 
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-192?filter=allissues
 - Project status file https://incubator.apache.org/projects/linkis.html
 
-- View ppmc mail and other information 
https://whhimsy.apache.org/roster/ppmc/linkis
+- View PMC mail and other information 
https://whimsy.apache.org/roster/committee/linkis#pmc 
 - project file 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/linkis.xml
 - podling file 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/linkis.yml
 
diff --git a/discuss/project-hisotry.md b/discuss/project-hisotry.md
deleted file mode 100644
index 64e1035d94..0000000000
--- a/discuss/project-hisotry.md
+++ /dev/null
@@ -1,155 +0,0 @@
-## Apache Gobblin 
-- 孵化时间:2017-02-23 ~ 2021-01-20
-- 毕业讨论邮件:https://lists.apache.org/thread/9z79b2648bcxy6pw78bfhvq1jkwy0lox
-- 孵化信息: https://incubator.apache.org/projects/gobblin.html 
-- 反馈的问题: 
-
-
-## Apache Ratis 
-- 孵化时间:2017-01-03 ~ 2021-02-17
-- 毕业讨论邮件: https://lists.apache.org/thread/0x2pbbr0khldfo2t8vp49cnl9oz51wcb 
-- 孵化信息: https://incubator.apache.org/projects/ratis.html 
-- 反馈的问题: 
-    - 邮件流量问题 Adjust Github nofications settings to use issues@ mailing list
-
-
-## Apache Pinot 
-- 孵化时间:2018-10-17 ~ 2021-07-21
-- 毕业讨论邮件: https://lists.apache.org/thread/9y63b4fosbocmsj8qlyzg8j4c6166b54
-- 孵化信息: https://incubator.apache.org/projects/pinot.html 
-- 反馈的问题:
-    - 文档有一些 ASF 软件的品牌问题 https://github.com/prestodb/presto/issues/16271
-One other thing you might want to correct, all of the download links to 
previous version are broken on your download page. [1] The previous version are 
automatically archived and can be found here. [2] You may also want to consider 
not calling the convenience binary an “offical binary release”.
-
-
-## Apache Hop 
-- 孵化时间:2020-09-24 ~ 2021-12-16
-- 毕业讨论邮件: https://lists.apache.org/thread/jj46blkwrhf0l31srtzo5j5dcv7zsqz3
-- 孵化信息: https://incubator.apache.org/projects/hop.html
-- 反馈的问题:
-    - 下载区有几个旧版本；这些应该被删除
-    - 项目描述太长，需优化相关的措辞
-
-## Apache AGE 
-- 孵化时间:2020-04-29 ~ 2022-05-18
-- 毕业讨论邮件: https://lists.apache.org/thread/jvrtvcw1zb8gf286css7tvol94r3qd68
-- 孵化信息: https://incubator.apache.org/projects/age.html
-- 反馈的问题:
-    - 三名 PPMC 成员未订阅私人邮件列表。
-    - 包括一些 PPMC 成员在内的四名 Committer 没有将他们的 apache id 映射到他们的 GitHub id。他们如何做出贡献？
-    - 没有人加入PPMC
-
-讨论指出的问题比较多，多次发起了 
-
-
-## Apache YuniKorn 
-- 孵化时间:2020-01-21 ~ 2022-03-16
-- 毕业讨论邮件:  https://lists.apache.org/thread/o8y4b3mp21f608745ngqqdhc628qtwxf
-- 孵化信息: https://incubator.apache.org/projects/yunikorn.html
-- 反馈的问题:
-
-
-## Apache Doris 
-- 孵化时间:2018-07-18 ~ 2022-06-15
-- 毕业讨论邮件: https://lists.apache.org/thread/nbncjl8fdq0bcjop6l4747c8x9c06q00
-- 孵化信息: https://incubator.apache.org/projects/doris.html
-- 反馈的问题:
-    - DorisDB  和 StarRocks的侵权问题 
-    - 百度在中国拥有 Doris 商标，该商标是否已转让给 ASF？
-    - 与 Apache Impala 的关系 
-
-注:涉及比较多的商标和License 问题
-
-- 毕业清单  https://cwiki.apache.org/confluence/display/DORIS/Graduation+Check+List
- 
-## Apache MXNet 
-
-- 孵化时间:2017-01-23 ~ 2022-06
-- 毕业讨论邮件: https://lists.apache.org/thread/3rxzjcmo2y457y6r8ohz1j4qv49joyo6
-- 孵化信息: https://incubator.apache.org/projects/mxnet.html
-- 反馈的问题:
-    - 不应该使用 Google Analytics，而是使用 Apache 安装的 Matomo 跟踪器。
-    - 第三方产品名称问题  3rd party product name listed
-
-- - ICLA签署
-https://cwiki.apache.org/confluence/display/MXNET/ICLA+Progress
-
-
-
-## Apache ShenYu 
-- 孵化时间:2021-05-03 ~ 2022-06
-- 毕业讨论邮件: https://lists.apache.org/thread/cc2myvso0pbyl39yv26bdmzml8jjvpt2
-- 孵化信息: https://incubator.apache.org/projects/shenyu.html
-- 反馈的问题:
-    - 主页描述不够精简 最好用简短而清晰的句子来 说明它在做什么
-    -  网站上提到了 5 个版本，而不是 4 个,在孵化之前的需要标识出  There's no 2.3.0 version release. And 
the 2.3.0 document is marked legacy now https://github.com/ 
apache/shenyu-website/pull/604
-    -  文档中名字最好带上 Apache 前缀  https://github.com/apache/shenyu/pull/3568
-    -  商标问题 \[Branding Issue] Shenyu is still decleared as a project of 
dromara community 
https://lists.apache.org/thread/o9bwzkl3cjbrmzx4n36l63xbv0q112px
-
-
-## Apache DataSketches
-- 孵化时间:2019-03-30 ~ 2020-12-16
-- 毕业讨论邮件: https://lists.apache.org/thread/kcpo1ngkmh9q3zgxl5vo64m9m62c45m0
-- 孵化信息: https://incubator.apache.org/projects/datasketches.html
-- 反馈的问题:
-    - 如果有重要贡献者没有作为初始贡献者加入 podling，或者如果有其他公司实体可以在代码中主张权利，则 podling 必须从这些个人或公司获得 
SGA
-
-
-
-
-
-
-1. 之前尝试在Jira上提单申请hub账户 但是反馈坐席满了， 推荐使用Github Docker Registry。  
这个是否存在合规性问题(官网文档https://incubator.apache.org/guides/distribution.html#docker 是说：
-Artifacts need to be placed in https://hub.docker.com/r/apache/<project>）
-
-2. 另外对于容器镜像构建过程中 的Dockfile文件，使用了基础镜像 如centos:7 ，以及通过如yun install unzip 
的安装的基础环境软件包, 或则使用curl/ADD/COPY  to a destination inside the Docker image. 
这些第三方的工具的使用 是否需要单独在LICENSE中进行 罗列说明 。 
-
-
-1. 我们之前申请hub账号权限， 但是反馈seat 坐席满了， 推荐使用Github Docker Registry。  这个是否符合asf docker 
镜像分发要求(官网文档https://incubator.apache.org/guides/distribution.html#docker 提到：
-Artifacts need to be placed in https://hub.docker.com/r/apache/<project>）
-
-2. 另外对于构建docker 镜像使用的 Dockfile文件，使用了基础镜像 如centos:7 ，以及通过如yun install unzip 
的安装的基础环境软件包, 或则使用 ADD/COPY  添加资源 to a destination inside the Docker image. 
这些第三方的工具的使用 是否需要单独在LICENSE文件中进行 罗列说明 。 
-
-
-https://issues.apache.org/jira/browse/INFRA-22785
-
-https://issues.apache.org/jira/browse/INFRA-22785
-DockerHub is out of seats. Project is using GitHub Registry instead.
-
-About docker image release and license 
-
-We applied for the DockerHub permission before[1], but the feedback DockerHub 
is out of seats. It is recommended to use the Github Docker Registry. 
-Does this meet the asf docker image distribution requirements (the official 
website document[2]mentions:
-artifacts need to be placed in https://hub.docker.com/r/apache/<project>)
-
-In addition, for the Dockfile file used to build the docker image[3], use the 
basic image such as centos, 
-and the basic environment package installed through such as `yun install 
unzip`, 
-or use `ADD/COPY` to add resources to a destination inside the Docker image. 
-Whether the use of these third-party tools needs to be listed separately in 
the LICENSE file. 
-If so, for the toolkit installed by the yum command, it seems that the 
indirect dependency license cannot be listed well.
-
-
-1. https://issues.apache.org/jira/browse/INFRA-22785
-2. https://incubator.apache.org/guides/distribution.html#docker 
-3. 
https://github.com/apache/linkis/blob/dev-1.3.0/linkis-dist/docker/ldh.Dockerfile
-
-
-We applied for the Docker Hub permission before[1], but the feedback Docker 
Hub is out of seats. 
-It is recommended to use the Github Docker Registry. 
-Does this meet the ASF docker image distribution requirements (The official 
website document[2] 
-mentions:artifacts need to be placed in 
https://hub.docker.com/r/apache/<project>)
-
-In addition, for the Dockfile file used to build the docker image[3], use the 
basic image such as CentOS, 
-and the basic environment package installed through such as `yun install 
unzip`, 
-or use `ADD/COPY` to add resources to a destination inside the Docker image. 
-Whether the use of these third-party tools needs to be listed separately in 
the LICENSE file. 
-If so, for the toolkit installed by the yum command, it seems that the 
indirect dependency license cannot be listed well.
-
-
-1. https://issues.apache.org/jira/browse/INFRA-22785
-2. https://incubator.apache.org/guides/distribution.html#docker 
-3. 
https://github.com/apache/linkis/blob/dev-1.3.0/linkis-dist/docker/ldh.Dockerfile
-
-Best Regards!
-Apache Linkis
-Chen Xia
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-email.md 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-email.md
index d6b5f5b8eb..2e61a8b590 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-email.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-email.md
@@ -14,8 +14,8 @@ Linkis的存档邮件可以在此处查看[存档邮件](https://lists.apache.or
 邮件的主题可以大体分为以下几种类型
 - **\[DISCUSS]**  针对某一特性/功能/逻辑修改/CI/CD的讨论，可以是实现方式/设计/优化建议等等 
 - **\[PROPOSAL]** 提案，如新增/移除某些功能，和\[DISCUSS]区别并不大
-- **\[VOTE]**     
对变更的投票/推选Committer/推选新的PPMC成员等，比如版本的发布，每个版本都会在社区dev邮件列表进行投票；也可以进行多种方案的选择时，发起投票。
-- **\[ANNOUNCE]** 宣布新版本完成发布，宣布推选出的新Committer/PPMC等
+- **\[VOTE]**     
对变更的投票/推选Committer/推选新的PMC成员等，比如版本的发布，每个版本都会在社区dev邮件列表进行投票；也可以进行多种方案的选择时，发起投票。
+- **\[ANNOUNCE]** 宣布新版本完成发布，宣布推选出的新Committer/PMC等
 - **\[NOTICE]** 
主要用来通知一些临时公告等，如社区沙箱环境停服维修/升级，web官网出现服务异常不可用等；以及线上线下周会/交流会以及各种活动信息公告等
 - **\[HELP]**   寻求帮助, 
因为git的代码通知比较多，有时无法及时查阅到；另外github网络访问受限，可能有些同学无法顺利的通过github提交issue。通过邮件发起，更容易辨别和被感知到。
 - **\[VOTE]\[RESULT]** 宣布版本发布投票的结果 
@@ -27,7 +27,7 @@ Linkis的存档邮件可以在此处查看[存档邮件](https://lists.apache.or
 ** 通用规范 **
 
 - 尽可能不要发送纯 HTML 内容，而是发送纯文本。如果使用QQ邮箱，其邮件内容默认使用的是html格式，编写时请先切换至纯文本格式，详细切换指引见本文附录
-- 开发者/社区用户/PPMC成员针对以上场景的内容，发起邮件讨论/需求帮助/通知事宜等，请发送至[email protected]邮箱
+- 开发者/社区用户/PMC成员针对以上场景的内容，发起邮件讨论/需求帮助/通知事宜等，请发送至[email protected]邮箱
 - 邮件标题前请带上对应的类型前缀：如`[HELP] XXXXXXX`,`[DISCUSS] XXXXXXX`
 
 更多可以参阅官方[邮件规范](https://infra.apache.org/contrib-email-tips) 
https://infra.apache.org/contrib-email-tips
@@ -36,7 +36,7 @@ Linkis的存档邮件可以在此处查看[存档邮件](https://lists.apache.or
 ** 回复规范**
 
 - 邮件内容末尾，最好带上自己的署名(英文)
-- 如果是回复投票类的邮件，最好带上是否具有约束性的标识(PPMC/IPMC成员投的票具有约束性，可以加上 binding后缀 如：`+1 
approve(binding)`;
+- 如果是回复投票类的邮件，最好带上是否具有约束性的标识(PMC成员投的票具有约束性，可以加上 binding后缀 如：`+1 
approve(binding)`;
 普通成员投的票，无约束性，可以加上 non-binding后缀 如：`+1 approve(non-binding)` )
 - 由于部分邮箱如:163/sina 在进行邮件回复时，默认是带上的中文`回复`会导致apache 邮件识别为一封新线程邮件 
 如：https://lists.apache.org/thread/otfftdtbq0z9xsddnl7wb8tgzkhqcnof， 
无法将整个邮件的线程串联起来，
@@ -84,12 +84,12 @@ Linkis的存档邮件可以在此处查看[存档邮件](https://lists.apache.or
 ** \[HELP] 示例** 
 - 寻求帮助:https://lists.apache.org/thread/br03lmd3n73lbc6n0lzcmqjbvy960wvf
 
-## 4. PPMC的邮件使用
+## 4. PMC的邮件使用
 从一个版本的确定到发布，可能会涉及具体的使用邮件的常见场景
 1. 新版本需要组织PMC和开发者进行讨论，需要记录会议纪要，确定此版本功能点，计划的大体发布时间，以及本次的release 
manager等，并发送会议纪要[email protected] 邮件列表。
 2. 对于新版本的特性列表范围，需要发送投票邮件至[email protected]邮箱中，并需要3+ PMC同意且同意票大于反对票。
 3. 主持的周例会，会议前需要发布会议邀约提醒邮件/会议后要发送会议纪要邮件至[email protected]邮箱中
-4. 
新的committer/ppmc投票需要发送投票邮件至[email protected]邮箱中。新的committer/ppmc推选流程见 
https://community.apache.org/newcommitter.html
+4. 新的committer/PMC投票需要发送投票邮件至[email protected]邮箱中。新的committer/PMC推选流程见 
https://community.apache.org/newcommitter.html
 
 ## 5. 版本发布投票邮件的回复
 如果发起了发布投票，验证后(详细验证流程见[如何验证](how-to-verify.md))，可以参照此回复示例进行邮件回复
@@ -97,10 +97,10 @@ Linkis的存档邮件可以在此处查看[存档邮件](https://lists.apache.or
 <font color="red">
 回复的邮件一定要带上自己检查了那些项信息，仅仅回复`+1 approve`，是无效的。
 
-PPMC/IPMC成员，投票时请带上 binding后缀，表示具有约束性投票，方便统计投票结果
+PMC成员，投票时请带上 binding后缀，表示具有约束性投票，方便统计投票结果
 </font>
 
-非PPMC/IPMC成员
+非PMC成员
 ```html
 +1 (non-binding)
 I  checked:
@@ -111,7 +111,7 @@ I  checked:
     5. ....
 ```
 
-PPMC/IPMC成员
+PMC成员
 ```html
 +1 (binding)
 I  checked:
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-sign-apache-icla.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-sign-apache-icla.md
index 9df031de93..8c3d420832 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-sign-apache-icla.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-sign-apache-icla.md
@@ -34,11 +34,12 @@ Apache CLA 全称 Apache Contributor License 
Agreement，签署ICLA的目的是
 
 ```html
 To: [email protected]
+Cc: [email protected]
 Subject: Accept to become a linkis committer
 Content:
 
-Hello Apache Incubator:
-    I have accepted the Apache Linkis(Incubator) PPMC 
+Hello everyone:
+    I have accepted the Apache Linkis PMC 
 invitation to become linkis committer, the attachment 
 is my ICLA information.
 Thanks!
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
index ec5814b4df..a18aa457cc 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
@@ -15,9 +15,9 @@ sidebar_position: 4
 :::
 ```shell
 #如果本地有svn，可以clone到本地 
-svn co 
https://dist.apache.org/repos/dist/dev/incubator/linkis/${release_version}-${rc_version}/
+svn co 
https://dist.apache.org/repos/dist/dev/linkis/${release_version}-${rc_version}/
 #或则 直接下载物料文件
-wget 
https://dist.apache.org/repos/dist/dev/incubator/linkis/${release_version}-${rc_version}/xxx.xxx
+wget 
https://dist.apache.org/repos/dist/dev/linkis/${release_version}-${rc_version}/xxx.xxx
 
 ```
 ## 2. 验证上传的版本是否合规
@@ -37,7 +37,7 @@ wget 
https://dist.apache.org/repos/dist/dev/incubator/linkis/${release_version}-
 #### 2.2.1 导入公钥
 
 ```shell
-$ curl  https://downloads.apache.org/incubator/linkis/KEYS > KEYS # 下载KEYS
+$ curl  https://downloads.apache.org/linkis/KEYS > KEYS # 下载KEYS
 $ gpg --import KEYS # 导入KEYS到本地
 ```
 #### 2.2.2 信任公钥
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-ppmc.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-pmc.md
similarity index 68%
rename from 
i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-ppmc.md
rename to 
i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-pmc.md
index 845db949b3..710bd6d7f5 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-ppmc.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-vote-a-committer-pmc.md
@@ -1,11 +1,11 @@
 ---
-title: 如何提名新的Committer 和 PPMC
+title: 如何提名新的Committer 和 PMC
 sidebar_position: 6
 ---
-> 介绍Committer 和 PPMC 
的推选要求以及流程。官方指引可参见：https://incubator.apache.org/guides/ppmc.html
+> 介绍Committer 和 PMC 
的推选要求以及流程。官方指引可参见：https://community.apache.org/newcommitter.html
 
 ## 1.候选人要求
-在投票时，所有 PPMC 
成员都需要自己决定是否应批准候选人成为提交者。可以通过搜索[邮件列表](https://lists.apache.org/[email protected])/[ISSUES/PR](https://github.com/apache/linkis/issues)/[官网文档贡献](https://github.com/apache/linkis-website)，以了解候选人如何与他人互动，以及他们所做的贡献（代码或文档补丁、建议、参与答疑等）。
+在投票时，所有 PMC 
成员都需要自己决定是否应批准候选人成为提交者。可以通过搜索[邮件列表](https://lists.apache.org/[email protected])/[ISSUES/PR](https://github.com/apache/linkis/issues)/[官网文档贡献](https://github.com/apache/linkis-website)，以了解候选人如何与他人互动，以及他们所做的贡献（代码或文档补丁、建议、参与答疑等）。
 
 以下是在评估候选人的承诺资格时需要考虑的一些要点。
 1. 与社区开发合作的能力？
@@ -22,41 +22,41 @@ sidebar_position: 6
    - 对项目有扎实的总体了解
    - 电子邮件中讨论的质量
    - 他们的补丁（如果适用）是否易于应用，只需粗略的审查
-5. PPMC 的能力要求
+5. PMC 的能力要求
    - 对项目有比较全面的了解
    - 能够把控项目进度和版本质量
    - 积极参与/主导社区建设，推动社区健康发展，主动承当项目的责任和治理工作
    - 积极回复 ASF 董事会提出的问题，并采取必要的行动
    - 熟悉 ASF 的版本发布流程
 
-在大多数情况下，新的 PPMC 成员是从 Committer 团队中提名的。但也可以直接成为 PPMC 成员，只要 PPMC 
同意提名，并确信候选人已经准备好。例如，这可以通过他/她曾是 Apache 成员、Apache 官员或另一个项目的 PPMC 成员这一事实来证明。
+在大多数情况下，新的 PMC 成员是从 Committer 团队中提名的。但也可以直接成为 PMC 成员，只要 PMC 
同意提名，并确信候选人已经准备好。例如，这可以通过他/她曾是 Apache 成员、Apache 官员或另一个项目的 PMC 成员这一事实来证明。
 
 ## 2. 推举详细流程
 
 :::tip 
 ${Candidate Name}：代表被选举人 如：Joe Bloggs
 
-${Committer/PPMC}：代表推选的类型 Committer/PPMC
+${Committer/PMC}：代表推选的类型 Committer/PMC
 :::
 
 ### 2.1 发起社区邮件讨论
 
->任何linkis的 PPMC 成员都可以发起投票讨论，在 PPMC 
发现社区贡献者任何有价值的贡献并取得候选人本人同意后，可以在linkis的private邮件列表发起讨论。讨论邮件里提议者要把候选人的贡献说清楚，并且给出复核对应贡献的地址，便于大家讨论分析。讨论邮件主送[email protected]邮箱，讨论将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法。
+>任何linkis的 PMC 成员都可以发起投票讨论，在 PMC 
发现社区贡献者任何有价值的贡献并取得候选人本人同意后，可以在linkis的private邮件列表发起讨论。讨论邮件里提议者要把候选人的贡献说清楚，并且给出复核对应贡献的地址，便于大家讨论分析。讨论邮件主送[email protected]邮箱，讨论将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法。
 
 
 如下是讨论邮件样例：
 
 ```html
 To: [email protected]
-Subject: [DISCUSS]  ${Candidate Name} as an Linkis ${Committer/PPMC} candidate
+Subject: [DISCUSS]  ${Candidate Name} as an Linkis ${Committer/PMC} candidate
 Content:
 
 Hi all:
-    I nominate ${Candidate Name} as an Linkis ${Committer/PPMC} candidate
+    I nominate ${Candidate Name} as an Linkis ${Committer/PMC} candidate
  
     Judging from the contributions in recent months, ${Candidate 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 Name} as ${Committer/PPMC} of the Linkis 
project.
+    So I nominated ${Candidate Name} as ${Committer/PMC} of the Linkis project.
   
     1. https://github.com/apache/linkis/issues/created_by/${Candidate 
Githubid} 
     2. https://github.com/apache/linkis/commits?author=${Candidate Githubid} 
@@ -66,17 +66,17 @@ Thanks!
 ```
     
 ### 2.2 发起社区邮件投票
->如果讨论邮件在规定时间内没有收到分歧信息，投票发起者需要在linkis的private邮件列表发起Committer或 PPMC 
的选举投票。投票邮件主送[email protected]，至少持续72小时，至少要3票+1通过；如果存在-1投票则整个投票失败；投票人需要把-1的原因说清楚，便于大家理解和知晓。
+>如果讨论邮件在规定时间内没有收到分歧信息，投票发起者需要在linkis的private邮件列表发起Committer或 PMC 
的选举投票。投票邮件主送[email protected]，至少持续72小时，至少要3票+1通过；如果存在-1投票则整个投票失败；投票人需要把-1的原因说清楚，便于大家理解和知晓。
 
 如下是投票邮件样例：
 ```html
 To: [email protected]
-Subject: [VOTE] ${Candidate Name} as an Linkis ${Committer/PPMC} candidate
+Subject: [VOTE] ${Candidate Name} as an Linkis ${Committer/PMC} candidate
 Content: 
 Hi all:
     Judging from the contributions in recent months, ${Candidate 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 ${Committer/PPMC} will be a recognition of his 
outstanding work for Linkis. So, I am happy to call VOTE to accept ${Candidate 
Name} as an Linkis ${Committer/PPMC}.
+    I think making him a ${Committer/PMC} will be a recognition of his 
outstanding work for Linkis. So, I am happy to call VOTE to accept ${Candidate 
Name} as an Linkis ${Committer/PMC}.
   
     Voting will continue for at least 72 hours or until the required number of 
votes is reached.
  
@@ -98,15 +98,15 @@ Thanks!
 如下投票结果样例：
 ```html
 To: [email protected]
-Subject: [RESULTS][VOTE] ${Candidate Name} as an Linkis ${Committer/PPMC}
+Subject: [RESULTS][VOTE] ${Candidate Name} as an Linkis ${Committer/PMC}
 Content: 
 
 Hi all:
-    The vote for "${Candidate Name} as an Linkis ${Committer/PPMC}" has PASSED 
and closed now.
+    The vote for "${Candidate Name} as an Linkis ${Committer/PMC}" has PASSED 
and closed now.
 
     The result is as follows:
 
-    3 PPMC  +1 Votes
+    3 PMC  +1 Votes
     - aaa
     - bbb
     - ccc
@@ -119,26 +119,24 @@ Hi all:
     Thanks for everyone's support!   
 Thanks!
 ```
-**备注：如果是未通过，结果是 "The vote for "${Candidate Name} as an Linkis 
${Committer/PPMC}" has FAILED and closed now."**
+**备注：如果是未通过，结果是 "The vote for "${Candidate Name} as an Linkis 
${Committer/PMC}" has FAILED and closed now."**
    
-### 2.4 新增 PPMC 的通知邮件
+### 2.4 新增 PMC 的通知邮件
 
->该步骤只针对新的 PPMC 推举流程，如果选举的是Committer，该步跳过不执行。
->投票发起者需要发送至IPMC [email protected]邮件组发送知会邮件，并等待至少72小时；
->邮件发送 
[email protected]，抄送[email protected]；IPMC们会分析合规性，直到没有异议。
+> 该步骤只针对新的 PMC 推举流程，如果选举的是Committer，该步跳过不执行。
+> 投票发起者需要发送至 [email protected] 邮件组发送知会邮件，并等待至少72小时。
+> 邮件发送 [email protected]，抄送[email protected]；PMC们会分析合规性，直到没有异议。
 
-发送至IPMC [email protected]  抄送 [email protected] 。 从 PPMC 向 
IPMC 发送通知到 PPMC 正式邀请被提议的成员，之间要有 72 小时的宽限期
-
-如下是新增推选 PPMC 的通知邮件样例：
+如下是新增推选 PMC 的通知邮件样例：
 ```html
-To: [email protected]
+To: [email protected]
 Cc: [email protected]
 
-Subject：[NOTICE] ${Candidate Name} for Linkis PPMC
+Subject：[NOTICE] ${Candidate Name} for Linkis PMC
 Content:
 Hi everyone,
 
-    ${Candidate Name} has been voted as a new member of the Linkis PPMC. 
+    ${Candidate Name} has been voted as a new member of the Linkis PMC. 
 
     The vote thread is at:
     https://lists.apache.org/thread/xx
@@ -146,7 +144,7 @@ Hi everyone,
 Thanks!
 ```
 
-72 小时后，如果IPMC不反对提名（大多数情况下不会反对），则可以向候选人发送邀请。
+72 小时后，如果董事会不反对提名（大多数情况下不会反对），则可以向候选人发送邀请。
 
 
 ### 2.5 向候选人发起邮件邀请 
@@ -161,16 +159,16 @@ Subject: Invitation to become Linkis committer: Joe Bloggs
     
 Hello Joe Bloggs,
 
-    The Linkis Podling Project Management Committee] (PPMC) 
+    The Linkis Podling Project Management Committee] (PMC) 
     hereby offers you committer privileges to the project 
-    [as well as membership in the PPMC]. These privileges are
+    [as well as membership in the PMC]. 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 PPMC member enables you 
+    submission process. [Being a PMC member enables you 
     to guide the direction of the project.]
     
     Being a committer does not require you to 
@@ -199,7 +197,7 @@ Hello Joe Bloggs,
         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 
+        This will allow the Secretary to notify the PMC 
         when your iCLA has been recorded.
     
     When recording of your iCLA is noted, you will 
@@ -208,21 +206,21 @@ Hello Joe Bloggs,
 
     With the expectation of your acceptance, welcome!
 
-The Apache Linkis PPMC
+The Apache Linkis PMC
 ```
 
 ### 2.6 接受邀请流程
 >需要候选人进行处理
 
 新的 Committer 应回复 `[email protected]`（选择`reply all`），并表达他/她接受邀请。
-然后，该邀请将被项目的 PPMC 视为已接受。当然，新的 committer 也可以选择拒绝邀请。
+然后，该邀请将被项目的 PMC 视为已接受。当然，新的 committer 也可以选择拒绝邀请。
 
 接受邀请，回复邮件示例 
 ```
-Hello Apache Linkis PPMC,
+Hello Apache Linkis PMC,
 
 I accept the invitation.
-Thanks to the  Apache Linkis Community PPMC for
+Thanks to the  Apache Linkis Community PMC for
 recognizing my work, I will continue to actively participate in the
 work of the  Apache Linkis. Next, I will follow the
 instructions to complete the next steps: Signing and submitting iCLA
@@ -236,7 +234,7 @@ XXXX
 - 选择一个未被使用过 [apache committers list 
page](http://people.apache.org/committer-index.html) 的 Apache ID。
 - 下载 ICLA 并签署 指引见[ICLA 签署流程](how-to-sign-apache-icla)。
 
-- PPMC 将等待Apache秘书确认ICLA（或CCLA）备案。新的提交者和 PPMC 将收到以下电子邮件：
+- PMC 将等待Apache秘书确认ICLA（或CCLA）备案。新的提交者和 PMC 将收到以下电子邮件：
 
 ```html
 Dear ${Candidate Name},
@@ -250,12 +248,12 @@ Please refer to 
https://www.apache.org/foundation/how-it-works.html#developers
 for more information about roles at Apache.
 ```
 
-万一该帐户未被处理，PPMC 成员应联系项目[Apache 
Incubator的VP](https://www.apache.org/foundation/), 可以通过 [Apache Account 
Submission Helper Form](https://whimsy.apache.org/officers/acreq) 请求。
+万一该帐户未被处理，PMC 成员应联系项目[Apache 
Incubator的VP](https://www.apache.org/foundation/), 可以通过 [Apache Account 
Submission Helper Form](https://whimsy.apache.org/officers/acreq) 请求。
 
 几天后，新的提交者将收到一封来自[email protected]帐户通知账号创建的电子邮件，标题为`Welcome to the Apache 
Software Foundation (ASF)!`。
 
-收到账户创建成功的通知邮件后，可以再次回复之前的邀请邮件，告知Linkis PPMC，你的Apache Id账号已经创建，请求将你的Apache 
Id添加到Linkis的官方提交者列表中。
-(告知负责提名你的PPMC通过 [Roster](https://whimsy.apache.org/roster/committee/linkis) 
页面，将新的提交者添加到官方提交者列表中）
+收到账户创建成功的通知邮件后，可以再次回复之前的邀请邮件，告知Linkis PMC，你的Apache Id账号已经创建，请求将你的Apache 
Id添加到Linkis的官方提交者列表中。
+(告知负责提名你的PMC通过 [Roster](https://whimsy.apache.org/roster/committee/linkis) 
页面，将新的提交者添加到官方提交者列表中）
 
 ### 2.7 设置 Apache ID 和开发环境
 
@@ -265,7 +263,7 @@ for more information about roles at Apache.
 - 使用【GitBox Account Linking 
Utility】（https://gitbox.apache.org/setup/）获取Linkis项目的写权限。
 - [linkis-website](https://linkis.apache.org/team)相关页面更新
 
-详细指引见[PPMC/Committer 相关权限配置](ppmc-related-permission-configuration.md)
+详细指引见[PMC/Committer 相关权限配置](pmc-related-permission-configuration.md)
 
 如果您想在 Apache GitHub 组织中公开露面，您需要前往 [Apache GitHub 
人员页面](https://github.com/orgs/apache/people)，
 搜索自己，然后选择`Organization visibility`为`Public`。
@@ -277,27 +275,27 @@ for more information about roles at Apache.
 如下是通知邮件样例：
 ```html
 To: [email protected]
-Subject: [ANNOUNCE] New ${Committer/PPMC}: ${Candidate Name}
+Subject: [ANNOUNCE] New ${Committer/PMC}: ${Candidate Name}
 Content: 
 Hi all:
     Hi everyone,
 
-    The Project Management Committee(PMC) for Apache Linkis has invited 
${Candidate Name} to become a ${Committer/PPMC} and we are pleased to announce 
that he has accepted.
+    The Project Management Committee(PMC) for Apache Linkis has invited 
${Candidate Name} to become a ${Committer/PMC} and we are pleased to announce 
that he has accepted.
 
     ${Candidate Name} is being active in the Linkis community, and we are glad 
to see his more interactions with the community in the future.
 
     Welcome ${Candidate Name}, and please enjoy your journey.:)
 
 Thanks!
-The Apache Linkis PPMC
+The Apache Linkis PMC
 ```
    
-到此，整个流程才算走完，候选人才正式的成为项目的Committer或者PPMC。
+到此，整个流程才算走完，候选人才正式的成为项目的Committer或者PMC。
 
-## 4 更新 Clutch Status信息
+## 4 更新项目状态信息
 step1 克隆状态记录的文件 
 ```shell script
-svn co 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/
+svn co https://svn.apache.org/repos/asf/public/trunk/content/projects/
 ```
 
 step2 修改 linkis.xml 中的new信息
@@ -316,7 +314,7 @@ step2 修改 linkis.xml 中的new信息
     </section>
 ```
 step3 更新提交后，信息会在这里呈现 
-https://incubator.apache.org/clutch/linkis.html
+https://incubator.apache.org/projects/linkis.html
 
 
 ## 5 操作流程总结
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/ppmc-related-permission-configuration.md
 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/pmc-related-permission-configuration.md
similarity index 90%
rename from 
i18n/zh-CN/docusaurus-plugin-content-docs-community/current/ppmc-related-permission-configuration.md
rename to 
i18n/zh-CN/docusaurus-plugin-content-docs-community/current/pmc-related-permission-configuration.md
index c4326a6113..fdfe629d20 100644
--- 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/ppmc-related-permission-configuration.md
+++ 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/pmc-related-permission-configuration.md
@@ -1,8 +1,8 @@
 ---
-title: PPMC/Committer 相关权限配置
+title: PMC/Committer 相关权限配置
 sidebar_position: 8
 ---
-> PPMC(Podling Project Management Committee)成员,绑定github账号流程/以及主要邮件订阅
+> PMC(Podling Project Management Committee)成员,绑定github账号流程/以及主要邮件订阅
 
 ## 1. 绑定github账号流程
 
@@ -101,13 +101,13 @@ Server: mail-relay.apache.org Port: 587 (STARTTLS), 465 
(SSL) User/Pass: {Your L
 
 
 ### 2.2 订阅相关邮件列表
-作为PPMC一员 需要积极参与到社区建设中，推动社区健康发展，承当项目的责任和治理工作,这部分工作很多时候是通过邮件方式进行（讨论/投票/答疑等）,
-每一位PPMC成员都需要订阅以下邮件列表:
+作为PMC一员 需要积极参与到社区建设中，推动社区健康发展，承当项目的责任和治理工作,这部分工作很多时候是通过邮件方式进行（讨论/投票/答疑等）,
+每一位PMC成员都需要订阅以下邮件列表:
 
 |名称|描述|订阅邮件|退订邮件|邮件归档|
 |:-----|:--------|:------|:-------|:-----|
 | [[email protected]](mailto:[email protected]) | 
linkis的社区活动信息,项目的讨论公告等 | [订阅](mailto:[email protected])   | 
[退订](mailto:[email protected])   | 
[归档](http://mail-archives.apache.org/mod_mbox/linkis-dev)   |
-| [[email protected]](mailto:[email protected]) 
|此邮件列表是不公开的，PPMC内部可见，主要用于内部讨论 | 
[订阅](mailto:[email protected])   | 
[退订](mailto:[email protected])   | 
[归档](http://mail-archives.apache.org/mod_mbox/linkis-private)   |
+| [[email protected]](mailto:[email protected]) 
|此邮件列表是不公开的，PMC内部可见，主要用于内部讨论 | [订阅](mailto:[email protected]) 
  | [退订](mailto:[email protected])   | 
[归档](http://mail-archives.apache.org/mod_mbox/linkis-private)   |
 | [[email protected]](mailto:[email protected]) | 
孵化社区的公开邮件，主要是孵化项目的相关动态 | [订阅](mailto:[email protected])   
| [退订](mailto:[email protected])   | 
[归档](http://mail-archives.apache.org/mod_mbox/general)   |
 
 订阅操作可以见指引[订阅邮件列表](how-to-subscribe.md)
@@ -119,4 +119,4 @@ Server: mail-relay.apache.org Port: 587 (STARTTLS), 465 
(SSL) User/Pass: {Your L
 ![image](/img/community/subscribe.png)
 
 
-邮件列表订阅情况，PPMC成员可以在此查看:https://whimsy.apache.org/roster/ppmc/linkis
+邮件列表订阅情况，PMC成员可以在此查看:https://whimsy.apache.org/roster/committee/linkis#pmc 
diff --git 
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md 
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md
index dc9c439fd4..56d6e0a8d2 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md
@@ -52,7 +52,7 @@ sidebar_position: 12
 - Board Reports https://whimsy.apache.org/board/minutes/Linkis.html
 - Linkis的名字申请工单  
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-192?filter=allissues
 
 - 项目状态文件  https://incubator.apache.org/projects/linkis.html
-- ppmc 邮件等信息查看 https://whimsy.apache.org/roster/ppmc/linkis
+- PMC 邮件等信息查看 https://whimsy.apache.org/roster/committee/linkis#pmc 
 - project 文件  
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/linkis.xml
 
 - podling 文件 
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/linkis.yml
 - 毕业后report上报工具 https://reporter.apache.org/wizard/ （主席和PMC可查看） 
diff --git a/src/pages/team/config.json b/src/pages/team/config.json
index 68c05c97a1..06b4059bff 100644
--- a/src/pages/team/config.json
+++ b/src/pages/team/config.json
@@ -67,13 +67,18 @@
       "githubId": "ruY9527",
       "publicName": "Yang Bao"
     },
+    {
+      "apacheId": "allenlliu",
+      "githubId": "liuyou2",
+      "publicName": "You Liu"
+    },
     {
       "apacheId": "zhiqiangtao",
       "githubId": "jacktao007",
       "publicName": "Zhiqiang Tao"
     }
   ],
-  "ppmc": [
+  "pmc": [
     {
       "apacheId": "alexkun",
       "githubId": "Alexkun",
@@ -149,11 +154,6 @@
       "githubId": "seayi",
       "publicName": "Xiaohua Yi"
     },
-    {
-      "apacheId": "allenlliu",
-      "githubId": "liuyou2",
-      "publicName": "You Liu"
-    },
     {
       "apacheId": "wangzhen",
       "githubId": "wForget",
diff --git a/src/pages/team/index.js b/src/pages/team/index.js
index f2222d1b79..c5f513a2b1 100644
--- a/src/pages/team/index.js
+++ b/src/pages/team/index.js
@@ -25,11 +25,11 @@ export default function() {
     }
 
 
-    const sortToShowPPMC = () =>{
-          config.ppmc.sort((a, b) =>{
+    const sortToShowPMC = () =>{
+          config.pmc.sort((a, b) =>{
             return a.publicName.localeCompare(b.publicName)
           })
-          return  config.ppmc.map((item, i) => (
+          return  config.pmc.map((item, i) => (
                <tr>
                    <td align="left"><a 
href={'https://people.apache.org/committer-index.html#'+ item.apacheId} 
target="_blank" rel="noopener noreferrer">{item.apacheId}</a></td>
                    <td align="left">{item.githubId}</td>
@@ -61,7 +61,7 @@ export default function() {
         <br/>
         <p className="normal-desc" 
dangerouslySetInnerHTML={{__html:dataSource.info.desc}}></p>
         <br></br>
-        <h3 
className="normal-title">PPMC({config.ppmc.length+config.mentor.length})</h3>
+        <h3 
className="normal-title">PMC({config.pmc.length+config.mentor.length})</h3>
         <p className="normal-desc">{dataSource.info.tip}</p>
 
         <table>
@@ -78,7 +78,7 @@ export default function() {
             }
 
             {
-             sortToShowPPMC()
+             sortToShowPMC()
             }
            </tbody>
         </table>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to