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

wangxin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new 4184dee  Updated New Committer Guide (markdown)
4184dee is described below

commit 4184deee4cb989f3d9a0cf78e0ed31663a87f68f
Author: Xin Wang <xin.victorw...@gmail.com>
AuthorDate: Sat Jun 2 22:11:09 2018 +0800

    Updated New Committer Guide (markdown)
---
 New-Committer-Guide.md | 50 ++++++++++++++++++++++++--------------------------
 1 file changed, 24 insertions(+), 26 deletions(-)

diff --git a/New-Committer-Guide.md b/New-Committer-Guide.md
index 2ec3fd3..d5739a5 100644
--- a/New-Committer-Guide.md
+++ b/New-Committer-Guide.md
@@ -1,40 +1,40 @@
-# Apache committer guide
+# Apache Committer Guide
 
-##  First: How to become a committer
+## First: How to become a committer
 
-### Initializer committers at the project incubator stage
-At the project incubator stage, there will be an initialize committers list in 
the proposal of the incubator project. Confirm that you are one of the 
initialize committers. After the vote is passed in the Apache incubator 
community, the committer can start preparing his account. You can see 
[incubator wiki](https://wiki.apache.org/incubator/).
+### Initial committers at the project incubator stage
+At the project incubator stage, there will be an initial committers list in 
the proposal of the incubator project. Confirm that you are one of the initial 
committers. After the vote is passed in the Apache incubator community, these 
committers can start preparing their account. See [incubator 
wiki](https://wiki.apache.org/incubator/) for details.
 
 ### The active contributor is elected as a committer
-In the late development process, an active contributor can be elected as a 
committer. See [how to become a 
committer](https://www.apache.org/dev/new-committers-guide.html#becoming-a-committer)
+At the late development stage, an active contributor can be elected as a 
committer. See [how to become a 
committer](https://www.apache.org/dev/new-committers-guide.html#becoming-a-committer)
 
-## Second: The individual contributor submits ICLA
+## Second: The individual contributor signs ICLA
 
 ### 1, Apache ID
 Choose a Apache ID not in the [apache committers list 
page](http://people.apache.org/committer-index.html).
 
 ### 2, Individual Contributor License Agreement  (ICLA):
-Download the [ICLA template](https://www.apache.org/licenses/icla.pdf) to find 
the available ID. After filling the icla.pdf personal information correctly, 
printing, signing, scanning, and sending mail as an attachment to the secretary 
secret...@apache.org, the secretary will help to create the Apache user ID. At 
the same time, a your...@apache.org mailbox can be created. You can see if the 
user has been created on the [apache committers list page 
(http://people.apache.org/committer-inde [...]
+Download the [ICLA template](https://www.apache.org/licenses/icla.pdf). After 
filling the icla.pdf with personal information correctly, print, sign, scan, 
and send it in mail as an attachment to the secretary secret...@apache.org, the 
secretary will help to create the Apache user ID. At the same time, a 
your...@apache.org mailbox will be created. You can see if the user has been 
created on the [apache committers list page 
(http://people.apache.org/committer-index.html).
 
-## Third: Join the Apache developer group
+## Third: Join The Apache Developer Group
 
-* 1, login the [Apache account tool](https://id.apache.org/), when you login 
at the first time, you can select the "Change password?" checkbox  to get the 
initializer password. Then the initializer password will be sent to the forward 
mailbox (the developer mail recorded in the project incubator proposal)
+* 1, login via the [Apache account tool](https://id.apache.org/), when you 
login at the first time, you can select the "Change password?" checkbox  to get 
the initial password. Then the initial password will be sent to the forward 
mailbox (the developer mail recorded in the project incubator proposal)
 
-* 2, about Apache mailbox: apache.org mailbox does not have its own mail 
content storage server. It needs to borrow other mail providers' mail content 
storage and mail sending functions. In many voting sessions, Apache mailbox is 
recommended.
+* 2, about Apache mailbox: does not have its own mail content storage server. 
It needs to borrow the mail content storage and mail sending functions of other 
mail providers. In many voting sessions, Apache mailbox is recommended.
 
-There is a question about how to configure the apache.org mailbox forwarding 
function in other mailboxes.
+There is a question about how to configure the apache.org mailbox forwarding 
function using other mailboxes.
 
-1) inbox: to receive mails that sent to youer...@apache.org mailbox. The 
forward mailbox in the first step the configured int the Apache account tool 
can use forward mailbox to pick up the mail.
+1) inbox: to receive mails that sent to youer...@apache.org mailbox. The 
forward mailbox configured in the Apache account tool in the first step can use 
the forward mailbox to pick up incoming mail.
 
-2) the Outbox: the sent email will shows the sender as  your...@apache.org 
account. Please refer to: [set up Apache mailbox 
guide](https://reference.apache.org/committer/email) and [Gmail mailbox 
setting](http://gmailblog.blogspot.com/2009/07/send-mail-from-another-address-without.html).
 In other mailbox service settings, this forwarding mode is not easy to find. 
Gmail is the most convenient, so it is recommended to use Gmail  (not 
advertising).
+2) the Outbox: emails sent out will show the sender as  your...@apache.org 
account. Please refer to: [set up Apache mailbox 
guide](https://reference.apache.org/committer/email) and [Gmail mailbox 
setting](http://gmailblog.blogspot.com/2009/07/send-mail-from-another-address-without.html).
 In other mailbox service settings, this forwarding mode is not easy to find. 
Gmail is the most convenient, which is recommended  (no advertising).
 
 * 3, Modify the homepage URL option in the edit page, homepage link of  your 
account can be added in [apache committer index 
page](http://people.apache.org/committer-index.html) 
 
-* 4, Modify the GitHub account in the edit page, and  an email will be sent to 
invite you to join the github.com/apache-commiiters group. Now, please learn 
from the way [ASF 
works](http://www.apache.org/foundation/how-it-works.html#developers) to do 
some basic preparation of ASF development.
+* 4, Modify the GitHub account in the edit page, and an email will be sent to 
invite you to join the github.com/apache-commiiters group. Now, please learn 
from the way [ASF 
works](http://www.apache.org/foundation/how-it-works.html#developers) to do 
some basic preparation of ASF development.
 
 ## Fourth: To obtain write permission of the project
 
-The operation of the [GitBox account link 
tool](https://gitbox.apache.org/setup/) 
+Operation of the [GitBox account link tool](https://gitbox.apache.org/setup/) 
 
 ### 1, Apache account authorization
 
@@ -46,32 +46,30 @@ According to the prompt, the OAuth protocol of Github 
account is authorized to l
 
 ### 3, Set up GitHub account in github.com, two-factors authorization (2FA)
 
-According to [authorized GitHub 2FA 
wiki](https://help.github.com/articles/configuring-two-factor-authentication-via-a-totp-mobile-app/)
 operation:
-
-* 1) install "Google Authenticator" app to your mobile phone
+* 1) install "Google Authenticator" app on your cell phone
 * 2), Following the [authorized GitHub 2FA 
wiki](https://help.github.com/articles/configuring-two-factor-authentication-via-a-totp-mobile-app/),
  you can operation step by step .
 
-In the [two-factors authorization authentication (2. Scan this barcode with 
your app.)](https://github.com/settings/two_factor_authentication/verify) page, 
it is not recommended to select a two-dimensional code with a mobile phone, 
because some of the mobile phones will not be able to scan it.
+In the [two-factors authorization authentication (2. Scan this barcode with 
your app.)](https://github.com/settings/two_factor_authentication/verify) page, 
it is not recommended to select a two-dimensional code with a cell phone, 
because some of the cell phones will not be able to scan.
 
-Please open the cell phone "Google Authenticator" app, click "+" to select 
"input the secret key": write the GitHub account in the account name input box. 
In your "secret key" input box, write the text of the "enter this text code" 
link in the open web page. After clicking "add" in app, 6 digit dynamic will be 
generated for this account. Write the 6 digit number to the text box in the web 
page, and then click "Enable". In this way, the 2fa is set to be successful.
+Please open the cell phone "Google Authenticator" app, click "+" to select 
"input the secret key": write the GitHub account in the account name input box. 
In your "secret key" input box, write the text of the "enter this text code" 
link in the open web page. After clicking "add" in app, 6 digit dynamic will be 
generated for this account. Write the 6 digit number to the text box in the web 
page, and then click "Enable". In this way, the 2fa is set successfully.
 
-* 3), logout and login to Github again, and one more step will appear after 
entering user name and password. Fill in the dynamic password and use the 
dynamic password of app
+* 3), logout and login to Github again, and one more step will appear after 
entering user name and password. Fill in the 6 digit number dynamic password  
generated by the app 
 
-* 4), IIt will take about half an hour, and you will be notified by mail that 
you have joined the XX project-committers developer group. You can also check 
it in the [apache teams] (https://github.com/orgs/apache/teams) page yourself.
+* 4),It will take about half an hour, and you will be notified by mail that 
you have joined the XX project-committers developer group. You can also check 
it in the [apache teams] (https://github.com/orgs/apache/teams) page yourself.
 
-* 5), After the 2fa has been submitted, you will have the permission check 
problem for the cloned projects. The solution is selected below two.:
+* 5), After the 2fa has been submitted, you will have the permission check 
problem for the cloned projects. The solution is one of below two:
 
 * A. Apply for Access Token
 
 When access token is generated on GitHub, the token where the instruction line 
needs a password is pasted.
 
-Reference website [referenced link 
one](https://help.github.com/articles/https-cloning-errors/#provide-access-token-if-2fa-enabled)
 and [referenced link 
two](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/)
+Refer to website [referenced link 
one](https://help.github.com/articles/https-cloning-errors/#provide-access-token-if-2fa-enabled)
 and [referenced link 
two](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/)
 
 * B. switch to SSH
 
 ssh-keygen then paste the content in the pub file into GitHub.
 
-* Note: ensure that GitHub's 2fa is "enable". When you set 2fa to "off", it 
will be delisted by the corresponding Apache committer write permission group 
until you set it up again.
+**Note**: ensure that GitHub's 2fa is "enabled". When you set 2fa to "off", it 
will be delisted by the corresponding Apache committer write permission group 
until you set it up again.
 
 ## Fifth: other
 
@@ -84,7 +82,7 @@ If not discussed in the community (mailing list), just as it 
did not happen
 
 ### A small benefit
 
-Jetbrains company gives Apache committers a small benefit that is free to use 
idea's full series products. The specific address is: 
https://www.jetbrains.com/shop/eform/apache? Product=ALL
+Jetbrains company gives Apache committers a small benefit, which is free to 
use IDEA's full series products. The specific address is: 
https://www.jetbrains.com/shop/eform/apache? Product=ALL
 
 ### Reference wiki
 https://www.apache.org/dev/new-committers-guide.html
\ No newline at end of file

-- 
To stop receiving notification emails like this one, please contact
wang...@apache.org.

Reply via email to