This is an automated email from the ASF dual-hosted git repository.
hulk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-kvrocks-website.git
The following commit(s) were added to refs/heads/main by this push:
new 825a622 Add some how to docs to community (#9)
825a622 is described below
commit 825a622669ff6e4f050bc0372c39dd67d2d5a356
Author: hulk <[email protected]>
AuthorDate: Tue Jul 26 16:56:16 2022 +0800
Add some how to docs to community (#9)
---
community/how-to-release.md | 302 +++++++++++++++++++++++++++++++
community/how-to-verify.md | 144 +++++++++++++++
community/how-to-vote-a-committer-pmc.md | 155 ++++++++++++++++
community/index.md | 2 +-
4 files changed, 602 insertions(+), 1 deletion(-)
diff --git a/community/how-to-release.md b/community/how-to-release.md
new file mode 100644
index 0000000..5b8690c
--- /dev/null
+++ b/community/how-to-release.md
@@ -0,0 +1,302 @@
+---
+title: How to release
+sidebar_position: 2
+---
+
+> This article mainly introduces how the Release Manager releases a new
version in accordance with the Apache requirements.
+
+## Prolegomenon
+Source Release is the key point which Apache values, also, is necessary for a
release;
+Binary Release is optional. Kvrocks can choose whether to release the binary
package to the Apache repository or not.
+
+Note that for binary distribution packages, it is necessary to check that the
new version does not contain third-party dependencies.
+
+For more guideline, you can refer the following links:
+
+[ASF Release Creation
Process](https://infra.apache.org/release-publishing.html)
+
+[ASF Release Policy](https://www.apache.org/legal/release-policy.html)
+
+
+## Adding PG KEY
+> Ref：https://infra.apache.org/openpgp.html
+**This section is the requirements for release manager who is the first time
to be a release manager**
+
+### Install gpg
+For more details, please ref to [Official
website](https://www.gnupg.org/download/index.html), configurations under Mac
OS:
+```shell
+$ brew install gpg
+$ gpg --version #check the version, should be 2.x
+```
+### Generate gpg Key
+#### Attentions：
+- Name is best to keep consistent with your full name of Apache ID
+- Email should be the Apache email
+- Name is best to only use English to avoid garbled
+
+#### Generate the key as prompt
+```shell
+➜ ~ gpg --full-gen-key
+gpg (GnuPG) 2.2.20; Copyright (C) 2020 Free Software Foundation, Inc.
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+
+Please select what kind of key you want:
+ (1) RSA and RSA (default)
+ (2) DSA and Elgamal
+ (3) DSA (sign only)
+ (4) RSA (sign only)
+ (14) Existing key from card
+Your selection? 1 # input 1
+RSA keys may be between 1024 and 4096 bits long.
+What keysize do you want? (2048) 4096 # input 4096
+Requested keysize is 4096 bits
+Please specify how long the key should be valid.
+ 0 = key does not expire
+ <n> = key expires in n days
+ <n>w = key expires in n weeks
+ <n>m = key expires in n months
+ <n>y = key expires in n years
+Key is valid for? (0) 0 # input 0
+Key does not expire at all
+Is this correct? (y/N) y # input y
+
+GnuPG needs to construct a user ID to identify your key.
+
+Real name: Hulk Lin # input your name
+Email address: [email protected] # input your emal
+Comment: # input some annotations, optional
+You selected this USER-ID:
+ "Hulk <[email protected]>"
+
+Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O # input O
+We need to generate a lot of random bytes. It is a good idea to perform
+some other action (type on the keyboard, move the mouse, utilize the
+disks) during the prime generation; this gives the random number
+generator a better chance to gain enough entropy.
+We need to generate a lot of random bytes. It is a good idea to perform
+some other action (type on the keyboard, move the mouse, utilize the
+disks) during the prime generation; this gives the random number
+generator a better chance to gain enough entropy.
+
+# Input the security key
+┌──────────────────────────────────────────────────────┐
+│ Please enter this passphrase │
+│ │
+│ Passphrase: _______________________________ │
+│ │
+│ <OK> <Cancel> │
+└──────────────────────────────────────────────────────┘
+# key generatio[n will be done after your inputting the key with the following
output
+gpg: key E49B00F626B marked as ultimately trusted
+gpg: revocation certificate stored as
'/Users/hulk/.gnupg/openpgp-revocs.d/F77B887A4F25A9468C513E9AA3008E49B00F626B.rev'
+public and secret key created and signed.
+
+pub rsa4096 2022-07-12 [SC]
+ F77B887A4F25A9468C513E9AA3008E49B00F626B
+uid [ultimate] hulk <[email protected]>
+sub rsa4096 2022-07-12 [E]
+```
+
+### upload your key to public gpg keyserver
+
+```shell
+➜ ~ gpg --list-keys
+-------------------------------
+pub rsa4096 2022-07-12 [SC]
+ F77B887A4F25A9468C513E9AA3008E49B00F626B
+uid [ultimate] hulk <[email protected]>
+sub rsa4096 2022-07-12 [E]
+
+# command for sending your key id to key server
+$ gpg --keyserver pgpkeys.mit.edu --send-key <key id>
+# Among them, pgpkeys.mit.edu is a randomly selected keyserver, and the
keyserver list is: https://sks-keyservers.net/status/, which is automatically
synchronized with each other, you can choose any one of them.
+```
+
+### Check whether the key is created successfully
+Uploading takes about one minute, after that, you can check by your email at
`http://keys.gnupg.net`. Be reminded to tick "the show full-key hashes" under
advance.
+
+
+### Add your gpg public key to the KEYS document
+
+> SVN is required for this step
+The svn repository of the DEV branch is:
https://dist.apache.org/repos/dist/dev/incubator/kvrocks
+The svn repository of the Release branch is:
https://dist.apache.org/repos/dist/release/incubator/kvrocks
+
+#### Add the public key to KEYS in the dev branch to release the RC version
+```shell
+➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/kvrocks
/tmp/kvrocks-dist-dev
+# As this step will copy all the versions, it will take some time. If the
network is broken, please use svn cleanup to delete the lock before re-execute
it.
+➜ ~ cd kvrocks-dist-dev
+➜ kvrocks-dist-dev ~ (gpg --list-sigs [email protected] && gpg --export
--armor [email protected]) >> KEYS # Append your key to the KEYS file
+➜ kvrocks-dist-dev ~ svn add . # It is not needed if the KEYS document
exists before.
+➜ kvrocks-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # Later on, if you
are asked to enter a username and password, just use your apache username and
password.
+```
+
+#### Add the public key to the KEYS in the release branch for releasing
official version
+```shell
+➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/kvrocks
kvrocks-dist-release
+➜ ~ cd kvrocks-dist-release
+➜ kvrocks-dist-release ~ (gpg --list-sigs [email protected] && gpg
--export --armor [email protected]) >> KEYS # Append the KEY you generated
to the document KEYS, after appending, it is best to check whether it is correct
+➜ kvrocks-dist-release ~ svn add . # It is not needed if the KEYS document
exists before.
+➜ kvrocks-dist-release ~ svn ci -m "Add gpg key for YOUR_NAME" # Later on, if
you are asked to enter a username and password, just use your apache username
and password.
+```
+### Upload the GPG public key to your Github account
+1. Enter https://github.com/settings/keys to add GPG KEYS.
+2. Please remember to bind the email address used in the GPG key to your
github account (https://github.com/settings/emails)., if you find "unverified"
after adding it.
+
+### create tag
+
+1. Checkout to the RELEASE BRANCH and cherry-pick commits to release
+2. Use `./x.py package source --version {VERSION}` to create release tarball
+3. Make sure it compiles good and push tag to GitHub
+
+### Upload tar file to dist repo
+> SVN is need in this step, SVN repo for DEV branch is
https://dist.apache.org/repos/dist/dev/incubator/kvrocks
+
+### Checkout Kvorcks to local directory
+```shell
+# As this step will copy all the versions, it will take some time. If the
network is broken, please use svn cleanup to delete the lock before re-execute
it.
+svn co https://dist.apache.org/repos/dist/dev/incubator/kvrocks
/tmp/kvrocks-dist-dev
+```
+
+### Add public key to KEYS file adn commit to SVN repository
+```shell
+cd /tmp/kvrocks-dist-dev
+mkdir ${release_version}-${rc_version} # create a directory named by version
+cp
/tmp/apache-kvrocks-${release_version}-${rc_version}-incubating-src/*tar.gz*
${release_version}-${rc_version}/ # copy source code and signature package to
the versioned directory
+svn status # check svn status
+svn add ${release_version}-${rc_version} # addi to svn
+svn status # check svn status
+svn commit -m "prepare for ${release_version} ${rc_version}" # commit to
SVN remote server
+```
+
+## Voting
+
+- Kvrocks community vote，send email to ：`[email protected]`
+
+### Kvrocks community vote
+
+#### Vote template
+
+```html
+Title：[VOTE] Release Apache Kvrocks(incubating) ${release_version}
${rc_version}
+
+Content：
+
+Hello Apache Kvrocks(incubating) PMC and Community,
+
+ This is a call for a vote to release Apache Kvrocks(incubating) version
${release_version}-${rc_version}.
+
+ The tag to be voted on is ${release_version}-${rc_version}:
+
+ The release candidate:
+
+
https://dist.apache.org/repos/dist/dev/incubator/kvrocks/${release_version}-${rc_version}/
+
+
+ Keys to verify the release candidate:
+
+ https://downloads.apache.org/incubator/kvrocks/KEYS
+
+
+ Git tag for the release:
+
+
https://github.com/apache/incubator-kvrocks/releases/tag/${release_version}-${rc_version}
+
+ Please download, verify, and test.
+
+ The VOTE will remain open for at least 72 hours.
+
+ [ ] +1 approve
+ [ ] +0 no opinion
+ [ ] -1 disapprove with the reason
+
+ To learn more about apache kvrocks, please see
+ https://kvrocks.apache.org/
+
+ Checklist for reference:
+
+ [ ] Download links are valid.
+ [ ] Checksums and signatures.
+ [ ] LICENSE/NOTICE files exist
+ [ ] No unexpected binary files
+ [ ] All source files have ASF headers
+ [ ] Can compile from source
+ [ ] All Tests Passed
+
+ More detailed checklist please refer to:
+ https://kvrocks.apache.org/community/how-to-verify
+
+Thanks,
+Your Kvrocks(incubating) Release Manager
+```
+
+#### Vote Result template
+```html
+Title：[RESULT][VOTE] Release Apache Kvrocks(incubating) ${release_version}
${rc_version}
+
+Content：
+
+Hello Apache Kvrocks(incubating) PMC and Community,
+
+ The vote closes now as 72hr have passed. The vote PASSES with
+ xx (+1 non-binding) votes from the PMC,
+ xx (+1 non-binding) vote from the rest of the developer community,
+ and no further 0 or -1 votes.
+
+ The vote thread: {vote_mail_address}
+
+ The release is accepted and will be published.
+
+Thank you for your support.
+Your Kvrocks(incubating) Release Manager
+```
+
+## Officially released
+
+### Move source code and binary package from DEV to release repository on SVN.
+```shell
+svn mv
https://dist.apache.org/repos/dist/dev/incubator/kvrocks/${release_version}-${rc_version}
https://dist.apache.org/repos/dist/release/incubator/kvrocks/${release_version}
-m "Release ${release_version}"
+```
+### Check whether the dev and release is correct
+1. Make sure `${release_version}-${rc_version}` is deleted in
[dev](https://dist.apache.org/repos/dist/dev/incubator/kvrocks/).
+2. Delete release package of pre versions
[release](https://dist.apache.org/repos/dist/release/incubator/kvrocks/)，these
packages will be saved
[here](https://archive.apache.org/dist/incubator/kvrocks/)
+
+### Update links on official website
+
+### Send email to `[email protected]` and CC `[email protected]`
+
+Release announce email template：
+```html
+Title： [ANNOUNCE] Release Apache Kvrocks(incubating) ${release_version}
+Content：
+Hi all,
+
+The Apache Kvrocks(incubating) community is pleased to announce
+that Apache Kvrocks(incubating) ${release_version} has been released!
+
+Kvrocks is a distributed key value NoSQL database that uses RocksDB
+as storage engine and is compatible with Redis protocol.
+
+This release contains a number of new features, bug fixes and
+improvements compared to the last version released before.
+The notable changes since ${release_version} include:
+1. xxxxx
+2. yyyyyy
+3. zzzzzz
+
+Please refer to the change log for the complete list of changes:
+https://github.com/apache/incubator-kvrocks/blob/${release_version}-${rc_version}/Changelog
+
+Apache Kvrocks website: https://kvrocks.apache.org/
+
+Download Links: https://kvrocks.apache.org/download
+
+Kvrocks Resources:
+- Issue: https://github.com/apache/incubator-kvrocks/issues
+- Mailing list: [email protected]
+
+Thanks
+On behalf of Apache Kvrocks community
+```
diff --git a/community/how-to-verify.md b/community/how-to-verify.md
new file mode 100644
index 0000000..81887bf
--- /dev/null
+++ b/community/how-to-verify.md
@@ -0,0 +1,144 @@
+---
+title: How to verify release
+sidebar_position: 3
+---
+
+To verify the release, the following checklist can be used to reference:
+- [ ] Download links are valid.
+- [ ] Checksums and PGP signatures are valid.
+- [ ] Source code artifacts have correct names matching the current release.
+- [ ] LICENSE and NOTICE files are correct for the repository.
+- [ ] All files have license headers if necessary.
+- [ ] Building is OK.
+
+
+## Download the release package to be verified to the local environment
+> Use the following command to download all artifacts, replace
"${release_version}-${rc_version}" with the version ID of the version to be
released:
+```shell
+svn co
https://dist.apache.org/repos/dist/dev/incubator/kvrocks/${release_version}-${rc_version}/
+```
+
+## Verify signature and hash
+> Start the verification process, which includes but is not limited to the
following content and verification methods.
+> GnuPG is recommended, which can install by yum install gnupg or apt-get
install gnupg.
+
+### Check if the release package is complete
+The package to release must check:
+- Whether to include the source code package
+- Whether to include the signature of the source code package
+- Whether to include the sha512 of the source code package
+- (if include) Check the binary package, also check the contents listed in
(2)-(4)
+
+### Verify signature and hash
+GnuPG is recommended, which can install by yum install GnuPG or apt-get
install GnuPG.
+ - Import public key
+ ```shell
+ curl https://downloads.apache.org/incubator/kvrocks/KEYS > KEYS # Download
KEYS
+ gpg --import KEYS # Import KEYS to local
+ ```
+ - Trust the public key
+ > Trust the KEY used in this version
+
+```shell
+gpg --edit-key xxxxxxxxxx # KEY used in this version
+
+gpg (GnuPG) 2.3.6; Copyright (C) 2021 Free Software Foundation, Inc.
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law.
+
+Secret key is available.
+
+sec rsa4096/A3008E49B00F626B
+ created: 2022-07-12 expires: never usage: SC
+ trust: ultimate validity: ultimate
+ssb rsa4096/DD4049061341F808
+ created: 2022-07-12 expires: never usage: E
+[ultimate] (1). hulk <[email protected]>
+
+gpg> trust
+sec rsa4096/A3008E49B00F626B
+ created: 2022-07-12 expires: never usage: SC
+ trust: ultimate validity: ultimate
+ssb rsa4096/DD4049061341F808
+ created: 2022-07-12 expires: never usage: E
+[ultimate] (1). hulk <[email protected]>
+
+Please decide how far you trust this user to correctly verify other users' keys
+(by looking at passports, checking fingerprints from different sources, etc.)
+
+ 1 = I don't know or won't say
+ 2 = I do NOT trust
+ 3 = I trust marginally
+ 4 = I trust fully
+ 5 = I trust ultimately
+ m = back to the main menu
+
+Your decision? 5
+Do you really want to set this key to ultimate trust? (y/N) y
+
+sec rsa4096/A3008E49B00F626B
+ created: 2022-07-12 expires: never usage: SC
+ trust: ultimate validity: ultimate
+ssb rsa4096/DD4049061341F808
+ created: 2022-07-12 expires: never usage: E
+[ultimate] (1). hulk <[email protected]>
+ ```
+ - Check signature and hash
+
+1. Save below shell codes to file `release-verify.sh`
+
+```shell
+#!/bin/sh
+YELLOW="\033[37;1m"
+GREEN="\033[32;1m"
+ENDCOLOR="\033[0m"
+
+if [ "$#" -ne 1 ]; then
+ echo "Usage: $0 {YOUR RELEASE TAR FILE}" >&2
+ exit 1
+fi
+
+PKG=$1
+
+if [ ! -f "$PKG" ]; then
+ echo "File '$PKG' does not exist."
+ exit 1
+fi
+
+#gpg --armor --output "$PKG.asc" --detach-sig $PKG
+gpg --verify "$PKG.asc" $PKG
+
+if [ $? -eq 0 ]
+then
+ printf $GREEN"Success to verify the gpg sign"$ENDCOLOR"\n"
+else
+ printf $YELLOW"Failed to verify the gpg sign"$ENDCOLOR"\n"
+fi
+
+#shasum -a 512 $PKG > "$PKG.sha512"
+shasum -a 512 -c "$PKG.sha512"
+
+if [ $? -eq 0 ]
+then
+ printf $GREEN"Success to verify the checksum"$ENDCOLOR"\n"
+else
+ printf $YELLOW"Failed to verify the checksum"$ENDCOLOR"\n"
+fi
+
+```
+2. verify the sign and checksum
+
+./release-verify.sh apache-kvrocks-${release_version}-src.tar.gz
+
+```shell
+gpg: Signature made 一 7/18 13:44:27 2022 CST
+gpg: using RSA key F77B887A4F25A9468C513E9AA3008E49B00F626B
+gpg: Good signature from "hulk <[email protected]>" [ultimate]
+```
+
+### Check the file content of the source package
+Unzip `apache-kvrocks-${release_version}-src.tar.gz` and check as follows:
+- [ ] LICENSE and NOTICE files are correct for the repository.
+- [ ] All files have ASF license headers if necessary.
+- [ ] Building is OK.
+
diff --git a/community/how-to-vote-a-committer-pmc.md
b/community/how-to-vote-a-committer-pmc.md
new file mode 100644
index 0000000..7c78539
--- /dev/null
+++ b/community/how-to-vote-a-committer-pmc.md
@@ -0,0 +1,155 @@
+---
+title: How to vote a Committer or PMC
+sidebar_position: 1
+---
+
+## Initiate discussion in the community private mailing group
+ Any Kvrocks 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
Kvrocks's private mailing list.
+ In the discussion email, the proposer should clearly state the candidate's
contributions and give the address for reviewing the corresponding
contributions, 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] XXXXXX for Kvrocks [committer|pmc]
+
+ I nominate XXXXXX as an Kvrocks [committer|pmc]
+
+ Judging from the contributions in recent months, XXXXXX 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 XXXXXX as [committer|pmc] of the Kvrocks project.
+
+ 1. https://github.com/apache/incubator-kvrocks/issues/created_by/XXXXXX
+ 2. https://github.com/apache/incubator-kvrocks/commits?author=XXXXXX
+ ```
+
+## 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 Kvrocks'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] XXXXXX as a Kvrocks [Committer|pmc]
+
+ Judging from contributions in recent months, XXXXXX 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|pmc] will be a recognition of his
outstanding work for Kvrocks. So, I am happy to call VOTE to accept XXXXXX as a
Kvrocks [committer|pmc]
+
+ 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 Kvrocks:
+ 1. Issues: https://github.com/apache/incubator-kvrocks/pulls?q=XXXXXX
+ 2. PRs : https://github.com/apache/incubator-kvrocks/issues?q=XXXXXX
+ ```
+
+## 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] XXXXXX as a Kvrocks[committer|pmc]
+
+ Hi everyone,
+
+ The vote for "XXXXXX as a Kvrocks [committer/pmc]" has PASSED and closed
now.
+
+ The result is as follows:
+
+ 3 PMC +1 Votes
+ - aaa
+ - bbb
+ - ccc
+
+ Vote thread:
+ https://lists.apache.org/thread/aaaaaxxxx
+
+ Then I'm going to invite XXXXXX to join us.
+
+ Thanks for everyone's support!
+ ```
+ Note: If it is not passed, the result is "The vote for "XXXXXX as a Kvrocks
[committer|pmc]" has FAILED and closed now."
+
+## 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] XXXXXX for Apache Kvrocks(incubating) PMC
+
+ Hi everyone,
+
+ Apache Kvrocks(incubating) proposes to invite XXXXXX to join the PMC.
+
+ The vote result is available here: https://lists.apache.org/...
+
+ 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 Kvrocks as a [committer|pmc]
+
+ Hi XXXXXX,
+
+ In recognition of your contributions to Apache Kvrocks(incubating), the
Kvrocks PMC
+ has recently voted to add you as a [committer|pmc]. The [committer|pmc]
role gives
+ you access to merge patches into Apache Kvrocks(incubating) 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 Kvrocks(incubating)
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 Kvrocks(incubating) PMC
+ ```
+
+## 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 Kvrocks” 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=kvrocks.
+
+## 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:
+
+ ```shell
+ [ANNOUNCE] New [committer|pmc]: XXXXXX
+
+ Hi everyone,
+
+ The Project Management Committee(PMC) for Apache has invited XXXXXX to
become a [committer|pmc] and we are pleased to announce that he has accepted.
+
+ XXXXXX is being active in the Kvrocks community, and we are glad to see his
more interactions with the community in the future.
+
+ Welcome XXXXXX, 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.
+
+
diff --git a/community/index.md b/community/index.md
index d65cbcb..75d13e5 100644
--- a/community/index.md
+++ b/community/index.md
@@ -1,5 +1,5 @@
---
-sidebar_position: 1
+sidebar_position: 0
title: Community
---
