You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@eventmesh.apache.org by mi...@apache.org on 2023/02/01 09:14:40 UTC
[incubator-eventmesh-site] branch master updated: update docs
This is an automated email from the ASF dual-hosted git repository.
mikexue pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-eventmesh-site.git
The following commit(s) were added to refs/heads/master by this push:
new 0ab71377 update docs
0ab71377 is described below
commit 0ab713775b5c61b00c2f79e385122ecbe4daa69b
Author: xwm1992 <mi...@126.com>
AuthorDate: Wed Feb 1 17:14:18 2023 +0800
update docs
---
...fficial-recommends-eventmesh-as-runtime-impl.md | 2 +-
community/03-how-to-use-email.md | 2 +-
docs/contribute/01-release.md | 192 ---------------------
.../current/01-contribute.md | 2 +-
.../current/02-how-to-subscribe.md | 2 +-
.../current/03-how-to-use-email.md | 93 ++++++++++
.../current/04-release.md | 5 +
static/images/serverlessworkflow-official.png | Bin 0 -> 317941 bytes
8 files changed, 102 insertions(+), 196 deletions(-)
diff --git a/blog/cncf-serverlessworkflow-official-recommends-eventmesh-as-runtime-impl.md b/blog/cncf-serverlessworkflow-official-recommends-eventmesh-as-runtime-impl.md
index e71f1a83..803bb6f6 100644
--- a/blog/cncf-serverlessworkflow-official-recommends-eventmesh-as-runtime-impl.md
+++ b/blog/cncf-serverlessworkflow-official-recommends-eventmesh-as-runtime-impl.md
@@ -22,5 +22,5 @@ It is a member project of the [CNCF Serverless Working Group](https://github.com
## Open-source workflow runtimes
<p align="center">
-<a href="https://serverlessworkflow.io" target="_blank"><img src="../images/serverlessworkflow-official.png" width="700px" alt="Serverlessworkflow"/></a>
+<a href="https://serverlessworkflow.io" target="_blank"><img src="/images/serverlessworkflow-official.png" width="700px" alt="Serverlessworkflow"/></a>
</p>
diff --git a/community/03-how-to-use-email.md b/community/03-how-to-use-email.md
index 01baa8ca..e84aeea6 100644
--- a/community/03-how-to-use-email.md
+++ b/community/03-how-to-use-email.md
@@ -19,7 +19,7 @@ sidebar_position: 2
-#### 4. Find your Apache email[#](https://shenyu.apache.org/community/use-apache-email/#4-find-your-apache-email)
+#### 4. Find your Apache email
You should have an email from `root@apache.org` like this in your mailbox:
diff --git a/docs/contribute/01-release.md b/docs/contribute/01-release.md
deleted file mode 100644
index 9fc3d31f..00000000
--- a/docs/contribute/01-release.md
+++ /dev/null
@@ -1,192 +0,0 @@
-# Release Creation Process
-
-:::caution
-The documentation of Release Creation Process is WIP (Work-in-Progress).
-:::
-
-## Understand the content and process of Apache publishing
-
-Source Release is the focus of Apache and a must for release; while Binary Release is optional,
-
-Please refer to the link below to find more publishing guidelines on ASF:
-
-- [Apache Release Guide](http://www.apache.org/dev/release-publishing)
-- [Apache Release Policy](http://www.apache.org/dev/release.html)
-- [Maven Release Info](http://www.apache.org/dev/publishing-maven-artifacts.html)
-
-
-## Local build environment preparation
-
-Mainly including signing tools, Maven warehouse certification related preparations
-
-### 1. Install GPG
-
-Download the installation package from [GnuPG official website](https://www.gnupg.org/download/index.html). The commands of GnuPG 1.x version and 2.x version are slightly different. The following instructions take **GnuPG-2.x** version as an example
-
-```sh
-$ gpg --version #Check the version, it should be 2.x
-```
-
-### 2. Generate key with gpg
-
-According to the prompt, generate the key
-
-> Note: Please use the Apache mailbox to generate the GPG Key
-
-```shell
-$ gpg --full-gen-key
-gpg (GnuPG) 2.0.12; Copyright (C) 2009 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)
-Your selection? 1
-RSA keys may be between 1024 and 4096 bits long.
-What key size do you want? (2048) 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)
-Key does not expire at all
-Is this correct? (y/N) y
-
-GnuPG needs to construct a user ID to identify your key.
-
-Real name: ${enter username}
-Email address: ${email address}
-Comment: CODE SIGNING KEY
-You selected this USER-ID:
- "${enter username} (CODE SIGNING KEY) <${email address}>"
-
-Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
-You need a Passphrase to protect your secret key. # Fill in the password, which will be often used in the packaging process in the future
-```
-
-### 3. View key
-
-```shell
-$ gpg --list-keys
-pub rsa4096/579C25F5 2021-04-26 # 579C25F5 is the key id
-uid [ultimate] ${enter username} <${email address}>
-sub rsa4096 2021-04-26
-
-# Send public key to keyserver by key id
-$ gpg --keyserver pgpkeys.mit.edu --send-key 579C25F5
-# Among them, pgpkeys.mit.edu is a randomly selected keyserver, and the keyserver list is: https://sks-keyservers.net/status/, which are automatically synchronized with each other, and you can choose any one.
-$ gpg --keyserver hkp://pgpkeys.mit.edu --recv-keys 579C25F5 # Verify whether it is synchronized to the public network, if the network is not good, you may need to try a few more times
-```
-
-**Note: If there are multiple public keys, set the default key. ** Modify `~/.gnupg/gpg.conf`
-
-```sh
-# If you have more than 1 secret key in your keyring, you may want to
-# uncomment the following option and set your preferred keyid.
-default-key 28681CB1
-```
-
-**If there are multiple public keys, useless keys can also be deleted:**
-
-```shell
-$ gpg --delete-secret-keys 29BBC3CB # Delete the private key first and specify the key id
-gpg (GnuPG) 2.2.27; Copyright (C) 2021 g10 Code GmbH
-This is free software: you are free to change and redistribute it.
-There is NO WARRANTY, to the extent permitted by law.
-
-sec rsa4096/EE8DAE7D29BBC3CB 2021-04-27 mikexue <mi...@apache.org>
-
-Delete this key from the keyring? (y/N) y
-This is a secret key! - really delete? (y/N) y
-```
-
-```shell
-$ gpg --delete-keys 29BBC3CB # delete public key, specify key id
-gpg (GnuPG) 2.2.27; Copyright (C) 2021 g10 Code GmbH
-This is free software: you are free to change and redistribute it.
-There is NO WARRANTY, to the extent permitted by law.
-
-
-pub rsa4096/EE8DAE7D29BBC3CB 2021-04-27 mikexue <mi...@apache.org>
-
-Delete this key from the keyring? (y/N) y
-```
-
-Since the public key server has no checking mechanism, anyone can upload the public key in your name, so there is no way to guarantee the reliability of the public key on the server. Usually, you can publish a public key fingerprint on the website, so that others can check whether the downloaded public key is genuine.
-
-```shell
-# The fingerprint parameter generates a public key fingerprint:
-$ gpg --fingerprint mikexue
-pub rsa4096 2021-04-26 [SCA]
- F84A 0041 D70B 37AF 9C7B F0B3 39F4 29D7 579C 25F5
-uid [ultimate] mikexue <mi...@apache.org>
-sub rsa4096 2021-04-26 [E]
-```
-
-Log in to [https://id.apache.org](https://id.apache.org/), paste the above fingerprint (ie F84A 0041 D70B 37AF 9C7B F0B3 39F4 29D7 579C 25F5) into your user information OpenPGP Public Key Primary Fingerprint
-
-
-
-## Publish the Apache Maven repository
-
-> Note: EventMesh uses Gradle to build, you need to modify the gradle related configuration
-
-### 1. Export the private key file
-
-```shell
-$ gpg --export-secret-keys -o secring.gpg #The private key file is kept properly, and it needs to be configured later
-```
-
-### 2. Prepare branch
-
-Pull the new branch from the trunk branch as the release branch. If you want to release the $`{release_version}` version now, pull the new branch `${release_version}-release` from the develop branch, and then `${release_version}` Release Candidates involves The modification and labeling of all files are carried out in the `${release_version}-release` branch, and merged into the main branch after the final release is completed.
-
-### 3. Update version description
-
-Update the following files of the official website project and submit them to the master branch:
-
-https://github.com/apache/incubator-eventmesh-site/tree/master/events/release-notes
-
-### 4. Configure the gradle.properties file under the root project
-
-```shell
-group=org.apache.eventmesh
-version=1.2.0-release
-#The last 8 digits of the 40-bit public key
-signing.keyId=579C25F5
-#passphrase filled in when generating the key
-signing.password=
-#Exported private key file secring.gpg path
-signing.secretKeyRingFile=../secring.gpg
-#apache account
-apacheUserName=
-#apache password
-apachePassWord=
-```
-
-### 5. Check the gradle.properties file under the submodule
-
-```shell
-group=org.apache.eventmesh
-version=${release_version}
-```
-
-### 6. Check and configure the build.gradle file under the root project
-
-```shell
-publishing {
- publications {
- mavenJava(MavenPublication) {
- from components.java
- artifact packageSources
- artifact package Javadoc
- versionMapping {
- usage('java-api') {
- fromResolutionOf('runtimeClasspath')
- }
diff --git a/i18n/zh/docusaurus-plugin-content-docs-community/current/01-contribute.md b/i18n/zh/docusaurus-plugin-content-docs-community/current/01-contribute.md
index b8eb9b6f..5d1dbb0a 100644
--- a/i18n/zh/docusaurus-plugin-content-docs-community/current/01-contribute.md
+++ b/i18n/zh/docusaurus-plugin-content-docs-community/current/01-contribute.md
@@ -1,5 +1,5 @@
---
-title: How to Contribute
+title: 如何贡献
sidebar_position: 0
---
diff --git a/i18n/zh/docusaurus-plugin-content-docs-community/current/02-how-to-subscribe.md b/i18n/zh/docusaurus-plugin-content-docs-community/current/02-how-to-subscribe.md
index 79af38f2..cf75ebc0 100644
--- a/i18n/zh/docusaurus-plugin-content-docs-community/current/02-how-to-subscribe.md
+++ b/i18n/zh/docusaurus-plugin-content-docs-community/current/02-how-to-subscribe.md
@@ -1,5 +1,5 @@
---
-title: How to Subscribe
+title: 如何订阅
sidebar_position: 1
---
diff --git a/i18n/zh/docusaurus-plugin-content-docs-community/current/03-how-to-use-email.md b/i18n/zh/docusaurus-plugin-content-docs-community/current/03-how-to-use-email.md
new file mode 100644
index 00000000..c26bd73d
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs-community/current/03-how-to-use-email.md
@@ -0,0 +1,93 @@
+---
+title: 如何使用邮件列表
+sidebar_position: 2
+---
+
+# 如何使用邮件列表
+
+## Apache email usage based on Gmail
+
+> 当成为 Committer 后，你就会拥有一个 Apache 邮箱，本教程基于 `Gmail` 使用 Apache 邮箱。
+
+#### 1. 登录Gmail
+
+* [Gmail's official website](https://gmail.google.com) 在这里
+
+#### 2. 设置你的 Apache 邮箱
+
+#### 3. 点开设置
+
+
+
+#### 4. 找到你的 Apache 邮箱
+
+你的邮箱里应该有这样一封来自`root@apache.org`的邮件：
+
+- 标题为`Welcome to the Apache Software Foundation`
+- 内容如下
+
+```text
+Dear YYYY,
+Good news! We have created your Apache Software Foundation (ASF) committer account, and it is now ready for you.
+Your ApacheID is: xxxx
+......
+```
+
+* 你的 Apache 邮箱为`xxxx@apache.org`
+
+#### 5. 添加 Apache 邮箱
+
+* 登录到 [id.apache.org](https://id.apache.org/), 配置你的apache邮箱转发地址
+
+
+
+* 添加apache邮箱至Gmail配置
+
+
+
+> 未配置前，默认使用Gmail邮箱发送，可以添加apache邮箱作为默认发送邮箱。这个过程需要相关的配置和邮箱来确认和验证。
+
+## 基于`163/126邮箱`的Apache邮箱使用方法
+
+#### 1. 登录到163/126邮箱
+
+* [163 email website](https://mail.163.com) 在这里
+* [126 email website](https://mail.126.com/) 在这里
+
+#### 2. 设置你的Apache邮箱的转发地址
+
+
+
+设置这一步之后，你就可以收到你的apache邮箱的邮件
+
+#### 3. 设置126邮箱
+
+
+
+1. 选择设置
+2. 添加发件人
+3. 填写你的apache邮箱以及相关信息并且选择下一步
+
+
+
+4. 继续选择下一步
+
+
+
+5. 设置apache邮箱作为默认邮箱
+
+#### 4. 发送邮件
+
+
+
+你可以选择邮件的发件人
+
+## 附录
+
+* **QQ邮箱切换纯文本格式**
+
+
+
+* **邮箱配置回复默认主题关键字** 中文`回复：`会存在问题
+
+* **修改邮箱常规设置** 
diff --git a/i18n/zh/docusaurus-plugin-content-docs-community/current/04-release.md b/i18n/zh/docusaurus-plugin-content-docs-community/current/04-release.md
index 5d33b272..6c3895b8 100644
--- a/i18n/zh/docusaurus-plugin-content-docs-community/current/04-release.md
+++ b/i18n/zh/docusaurus-plugin-content-docs-community/current/04-release.md
@@ -1,3 +1,8 @@
+---
+title: Apache 发布指南
+sidebar_position: 3
+---
+
# Apache 发布指南
## 理解 Apache 发布的内容和流程
diff --git a/static/images/serverlessworkflow-official.png b/static/images/serverlessworkflow-official.png
new file mode 100644
index 00000000..721dc24e
Binary files /dev/null and b/static/images/serverlessworkflow-official.png differ
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@eventmesh.apache.org
For additional commands, e-mail: commits-help@eventmesh.apache.org