This is an automated email from the ASF dual-hosted git repository.
zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new ad970bb2324 Modify some unreasonable specifications in the document
and format the document (#31404)
ad970bb2324 is described below
commit ad970bb2324dc30b17c3a20626594a3c6a073be0
Author: LJ <[email protected]>
AuthorDate: Mon May 27 23:18:12 2024 +0800
Modify some unreasonable specifications in the document and format the
document (#31404)
* Update
2022_06_16_Understanding_Apache_ShardingSphere's_SPI_and_why_it’s_simpler_than_Dubbo’s.en.md
According to the meaning of the documentation, there is no need for a list
to delete the document.
* Update
2022_06_28_Cloud_native_deployment_for_a_high-performance_data_gateway_new_API_driver_Apache_ShardingSphere_5.1.2_is_released.en.md
Modify unreasonable segmentation errors in the document.
* Update
2022_06_28_Cloud_native_deployment_for_a_high-performance_data_gateway_new_API_driver_Apache_ShardingSphere_5.1.2_is_released.en.md
Modify the related division as a three -level title.
* Update: Adjust the unreasonable document format in the document:
According to the semantics, change the orderly list in the document to the
sequence list.
* Update
2022_07_06_ShardingSphere-JDBC_Driver_Released_A_JDBC_Driver_That_Requires_No_Code_Modifications.en.md
The unreasonable place to modify the format in the document:
1. Add corresponding changes according to semantics.
2. Modify the thick symbols so that the document is shown normally.
* Update
2022_07_08_ShardingSphere-Proxy_Front-End_Protocol_Troubleshooting_Guide_and_Examples.en.md
The unreasonable place to modify the format in the document:
1. Partial change of the line is abnormal;
2. Add the corresponding multi -level title;
3. Adjust the corresponding disorderly list according to the semantics;
* Update community.cn.md
Modify the spacing between Chinese and English in the document.
* Update alpha.cn.md
Optimize docs
* Chinese and English documents are synchronized.
* Update
Oct_12_9_ShardingSphere_JD_Baitiao_Story_of_an_Implementation_Journey.cn.md
Delete redundant unordered lists.
* Update
Oct_12_9_ShardingSphere_JD_Baitiao_Story_of_an_Implementation_Journey.cn.md
Remove unwanted unordered list symbols from the document.
* Update
Oct_12_8_ShardingSphere_Google_Summer_of_Code_Students_How_Was_Your_Open_Source_Experience.en.md
Modify unreasonable document syntax format: Change the bold match to make
it normal bold.
* Update
Oct_12_7_openGauss_ShardingSphere_One_of_the_Top_Distribution_Solutions.cn.md
Add an ordered list, depending on the semantics.
* Update
Oct_12_7_openGauss_ShardingSphere_One_of_the_Top_Distribution_Solutions.cn.md
Unified document format based on Chinese and English documents.
---
...gSphere_One_of_the_Top_Distribution_Solutions.cn.md | 16 ++++++++--------
..._Students_How_Was_Your_Open_Source_Experience.en.md | 18 +++++++++---------
...JD_Baitiao_Story_of_an_Implementation_Journey.cn.md | 4 +---
docs/blog/content/material/Open_source_community.cn.md | 4 ++++
docs/blog/content/material/alpha.cn.md | 4 ++--
docs/blog/content/material/community.cn.md | 16 ++++++++--------
6 files changed, 32 insertions(+), 30 deletions(-)
diff --git
a/docs/blog/content/material/Oct_12_7_openGauss_ShardingSphere_One_of_the_Top_Distribution_Solutions.cn.md
b/docs/blog/content/material/Oct_12_7_openGauss_ShardingSphere_One_of_the_Top_Distribution_Solutions.cn.md
index 8fb0d655368..52c102b0bfc 100644
---
a/docs/blog/content/material/Oct_12_7_openGauss_ShardingSphere_One_of_the_Top_Distribution_Solutions.cn.md
+++
b/docs/blog/content/material/Oct_12_7_openGauss_ShardingSphere_One_of_the_Top_Distribution_Solutions.cn.md
@@ -23,36 +23,36 @@ openGauss 融合了众多开源组件，用以构建集数据水平扩展、分
## 产品优势
-1.极致扩展能力，灵活扩缩容
+- 极致扩展能力，灵活扩缩容
计算与存储能力可通过水平拆分实现线性扩展，最高可达数据 6400
分片，性能随扩展准线性增长，可有效解决单表数据量膨胀问题；结合业务流量，灵活平滑进行数据节点的扩缩容，智能读写分离，实现分布式数据库的自动负载均衡。
-2.丰富企业级特性
+- 丰富企业级特性
支持分布式存储过程、触发器，分布式事务，全密态数据加密，WDR 诊断报告，提供丰富的企业级特性。
-3.一键部署，屏蔽底层依赖
+- 一键部署，屏蔽底层依赖
标准化镜像确保多环境一致性交付，容器化部署，实现物理资源池化，降低对平台的依赖性，简洁高效，实现应用秒级部署。
-4.超高可用，实现异地容灾
+- 超高可用，实现异地容灾
强有力的集群管理、运维能力，支持同城、异地、多地多中心灵活部署，基于 Paxos 协议保证数据的安全及强一致性，提供 RPO=0 的多种容灾能力。
-5.开源开放，构建全栈生态
+- 开源开放，构建全栈生态
开源 openGauss 单机及分布式解决方案，鼓励更多伙伴、开发者共同参与其中，共建数据库的繁荣生态，打造全栈开源生态链。
## 应用场景
-1.金融系统
+- 金融系统
基于多数派共识协议 Paxos，提供分布式强一致事务能力，确保分布式环境下数据的强一致能力；多地多中心，提供 RPO=0 的能力，保障金融级可靠。
-2.政企办公
+- 政企办公
提供全密态数据加密，安全可信，支持软硬件生态，保障高可用场景，为政企办公保驾护航。
-3.智慧电网
+- 智慧电网
支持同城、异地、多地多中心灵活部署，根据业务的潮汐特点灵活扩缩容，助力智慧电网。
diff --git
a/docs/blog/content/material/Oct_12_8_ShardingSphere_Google_Summer_of_Code_Students_How_Was_Your_Open_Source_Experience.en.md
b/docs/blog/content/material/Oct_12_8_ShardingSphere_Google_Summer_of_Code_Students_How_Was_Your_Open_Source_Experience.en.md
index a88f1d1184b..c6095a84bf2 100644
---
a/docs/blog/content/material/Oct_12_8_ShardingSphere_Google_Summer_of_Code_Students_How_Was_Your_Open_Source_Experience.en.md
+++
b/docs/blog/content/material/Oct_12_8_ShardingSphere_Google_Summer_of_Code_Students_How_Was_Your_Open_Source_Experience.en.md
@@ -47,7 +47,7 @@ Major: Business Informatics
**Thanoshan:** Here, in Sri Lanka, many of my seniors have already done the
Google Summer of Code. They strongly advised me to look at this opportunity and
told me that I should definitely try it. So, I researched the GSoC program, for
things such as “What is about? How can I work on that?”.
-**Liangda：**The first time I got to know GSoC was during last year’s summer, I
was surfing on the internet, and I accidentally found out a blog sharing about
some GSoC experiences and application tips. I was really fascinated by this
program. But at that time, open source was completely new for me, and I was not
confident enough. Then during the winter of 2020, I got the chance to work as a
research assistant at the university on a chatbot project using Rasa, which is
an open source conv [...]
+**Liangda：** The first time I got to know GSoC was during last year’s summer,
I was surfing on the internet, and I accidentally found out a blog sharing
about some GSoC experiences and application tips. I was really fascinated by
this program. But at that time, open source was completely new for me, and I
was not confident enough. Then during the winter of 2020, I got the chance to
work as a research assistant at the university on a chatbot project using Rasa,
which is an open source con [...]
> **What’s so great about the program anyway?**
@@ -55,7 +55,7 @@ Major: Business Informatics
> **What project did you work on during GSoC?**
-**Thanoshan:**ShardingSphere’s ANTLR project. I’m really interested in Java,
and Java related technologies and it’s my one of the favorite languages. Also,
I am very passionate about open source software development. So, I want to do
something in Java and open source, to learn more from other people, something
that allows me to collaborate with other people. The Java-related technology is
the main motivation, which actually drove me in this project.
+**Thanoshan:** ShardingSphere’s ANTLR project. I’m really interested in Java,
and Java related technologies and it’s my one of the favorite languages. Also,
I am very passionate about open source software development. So, I want to do
something in Java and open source, to learn more from other people, something
that allows me to collaborate with other people. The Java-related technology is
the main motivation, which actually drove me in this project.
**Liangda:** My GSoC project contributes to Apache ShardingSphere’s parser
engine, which handles different database SQLs like MySQL, PostgreSQL, Oracle
etc. And I was focusing on proofreading the Oracle SQL definition of DDL (Data
Definition Language) and TCL (Transaction Control language).
@@ -77,35 +77,35 @@ However, the Apache ShardingSphere is a nice and friendly
community, my question
> **How was your experience as a GSoC student?**
-**Liangda:**It was a really great experience. The program is well organized
with clear timeline and schedule. I was able to learn a lot about open source
development and improve my skills and knowledge. The GSoC student summit at the
end of the program was also really interesting and informative.
+**Liangda:** It was a really great experience. The program is well organized
with clear timeline and schedule. I was able to learn a lot about open source
development and improve my skills and knowledge. The GSoC student summit at the
end of the program was also really interesting and informative.
>**What did you do differently in order to get selected for GSoC by
>ShardingSphere?**
-**Liangda:**I think I was really motivated and I’m able to dive deep into the
issues I faced to find the root cause. If I could not solve the issue by
myself, I’m not afraid to ask on GitHub directly. This makes me get started
quickly.
+**Liangda:** I think I was really motivated and I’m able to dive deep into the
issues I faced to find the root cause. If I could not solve the issue by
myself, I’m not afraid to ask on GitHub directly. This makes me get started
quickly.
And after I got familiar with my project, I also worked proactively to answer
questions, review pull requests and fix other small issues. Beside this, when I
was writing my project proposal, I communicated with my mentor regularly and
asked for early feedback. It is important to know mentors’ expectations.
>**How was your experience as a GSoC student?**
-**Liangda：**It was a really great experience. The program is well organized
with clear timeline and schedule. I was able to learn a lot about open source
development and improve my skills and knowledge. The GSoC student summit at the
end of the program was also really interesting and informative.
+**Liangda：** It was a really great experience. The program is well organized
with clear timeline and schedule. I was able to learn a lot about open source
development and improve my skills and knowledge. The GSoC student summit at the
end of the program was also really interesting and informative.
>**What did you do differently in order to get selected for GSoC by
>ShardingSphere?**
-**Liangda: **I think I was really motivated and I’m able to dive deep into the
issues I faced to find the root cause. If I could not solve the issue by
myself, I’m not afraid to ask on GitHub directly. This makes me get started
quickly.
+**Liangda:** I think I was really motivated and I’m able to dive deep into the
issues I faced to find the root cause. If I could not solve the issue by
myself, I’m not afraid to ask on GitHub directly. This makes me get started
quickly.
And after I got familiar with my project, I also worked proactively to answer
questions, review pull requests and fix other small issues. Beside this, when I
was writing my project proposal, I communicated with my mentor regularly and
asked for early feedback. It is important to know mentors’ expectations.
> **Is there anything that you would like to say to students who are looking
> forward to work with ShardingSphere in GSoC? Or do you have any tips for
> them?**
-**Thanoshan:**I would say there will be some projects that will be specified
by the mentors and the ShardingSphere community. So, students will have to
participate in the community even before the GSoC.
+**Thanoshan:** I would say there will be some projects that will be specified
by the mentors and the ShardingSphere community. So, students will have to
participate in the community even before the GSoC.
Students can approach the ShardingSphere community even before the program and
work on some preliminary tasks related to the GSoC’s main task, which will
definitely help them compete in the selection process. So, I would say that
they should approach the ShardingSphere community as early as possible.
-**Liangda:**Yes, I would highly recommend it and it will be a great experience
for sure. There are some issues labeled as “good first issue” or “volunteer
wanted”. Just go and try it as soon as possible! The easiest way to get started
is learning by doing. And if you feel blocked, don’t be afraid to ask questions
and express your thoughts! We are all here to support you!
+**Liangda:** Yes, I would highly recommend it and it will be a great
experience for sure. There are some issues labeled as “good first issue” or
“volunteer wanted”. Just go and try it as soon as possible! The easiest way to
get started is learning by doing. And if you feel blocked, don’t be afraid to
ask questions and express your thoughts! We are all here to support you!
> **Do you have any suggestions to improve ShardingSphere?**
-**Thanoshan:**To improve ShardingSphere? I mean it’s a huge project. And the
plus point I see here is the documentation. It’s great. So, to be honest with
you, I learned a lot about SQL. I worked on the SQL parser engine part of the
project, so I learned the concepts of the SQL parser engine in the
ShardingSphere project. For the improvement, I currently do not see anything
specific. Actually, ShardingSphere is a great one. I really love to collaborate
with the ShardingSphere community. [...]
+**Thanoshan:** To improve ShardingSphere? I mean it’s a huge project. And the
plus point I see here is the documentation. It’s great. So, to be honest with
you, I learned a lot about SQL. I worked on the SQL parser engine part of the
project, so I learned the concepts of the SQL parser engine in the
ShardingSphere project. For the improvement, I currently do not see anything
specific. Actually, ShardingSphere is a great one. I really love to collaborate
with the ShardingSphere community. [...]
It’s nice to see that ShardingSphere currently has been adding the setup
guides, so that the new contributors can easily jump to that document and read
and understand what they have to do. So, it’s a great thing to have. I am happy
for it.
diff --git
a/docs/blog/content/material/Oct_12_9_ShardingSphere_JD_Baitiao_Story_of_an_Implementation_Journey.cn.md
b/docs/blog/content/material/Oct_12_9_ShardingSphere_JD_Baitiao_Story_of_an_Implementation_Journey.cn.md
index 9092c817a6f..7d485cec703 100644
---
a/docs/blog/content/material/Oct_12_9_ShardingSphere_JD_Baitiao_Story_of_an_Implementation_Journey.cn.md
+++
b/docs/blog/content/material/Oct_12_9_ShardingSphere_JD_Baitiao_Story_of_an_Implementation_Journey.cn.md
@@ -162,7 +162,6 @@ DBRep 是 ShardingSphere-Scaling 产品设计的基石，Scaling 具备的自动
搭配使用 Scaling 同步迁移组件从容面对“618”和“11.11”等大型活动，系统灵活扩容。
--
### 写在最后
@@ -171,7 +170,6 @@ DBRep 是 ShardingSphere-Scaling 产品设计的基石，Scaling 具备的自动
互联网信用消费模式发展逐步多样化，未来 Apache ShardingSphere
将与京东展开更多业务场景的实践和探索，通过推动金融科技创新发展，进一步提升互联网金融的创新速度和效率。
--
-ShardingSphere 作为 Apache 基金会下的顶级开源项目，在 GitHub 上获得了超 14K Star
的关注，已成为行业内受欢迎的开源项目，全球有超过 170 家企业用户登记使用，覆盖金融、电子商务、云服务、旅游、物流、教育、文娱等多个领域。
+- ShardingSphere 作为 Apache 基金会下的顶级开源项目，在 GitHub 上获得了超 14K Star
的关注，已成为行业内受欢迎的开源项目，全球有超过 170 家企业用户登记使用，覆盖金融、电子商务、云服务、旅游、物流、教育、文娱等多个领域。
* 欢迎更多技术团队约稿投稿，和大家分享使用 ShardingSphere
的经验思考。如需转载请后台私信留言，对案例感兴趣的伙伴可联系社区经理（**ss_assistant_1**）回复“**加群**”进入技术交流群，我们也会不定期为社区发展做贡献的热心伙伴送上精美周边噢。
diff --git a/docs/blog/content/material/Open_source_community.cn.md
b/docs/blog/content/material/Open_source_community.cn.md
index 144d8e25265..7d6ef2491f1 100644
--- a/docs/blog/content/material/Open_source_community.cn.md
+++ b/docs/blog/content/material/Open_source_community.cn.md
@@ -68,3 +68,7 @@ chapter = true
**ShardingSphere GitHub 地址：** <https://github.com/apache/shardingsphere>
+**ShardingSphere Twitter 链接：** <https://twitter.com/ShardingSphere>
+
+**ShardingSphere Slack Channel 链接：** <https://bit.ly/3qB2GGc>
+
diff --git a/docs/blog/content/material/alpha.cn.md
b/docs/blog/content/material/alpha.cn.md
index a12371c62ac..a9017701ae5 100644
--- a/docs/blog/content/material/alpha.cn.md
+++ b/docs/blog/content/material/alpha.cn.md
@@ -11,7 +11,7 @@ ElasticJob（
https://github.com/apache/shardingsphere-elasticjob ）是面向
ElasticJob 在技术选型时，选择站在了巨人的肩膀上而不是重复制造轮子的理念，将定时任务事实标准的 QuartZ 与 分布式协调的利器
ZooKeeper 完美结合，快速而稳定的搭建了全新概念的分布式调度框架。
-### ElasticJob调度模型
+### ElasticJob 调度模型
ElasticJob 的调度模型划分为支持线程级别调度的进程内调度 ElasticJob-Lite，和进程级别调度的 ElasticJob-Cloud。
**进程内调度**
@@ -100,7 +100,7 @@ ElasticJob 中任务分片项的概念，使得任务可以在分布式的环境
5. 全新的控制台界面
-### 3.x版本设计解读
+### 3.x 版本设计解读
通过 Release Notes 能够看出，ElasticJob 3.x 并非 2.x 的修补版本，而是通过革新的设计理念践行的一套新产品。
diff --git a/docs/blog/content/material/community.cn.md
b/docs/blog/content/material/community.cn.md
index 3895015482a..853887a1a52 100644
--- a/docs/blog/content/material/community.cn.md
+++ b/docs/blog/content/material/community.cn.md
@@ -5,7 +5,7 @@ chapter = true
+++
-Apache ShardingSphere 社区受邀参与了11月9日在清华大学举办的《 Apache Event——走进 Apache
开源软件社区》的分享活动。在活动中 Apache ShardingSphere 社区的PPMC张亮分享了《 Apache ShardingSphere
社区的探索与拓展》这个话题，下面呈现分享的主要内容。
+Apache ShardingSphere 社区受邀参与了11月9日在清华大学举办的《 Apache Event——走进 Apache
开源软件社区》的分享活动。在活动中 Apache ShardingSphere 社区的 PPMC 张亮分享了《 Apache ShardingSphere
社区的探索与拓展》这个话题，下面呈现分享的主要内容。
### 01 为什么要做开源 ###
@@ -31,7 +31,7 @@ Apache ShardingSphere 社区受邀参与了11月9日在清华大学举办的《
### 02 Apache 软件基金会项目简介 ###
-Apache 软件基金会是一个非盈利组织。从1999年至今的20年时间里，产出了无数影响软件行业的项目。在几百个 Apache
软件基金会项目中，我们可以浏览一下几个非常著名的项目：Apache Tomcat、Apache Commons、Apache Maven、Apache
Hadoop、Apache Kafka、Apache Spark、Apache Zookeeper 等等。Apache
软件基金会的项目成为了开发者日常工作的基石。毫不夸张的说，如果以上项目，您一个都没听说过的话，那么可能很难拿到任何一家公司的 Java 后端或大数据类
Offer 。
+Apache 软件基金会是一个非盈利组织。从 1999 年至今的 20 年时间里，产出了无数影响软件行业的项目。在几百个 Apache
软件基金会项目中，我们可以浏览一下几个非常著名的项目：Apache Tomcat、Apache Commons、Apache Maven、Apache
Hadoop、Apache Kafka、Apache Spark、Apache Zookeeper 等等。Apache
软件基金会的项目成为了开发者日常工作的基石。毫不夸张的说，如果以上项目，您一个都没听说过的话，那么可能很难拿到任何一家公司的 Java 后端或大数据类
Offer 。
近年来，来自中国的 Apache 项目也越来越多了，截止到目前为止，已经有 19 个来自中国的项目进入了 Apache 软件基金会，其中有 9
个项目已经毕业成为顶级项目，还有 10 个项目正在孵化中。对于没有在西方社会工作过的人来说，参与一个国际化的开源项目的门槛有点高，因此，来自中国的
Apache
软件基金会项目对于想参与开源的国内同学是一个巨大的福音。这些项目能够提供一个有效的缓冲带，让一些初入社区且找不到门路的同学能够以熟悉的母语快速的进入国际化的开源社区。来自中国的
Apache 软件基金会项目，与来自西方的 Apache
软件基金会项目在流程、规范、法务等方面并无不同，唯一的区别是能在社区中找到可以说汉语的人，拉进沟通交流的举例，并进一步的了解 Apache
社区的运作模式，为以后参与其他国际化项目打好基础。
@@ -48,7 +48,7 @@ Apache ShardingSphere 开源将近4年了，它的外部使用相当广泛，目
\-1- 邮件列表数据变化
-这里只统计 [email protected] 邮箱，dev邮箱是社区交流问题的主要途径。2019 年 5 月有邮件 53
封；个；参与人数 14 人。而且这些数据的统计是包含了 GitBox 从 GitHub 转发的 15 封邮件，那么实际的邮件数量是38
封。在2019年9月的统计数据则有了明显的提升，其中邮件 148 封；主题 34 个，参与人 37 人，并且我们已经将 GitBox 转发的邮件从 dev
邮件组摘除，而是转移到了[email protected] 邮箱。
+这里只统计 [email protected] 邮箱，dev邮箱是社区交流问题的主要途径。2019 年 5 月有邮件 53
封；个；参与人数 14 人。而且这些数据的统计是包含了 GitBox 从 GitHub 转发的 15 封邮件，那么实际的邮件数量是 38
封。在2019年9月的统计数据则有了明显的提升，其中邮件 148 封；主题 34 个，参与人 37 人，并且我们已经将 GitBox 转发的邮件从 dev
邮件组摘除，而是转移到了[email protected] 邮箱。
\-2- GitHub 数据变化
@@ -56,7 +56,7 @@ Apache ShardingSphere 开源将近4年了，它的外部使用相当广泛，目
\-3- 社区数据变化
-在进入 Apache 孵化器时，ShardingSphere
的项目管理委员会成员一共有11人，除了项目管理委员会成员，社区中并未有官方提交者。经过了一年的进展，目前项目管理委员会成员增加了 2 人，达到了 13
人；并且新提升了7个官方提交者。一年来，参与项目的贡献者也从 37 人增长到了 88 人。参与的人数还在不断的增长中，未来 ShardingSphere
社区会从这些贡献者中提升更多的官方提交者，也会从官方提交者中提升更多的项目管理委员会成员。
+在进入 Apache 孵化器时，ShardingSphere 的项目管理委员会成员一共有 11
人，除了项目管理委员会成员，社区中并未有官方提交者。经过了一年的进展，目前项目管理委员会成员增加了 2 人，达到了 13 人；并且新提升了 7
个官方提交者。一年来，参与项目的贡献者也从 37 人增长到了 88 人。参与的人数还在不断的增长中，未来 ShardingSphere
社区会从这些贡献者中提升更多的官方提交者，也会从官方提交者中提升更多的项目管理委员会成员。
### 05 Apache ShardingSphere 社区的核心思路 ###
@@ -64,13 +64,13 @@ Apache ShardingSphere 开源将近4年了，它的外部使用相当广泛，目
2\.
尊重和相信合作者。我们相信，主动参与开源社区的人，是因为他愿意去做，并且愿意去做好的，是有充分热情的。所以我们会尊重每一个合作者，珍惜每个合作者的贡献。同时，我们也相信每一个合作者，并授予他们最大的权限。这里需要特别说明一下，合作者和初级贡献者是不同的，合作者需要通过较为长期参与来获得其他合作者的认同。识别值得依赖的合作者，是开源社区的重要工作之一。
-3\.
自动化测试。随着项目的贡献者越来越多，代码提交也会越来越频繁，靠人力去把控最终质量则会愈加不确定。出错与否不一定取决于个人意志，ShardingSphere社区更加看重能通过自动化的方式降低出错的概率。自动化测试框架能够保证贡献者不在提心吊胆的情况下提交代码，只要自动化测试是正确的，那么代码的正确性就可以保证。自动化测试可以让参与者更加愉悦的享受代码贡献的过程。
+3\.
自动化测试。随着项目的贡献者越来越多，代码提交也会越来越频繁，靠人力去把控最终质量则会愈加不确定。出错与否不一定取决于个人意志，ShardingSphere
社区更加看重能通过自动化的方式降低出错的概率。自动化测试框架能够保证贡献者不在提心吊胆的情况下提交代码，只要自动化测试是正确的，那么代码的正确性就可以保证。自动化测试可以让参与者更加愉悦的享受代码贡献的过程。
-4\.
创建自助渠道。随着项目被越来越多的用户所使用，各种问题也会层出不穷，即有可能是项目的bug，也有可能是用户自身的问题，还有可能是文档不清晰导致。因此，创建一个可以用用户自助的渠道就尤为重要。通过文档和FAQ，让用户能够以自助的方式解决大部分问题。在出现无法解决的问题时，通过邮件、GitHub、甚至微信群都可以找到社区的核心开发者，进一步的沟通和交流问题。
+4\. 创建自助渠道。随着项目被越来越多的用户所使用，各种问题也会层出不穷，即有可能是项目的
bug，也有可能是用户自身的问题，还有可能是文档不清晰导致。因此，创建一个可以用用户自助的渠道就尤为重要。通过文档和 FAQ
，让用户能够以自助的方式解决大部分问题。在出现无法解决的问题时，通过邮件、GitHub、甚至微信群都可以找到社区的核心开发者，进一步的沟通和交流问题。
-5\.
公开和远程的工作模式。只有在邮件列表或GitHub进行公开讨论问题，才会被视为已经发生的问题。社区不会处理私下的沟通和承诺，社区希望所有的问题和决议都是公开可查的。远程协作则表示合作者没有必要在地理上集中在一起，这就意味着工作是异步的。非交互式沟通，则进一步要求信息来往要交代清楚上下文，并尽可能多的通过一次信息描述更多的问题，从而进一步的促进沟通者的思考。
+5\. 公开和远程的工作模式。只有在邮件列表或 GitHub
进行公开讨论问题，才会被视为已经发生的问题。社区不会处理私下的沟通和承诺，社区希望所有的问题和决议都是公开可查的。远程协作则表示合作者没有必要在地理上集中在一起，这就意味着工作是异步的。非交互式沟通，则进一步要求信息来往要交代清楚上下文，并尽可能多的通过一次信息描述更多的问题，从而进一步的促进沟通者的思考。
-Apache 软件基金会提供了一个社区成熟度的评估模型，从代码、著作权、发布、质量、社区、一致决议、产品独立性这7个方面对社区的成熟度进行评估。目前
Apache ShardingSphere 已经完成了评估，已经通过了其全部34个子项目的评估。
+Apache 软件基金会提供了一个社区成熟度的评估模型，从代码、著作权、发布、质量、社区、一致决议、产品独立性这 7 个方面对社区的成熟度进行评估。目前
Apache ShardingSphere 已经完成了评估，已经通过了其全部 34 个子项目的评估。
### 06 提升 Apache ShardingSphere 社区的活跃度 ###
