This is an automated email from the ASF dual-hosted git repository.
kirs pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler-website.git
The following commit(s) were added to refs/heads/master by this push:
new a951610 Update docs for community (#334)
a951610 is described below
commit a951610a02c0c20ba658ff981244283f26debdde
Author: Shiwen Cheng <[email protected]>
AuthorDate: Tue Apr 27 22:59:50 2021 +0800
Update docs for community (#334)
---
community/en-us/development/DS-License.md | 2 +-
community/en-us/development/become-a-committer.md | 2 +-
community/en-us/development/code-conduct.md | 10 +++----
community/en-us/development/commit-message.md | 8 +-----
community/en-us/development/contribute.md | 2 +-
community/en-us/development/document.md | 14 +++++-----
community/en-us/development/issue.md | 2 ++
community/en-us/development/microbench.md | 8 +-----
community/en-us/development/pull-request.md | 2 ++
community/en-us/development/submit-code.md | 2 +-
community/en-us/development/subscribe.md | 2 ++
community/en-us/security.md | 3 +-
community/en-us/team.md | 16 ++++-------
community/zh-cn/development/DS-License.md | 2 +-
community/zh-cn/development/become-a-committer.md | 3 +-
community/zh-cn/development/code-conduct.md | 1 +
community/zh-cn/development/commit-message.md | 2 +-
community/zh-cn/development/contribute.md | 2 +-
community/zh-cn/development/document.md | 2 +-
community/zh-cn/development/issue.md | 2 ++
community/zh-cn/development/microbench.md | 11 ++++----
community/zh-cn/development/pull-request.md | 2 ++
community/zh-cn/development/submit-code.md | 2 +-
community/zh-cn/development/subscribe.md | 2 ++
community/zh-cn/security.md | 3 +-
community/zh-cn/team.md | 18 ++++--------
site_config/community.jsx | 34 +++++++++++------------
27 files changed, 74 insertions(+), 85 deletions(-)
diff --git a/community/en-us/development/DS-License.md
b/community/en-us/development/DS-License.md
index 8a03aa4..c3f13d7 100644
--- a/community/en-us/development/DS-License.md
+++ b/community/en-us/development/DS-License.md
@@ -1,4 +1,4 @@
-## DolphinScheduler-Contributor-License Policy
+# License Notice
As we know that DolphinScheduler is an open-source undergoing project at The
Apache Software Foundation (ASF), which means that you have to follow the
Apache way to become the DolphinScheduler contributor. Furthermore, Apache has
extremely strict rules according to the License. This passage will explain the
ASF license and how to avoid License risks at the early stage when you
participate in DolphinScheduler.
diff --git a/community/en-us/development/become-a-committer.md
b/community/en-us/development/become-a-committer.md
index b50d0e6..deac7d8 100644
--- a/community/en-us/development/become-a-committer.md
+++ b/community/en-us/development/become-a-committer.md
@@ -1,4 +1,4 @@
-# How to become DolphinScheduler committer
+# How to Become DolphinScheduler Committer
Anyone can be a contributor to an Apache project. Being a contributor simply
means that you take an interest in the project and contribute in some way,
ranging from asking sensible questions (which documents the project and
provides feedback to developers) through to providing new features as patches.
diff --git a/community/en-us/development/code-conduct.md
b/community/en-us/development/code-conduct.md
index 11c1b7e..b3c0fbf 100644
--- a/community/en-us/development/code-conduct.md
+++ b/community/en-us/development/code-conduct.md
@@ -1,22 +1,22 @@
-## Code of Conduct
+# Code of Conduct
The following Code of Conduct is based on full compliance with the [Apache
Software Foundation Code of
Conduct](https://www.apache.org/foundation/policies/conduct.html).
-### Development philosophy.
+## Development philosophy
- **Consistent** code style, naming, and usage are consistent.
- **Easy to read** code is obvious, easy to read and understand, when
debugging one knows the intent of the code.
- **Neat** agree with the concepts of《Refactoring》and《Code Cleanliness》and
pursue clean and elegant code.
- **Abstract** hierarchy is clear and the concepts are refined and
reasonable. Keep methods, classes, packages, and modules at the same level of
abstraction.
- **Heart** Maintain a sense of responsibility and continue to be carved in
the spirit of artisans.
-### Development specifications.
+## Development specifications
- Executing `mvn -U clean package -Prelease` can compile and test through all
test cases.
- The test coverage tool checks for no less than dev branch coverage.
- In the root directory, use Checkstyle to check your code for special
reasons for violating validation rules. The template location is located at
ds_check_style.xml.
- Follow the coding specifications.
-### Coding specifications.
+## Coding specifications
- Use linux line breaks.
- Indentation (including empty lines) is consistent with the last line.
@@ -42,7 +42,7 @@ The following Code of Conduct is based on full compliance
with the [Apache Softw
- Comments can only contain `javadoc`, `todo` and `fixme`.
- Exposed classes and methods must have javadoc, other classes and methods
and methods that override the parent class do not require javadoc.
-### Unit test specifications.
+## Unit test specifications
- Test code and production code are subject to the same code specifications.
- Unit tests are subject to AIR (Automatic, Independent, Repeatable) Design
concept.
diff --git a/community/en-us/development/commit-message.md
b/community/en-us/development/commit-message.md
index 26ac13a..92269a7 100644
--- a/community/en-us/development/commit-message.md
+++ b/community/en-us/development/commit-message.md
@@ -1,10 +1,4 @@
----
-title: Commit Message
-keywords: DolphinScheduler, commit message, contibuting
-description: This documentation outlines the commit message format for
contributing to dolphine scheduler
----
-
-## DolphinScheduler-Contributor-CommitMessage
+# Commit Message Notice
### Preface
diff --git a/community/en-us/development/contribute.md
b/community/en-us/development/contribute.md
index 35079f6..824999c 100644
--- a/community/en-us/development/contribute.md
+++ b/community/en-us/development/contribute.md
@@ -1,4 +1,4 @@
-## Contribute
+# Participate in Contributing
First of all, thank you very much for choosing and using DolphinScheduler, and
welcome to join the DolphinScheduler family!
diff --git a/community/en-us/development/document.md
b/community/en-us/development/document.md
index a232938..78c4950 100644
--- a/community/en-us/development/document.md
+++ b/community/en-us/development/document.md
@@ -1,8 +1,8 @@
-## Contribute documentation.
+# Documentation Notice
Good documentation is critical for any type of software. Any contribution that
can improve the DolphinScheduler documentation is welcome.
-### Get the document project.
+### Get the document project
Documentation for the DolphinScheduler project is maintained in a separate
[git repository](https://github.com/apache/dolphinscheduler-website).
@@ -12,13 +12,13 @@ First you need to fork the document project into your own
github repository, and
git clone https://github.com/<your-github-user-name>/dolphinscheduler-website
```
-### The document environment.
+### The document environment
The DolphinScheduler website is supported by
[docsite](https://github.com/chengshiwen/docsite-ext)
Make sure that your node version is 10+, docsite does not yet support versions
higher than 10.x.
-### Document build guide.
+### Document build guide
1. Run `npm install` in the root directory to install the dependencies.
@@ -38,13 +38,13 @@ If the latest version of node is installed locally,
consider using `nvm` to allo
Now you can run and build the website in your local environment.
-### The document specification.
+### The document specification
1. ** Spaces are Required ** between Chinese characters and English or numbers
and ** Spaces are not required ** between Chinese punctuation marks and English
or numbers, to enhance the aesthetics and readability of the Chinese-English
mix.
2. It is recommended that you use "you" in general. Of course, you can use the
term when necessary, such as when there is a warning prompt.
-### How to submit a document Pull Request.
+### How to submit a document Pull Request
1. Do not use "git add." to commit all changes.
@@ -55,6 +55,6 @@ Now you can run and build the website in your local
environment.
3. Submit the Pull Request to the **master** branch.
-### Reference to the documentation.
+### Reference to the documentation
[Apache Flink Translation
Specifications](https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications)
diff --git a/community/en-us/development/issue.md
b/community/en-us/development/issue.md
index da3129c..376b065 100644
--- a/community/en-us/development/issue.md
+++ b/community/en-us/development/issue.md
@@ -1,3 +1,5 @@
+# Issue Notice
+
## Preface
Issues function is used to track various Features, Bugs, Functions, etc. The
project maintainer can organize the tasks to be completed through issues.
diff --git a/community/en-us/development/microbench.md
b/community/en-us/development/microbench.md
index 4037b43..5cf148c 100644
--- a/community/en-us/development/microbench.md
+++ b/community/en-us/development/microbench.md
@@ -1,10 +1,4 @@
----
-title: Micro BenchMark Notice
-keywords: dolphinscheduler, microbenchmark
-description: This file describes several points of benchmark testing
----
-
-## DolphinSchedulerMicroBench Microbenchmark
+# Micro BenchMark Notice
All optimization must be based on data verification, and blind optimization is
rejected. Based on this, we provide the MicroBench module.
diff --git a/community/en-us/development/pull-request.md
b/community/en-us/development/pull-request.md
index 608ab79..13571d0 100644
--- a/community/en-us/development/pull-request.md
+++ b/community/en-us/development/pull-request.md
@@ -1,3 +1,5 @@
+# Pull Request Notice
+
## Preface
Pull Request is a way of software cooperation, which is a process of bringing
code involving different functions into the trunk. During this process, the
code can be discussed, reviewed, and modified.
diff --git a/community/en-us/development/submit-code.md
b/community/en-us/development/submit-code.md
index f3af348..83ca395 100644
--- a/community/en-us/development/submit-code.md
+++ b/community/en-us/development/submit-code.md
@@ -1,4 +1,4 @@
-#### How to submit
+# Submit Code
* First from the remote repository
*https://github.com/apache/dolphinscheduler.git* fork a copy of the code into
your own repository
diff --git a/community/en-us/development/subscribe.md
b/community/en-us/development/subscribe.md
index 3d972d9..ee12ba9 100644
--- a/community/en-us/development/subscribe.md
+++ b/community/en-us/development/subscribe.md
@@ -1,3 +1,5 @@
+# Subscribe Mailing Lists
+
It is highly recommended to subscribe to the development mailing list to keep
up-to-date with the community.
In the process of using DolphinScheduler, if you have any questions or ideas,
suggestions, you can participate in the DolphinScheduler community building
through the Apache mailing list. Sending a subscription email is also very
simple, the steps are as follows:
diff --git a/community/en-us/security.md b/community/en-us/security.md
index e6dee3d..28bcda1 100644
--- a/community/en-us/security.md
+++ b/community/en-us/security.md
@@ -1,4 +1,5 @@
-## Security
+# Security
+
The Apache Software Foundation takes a rigorous stance on eliminating security
issues in its software projects. Apache DolphinScheduler is also very concerned
Security issues related to its features and functionality.
If you have apprehensions regarding DolphinScheduler’s security or you
discover vulnerability or potential threat, don’t hesitate to get in touch with
the Apache Security Team by dropping a mail at
[[email protected]](mailto:[email protected]). Please specify the project
name as DolphinScheduler in the email and provide a description of the relevant
problem or potential threat. You are also urged to recommend the way to
reproduce and replicate the issue. The apache security team and [...]
diff --git a/community/en-us/team.md b/community/en-us/team.md
index 96c6de9..07ee185 100644
--- a/community/en-us/team.md
+++ b/community/en-us/team.md
@@ -1,10 +1,3 @@
----
-title: Team
-linkTitle: Team
-description: About DolphinScheduler Team.
-
----
-
# DolphinScheduler Team
The DolphinScheduler team is comprised of Members and Contributors. Members
have direct access to the source of DolphinScheduler project and actively
evolve the code-base. Contributors improve the project through submission of
patches and suggestions to the Members. The number of Contributors to the
project is unbounded. All contributions to DolphinScheduler are greatly
appreciated, whether for trivial cleanups, big new features or other material
rewards.
@@ -13,7 +6,7 @@ The DolphinScheduler team is comprised of Members and
Contributors. Members have
### PMC
-| Public Name | Apache ID | GitHub |
+| Public Name | Apache ID | GitHub ID |
| ----------------- | ------------ | -------------- |
| Furkan Kamaci | kamaci | kamaci |
| Gang Li | lgcareer | lgcareer |
@@ -34,10 +27,12 @@ The DolphinScheduler team is comprised of Members and
Contributors. Members have
### Committer
-| Public Name | Apache ID | GitHub |
+| Public Name | Apache ID | GitHub ID |
| ------------- | ------------ | ---------------- |
+| BoYi Zhang | zhangboyi | BoYiZhang |
| Caibiao Xiang | break60 | break60 |
| Calvin Kirs | kirs | CalvinKirs |
+| Chong Zhuang | kerwin | zhuangchong |
| Cong Huang | chongchongzi | chongchongzi |
| Hemin Wen | wenhemin | wen-hemin |
| Kai Zhu | zhukai | nauu |
@@ -46,12 +41,12 @@ The DolphinScheduler team is comprised of Members and
Contributors. Members have
| Lin Li | lilin | samz406 |
| Shang Lou | clay4megtr | clay4444 |
| Shaojie Wu | gabrywu | gabrywu |
+| Shiwen Cheng | chengshiwen | chengshiwen |
| Wenhe Li | liwenhe | liwenhe1993 |
| Xingchun Chen | chenxingchun | xingchun-chen |
| Yichao Yang | yangyichao | yangyichao-mango |
| Zongyao Zhang | lfyee | lfyee |
-
## Contributors
DolphinScheduler have hundreds of contributors, you could find them in our
repositories' contribution list.
@@ -69,4 +64,3 @@ The DolphinScheduler community follows the [Apache
Community’s process](http:/
1. Start the discussion and vote in @private. Only current PMC member could
nominate.
2. If the vote passes, send an offer to become a committer with @private CC’ed.
3. Setup committer rights
-
diff --git a/community/zh-cn/development/DS-License.md
b/community/zh-cn/development/DS-License.md
index 364ede0..dd5679a 100644
--- a/community/zh-cn/development/DS-License.md
+++ b/community/zh-cn/development/DS-License.md
@@ -1,4 +1,4 @@
-## DolphinScheduler-Contributor-LICENSE篇
+# License 须知
如您所知，DolphinScheduler现属于ASF(Apache基金会)下的开源项目，这意味着当您想要成为DolphinScheduler的贡献者的时候，就必须按照Apache的规则来，而Apache对于License有着极其严苛的规则，为了避免贡献者在License上浪费过多的时间，
本文将为您讲解ASF—License以及参与DolphinScheduler如何过早的规避掉License风险。
diff --git a/community/zh-cn/development/become-a-committer.md
b/community/zh-cn/development/become-a-committer.md
index 8fa92ae..b38dd0c 100644
--- a/community/zh-cn/development/become-a-committer.md
+++ b/community/zh-cn/development/become-a-committer.md
@@ -1,5 +1,4 @@
-# 如何成为 DolphinScheduler committer
-
+# 如何成为 DolphinScheduler Committer
每个人都可以成为Apache项目的贡献者。作为一个贡献者只是意味着你对项目感兴趣并以某种方式做出贡献，从提出合理的问题（这些问题记录了项目并向开发人员提供反馈）到提供新的特性作为补丁。
diff --git a/community/zh-cn/development/code-conduct.md
b/community/zh-cn/development/code-conduct.md
index 4024d9e..a3668b5 100644
--- a/community/zh-cn/development/code-conduct.md
+++ b/community/zh-cn/development/code-conduct.md
@@ -1,3 +1,4 @@
+# 行为准则
以下行为准则以完全遵循[Apache软件基金会行为准则](https://www.apache.org/foundation/policies/conduct.html)为前提。
diff --git a/community/zh-cn/development/commit-message.md
b/community/zh-cn/development/commit-message.md
index 9325960..3b1b0e8 100644
--- a/community/zh-cn/development/commit-message.md
+++ b/community/zh-cn/development/commit-message.md
@@ -1,4 +1,4 @@
-## DolphinScheduler-Contributor-CommitMessage篇
+# Commit Message 须知
### 前言
一个好的 commit message
是能够帮助其他的开发者（或者未来的开发者）快速理解相关变更的上下文，同时也可以帮助项目管理人员确定该提交是否适合包含在发行版中。但当我们在查看了很多开源项目的
commit log 后，发现一个有趣的问题，一部分开发者，代码质量很不错，但是 commit message
记录却比较混乱，当其他贡献者或者学习者在查看代码的时候，并不能通过 commit log 很直观的了解
diff --git a/community/zh-cn/development/contribute.md
b/community/zh-cn/development/contribute.md
index c43ab18..a8b0a2d 100644
--- a/community/zh-cn/development/contribute.md
+++ b/community/zh-cn/development/contribute.md
@@ -1,4 +1,4 @@
-## 贡献
+# 参与贡献
首先非常感谢大家选择和使用 DolphinScheduler，非常欢迎大家加入 DolphinScheduler 大家庭，融入开源世界！
diff --git a/community/zh-cn/development/document.md
b/community/zh-cn/development/document.md
index b061a3a..45f060a 100644
--- a/community/zh-cn/development/document.md
+++ b/community/zh-cn/development/document.md
@@ -1,4 +1,4 @@
-## 贡献文档
+# 文档须知
良好的使用文档对任何类型的软件都是至关重要的。欢迎任何可以改进 DolphinScheduler 文档的贡献。
diff --git a/community/zh-cn/development/issue.md
b/community/zh-cn/development/issue.md
index b26f62f..b81cbd8 100644
--- a/community/zh-cn/development/issue.md
+++ b/community/zh-cn/development/issue.md
@@ -1,3 +1,5 @@
+# Issue 须知
+
## 前言
Issues 功能被用来追踪各种特性，Bug，功能等。项目维护者可以通过 Issues 来组织需要完成的任务。
diff --git a/community/zh-cn/development/microbench.md
b/community/zh-cn/development/microbench.md
index 6fec272..97f37ae 100644
--- a/community/zh-cn/development/microbench.md
+++ b/community/zh-cn/development/microbench.md
@@ -1,11 +1,12 @@
-#### DolphinSchedulerMicroBench 微基准测试
+# 微基准测试须知
+
所有的优化必须建立在数据印证的基础上，拒绝盲目优化。基于此，我们提供了MicroBench模块。
MicroBench模块是基于OpenJDK JMH构件的（HotSpot的推荐基准测试方案）。当你开始基准测试时，你不需要额外的依赖。
JMH，即Java MicroBenchmark Harness，是专门用于代码微基准测试的工具套件。何谓Micro
Benchmark呢？简单的来说就是基于方法层面的基准测试，精度可以达到微秒级。当你定位到热点方法，希望进一步优化方法性能的时候，就可以使用JMH对优化的结果进行量化的分析。
-##### Java基准测试需要注意的几个点：
+### Java基准测试需要注意的几个点：
* 防止无用代码进入测试方法中。
@@ -13,7 +14,7 @@ JMH，即Java MicroBenchmark Harness，是专门用于代码微基准测试的
* 测试结果呈现。
-##### JMH比较典型的应用场景有：
+### JMH比较典型的应用场景有：
* 1:定量分析某个热点函数的优化效果
@@ -24,7 +25,7 @@ JMH，即Java MicroBenchmark Harness，是专门用于代码微基准测试的
DolphinScheduler-MicroBench提供了AbstractBaseBenchmark,你可以在其基础上继承，编写你的基准测试代码，AbstractMicroBenchmark能保证以JUnit的方式运行。
-##### 定制运行参数
+### 定制运行参数
默认的AbstractMicrobenchmark配置是
@@ -36,7 +37,7 @@ DolphinScheduler-MicroBench提供了AbstractBaseBenchmark,你可以在其基础
你可以在启动的时候指定这些参数，-DmeasureIterations、-DperfReportDir（输出基准测试结果文件目录）、-DwarmupIterations、-DforkCount
-##### DolphinScheduler-MicroBench 介绍
+### DolphinScheduler-MicroBench 介绍
通常并不建议跑测试时，用较少的循环次数，但是较少的次数有助于确认基准测试时工作的，在确认结束后，再运行大量的基准测试。
diff --git a/community/zh-cn/development/pull-request.md
b/community/zh-cn/development/pull-request.md
index 0c8c546..bc072ea 100644
--- a/community/zh-cn/development/pull-request.md
+++ b/community/zh-cn/development/pull-request.md
@@ -1,3 +1,5 @@
+# Pull Request 须知
+
## 前言
Pull Request 本质上是一种软件的合作方式，是将涉及不同功能的代码，纳入主干的一种流程。这个过程中，可以进行讨论、审核和修改代码。
diff --git a/community/zh-cn/development/submit-code.md
b/community/zh-cn/development/submit-code.md
index 5830f80..b640f08 100644
--- a/community/zh-cn/development/submit-code.md
+++ b/community/zh-cn/development/submit-code.md
@@ -1,4 +1,4 @@
-#### 提交代码流程
+# 提交代码
* 首先从远端仓库*https://github.com/apache/dolphinscheduler.git* fork一份代码到自己的仓库中
diff --git a/community/zh-cn/development/subscribe.md
b/community/zh-cn/development/subscribe.md
index f54768a..13783d0 100644
--- a/community/zh-cn/development/subscribe.md
+++ b/community/zh-cn/development/subscribe.md
@@ -1,3 +1,5 @@
+# 订阅邮件列表
+
强烈推荐订阅开发邮件列表，与社区保持最新信息同步，这一点非常重要。
在使用DolphinScheduler的过程中，如果您有任何问题或者想法、建议，都可以通过Apache邮件列表参与到DolphinScheduler的社区建设中来。
diff --git a/community/zh-cn/security.md b/community/zh-cn/security.md
index 0cb86f6..6fef3cc 100644
--- a/community/zh-cn/security.md
+++ b/community/zh-cn/security.md
@@ -1,4 +1,5 @@
-## 安全
+# 安全
+
Apache Software Foundation在消除其软件项目中的安全性问题方面采取严格的立场。 Apache
DolphinScheduler也非常关注与其功能有关的安全性问题。
如果您对DolphinScheduler的安全性有疑虑，或者发现了漏洞或潜在威胁，请发送邮件至[[email protected]]（mailto：[email protected]），与Apache安全团队联系。
请在电子邮件中将项目名称指定为DolphinScheduler，并提供相关问题或潜在威胁的描述。 还敦促您推荐重现和复制问题的方法。
在评估和分析调查结果之后，apache安全团队和DolphinScheduler社区将与您联系。
diff --git a/community/zh-cn/team.md b/community/zh-cn/team.md
index 9a9e442..ec9b219 100644
--- a/community/zh-cn/team.md
+++ b/community/zh-cn/team.md
@@ -1,21 +1,12 @@
----
-标题：团队
-链接标题：团队
-描述：关于 DolphinScheduler 团队。
-
----
-
# DolphinScheduler 团队
DolphinScheduler 团队由成员和贡献者组成。 成员可以直接访问 DolphinScheduler 项目的源代码并积极地开发代码库。
贡献者通过向成员提交补丁和建议来改善项目。 该项目的贡献者数量是无限的。 无论是琐碎的清理工作，重要的新功能还是其他重大的奖励，对
DolphinScheduler 所做的所有贡献都将受到极大的赞赏。
-
-
## 成员
### PMC
-| Public Name | Apache ID | GitHub |
+| Public Name | Apache ID | GitHub ID |
| ----------------- | ------------ | -------------- |
| Furkan Kamaci | kamaci | kamaci |
| Gang Li | lgcareer | lgcareer |
@@ -36,10 +27,12 @@ DolphinScheduler 团队由成员和贡献者组成。 成员可以直接访问 D
### Committer
-| Public Name | Apache ID | GitHub |
+| Public Name | Apache ID | GitHub ID |
| ------------- | ------------ | ---------------- |
+| BoYi Zhang | zhangboyi | BoYiZhang |
| Caibiao Xiang | break60 | break60 |
| Calvin Kirs | kirs | CalvinKirs |
+| Chong Zhuang | kerwin | zhuangchong |
| Cong Huang | chongchongzi | chongchongzi |
| Hemin Wen | wenhemin | wen-hemin |
| Kai Zhu | zhukai | nauu |
@@ -48,12 +41,12 @@ DolphinScheduler 团队由成员和贡献者组成。 成员可以直接访问 D
| Lin Li | lilin | samz406 |
| Shang Lou | clay4megtr | clay4444 |
| Shaojie Wu | gabrywu | gabrywu |
+| Shiwen Cheng | chengshiwen | chengshiwen |
| Wenhe Li | liwenhe | liwenhe1993 |
| Xingchun Chen | chenxingchun | xingchun-chen |
| Yichao Yang | yangyichao | yangyichao-mango |
| Zongyao Zhang | lfyee | lfyee |
-
## 贡献者
DolphinScheduler 有数百个贡献者，您可以在我们存储库的贡献列表中找到他们。
@@ -71,4 +64,3 @@ DolphinScheduler 社区在接受新提交者时遵循 [Apache 社区的流程](h
1.开始讨论并在 @private 中投票。 只有当前 PMC 成员可以提名。
2.如果投票通过，请发送邀请以成为 @private CC 的提交者。
3.设置提交者权限
-
diff --git a/site_config/community.jsx b/site_config/community.jsx
index aaa94a7..93874e2 100644
--- a/site_config/community.jsx
+++ b/site_config/community.jsx
@@ -17,7 +17,7 @@ export default {
title: 'Team',
children: [
{
- title: 'team introduce',
+ title: 'Team Introduction',
link: '/en-us/community/team.html',
},
],
@@ -26,7 +26,7 @@ export default {
title: 'Security',
children: [
{
- title: 'security introduce',
+ title: 'Security Introduction',
link: '/en-us/community/security.html',
},
],
@@ -35,15 +35,15 @@ export default {
title: 'Release Guide',
children: [
{
- title: 'release preparation',
+ title: 'Release Preparation',
link: '/en-us/community/release-prepare.html',
},
{
- title: 'release guide',
+ title: 'Release Guide',
link: '/en-us/community/release.html',
},
{
- title: 'release post',
+ title: 'Release Post',
link: '/en-us/community/release-post.html',
},
],
@@ -52,15 +52,15 @@ export default {
title: 'Contribution Guide',
children: [
{
- title: 'how to become a committer',
+ title: 'How to Become a Committer',
link: '/en-us/community/development/become-a-committer.html',
},
{
- title: 'Subscribe mail list',
+ title: 'Subscribe Mailing Lists',
link: '/en-us/community/development/subscribe.html',
},
{
- title: 'Participate in contributing',
+ title: 'Participate in Contributing',
link: '/en-us/community/development/contribute.html',
},
{
@@ -73,7 +73,7 @@ export default {
title: 'Submit Guide',
children: [
{
- title: 'Submit Pull Request Process',
+ title: 'Submit Code',
link: '/en-us/community/development/submit-code.html',
},
{
@@ -258,7 +258,7 @@ export default {
title: '贡献指南',
children: [
{
- title: '如何成为Dolphinscheduler的committer',
+ title: '如何成为DolphinScheduler Committer',
link: '/zh-cn/community/development/become-a-committer.html',
},
{
@@ -279,31 +279,31 @@ export default {
title: '提交者指南',
children: [
{
- title: '提交流程',
+ title: '提交代码',
link: '/zh-cn/community/development/submit-code.html',
},
{
- title: '参与贡献-License需知',
+ title: 'License须知',
link: '/zh-cn/community/development/DS-License.html',
},
{
- title: '参与贡献-文档需知',
+ title: '文档须知',
link: '/zh-cn/community/development/document.html',
},
{
- title: '参与贡献-Issue需知',
+ title: 'Issue须知',
link: '/zh-cn/community/development/issue.html',
},
{
- title: '参与贡献-Pull Request需知',
+ title: 'Pull Request须知',
link: '/zh-cn/community/development/pull-request.html',
},
{
- title: '参与贡献-CommitMessage需知',
+ title: 'Commit Message须知',
link: '/zh-cn/community/development/commit-message.html',
},
{
- title: '参与贡献-微基准测试',
+ title: '微基准测试须知',
link: '/zh-cn/community/development/microbench.html',
},
],
