You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@linkis.apache.org by ca...@apache.org on 2022/10/27 06:24:58 UTC
[incubator-linkis-website] branch dev updated: update docs (#557)
This is an automated email from the ASF dual-hosted git repository.
casion pushed a commit to branch dev
in repository https://gitbox.apache.org/repos/asf/incubator-linkis-website.git
The following commit(s) were added to refs/heads/dev by this push:
new 9f236acb7a update docs (#557)
9f236acb7a is described below
commit 9f236acb7a9bc9884a6174043d59742e120aa739
Author: Casion <ca...@gmail.com>
AuthorDate: Thu Oct 27 14:24:52 2022 +0800
update docs (#557)
---
community/how-to-ask-for-help.md | 6 +-
community/how-to-verify.md | 2 +-
doap.rdf | 4 +-
docs/deployment/cluster-deployment.md | 3 -
docs/deployment/deploy-linkis-without-hdfs.md | 2 +-
docs/deployment/engine-conn-plugin-installation.md | 9 +-
.../installation-hierarchical-structure.md | 8 +-
docs/deployment/involve-knife4j-into-linkis.md | 2 +-
docs/deployment/involve-prometheus-into-linkis.md | 2 +-
docs/deployment/involve-skywalking-into-linkis.md | 4 +-
docs/deployment/linkis-scriptis-install.md | 4 +-
.../sourcecode-hierarchical-structure.md | 2 +-
docs/deployment/start-metadatasource.md | 2 +-
docs/deployment/unpack-hierarchical-structure.md | 4 +-
docs/deployment/web-install.md | 4 +-
.../current/apache-product-name-usage-guide.md | 2 +-
.../current/how-to-ask-for-help.md | 2 +-
.../current/how-to-subscribe.md | 2 +-
.../current/how-to-verify.md | 2 +-
.../current/security.md | 2 +-
.../current/maturity.md | 254 ++++++++++-----------
maturity.md | 254 ++++++++++-----------
src/pages/home/config.json | 4 +-
23 files changed, 284 insertions(+), 296 deletions(-)
diff --git a/community/how-to-ask-for-help.md b/community/how-to-ask-for-help.md
index 60020e7f60..36cb1d3b0f 100644
--- a/community/how-to-ask-for-help.md
+++ b/community/how-to-ask-for-help.md
@@ -1,10 +1,6 @@
---
title: How to Ask for Help
-sidebar_position: 2.1
----
----
-title: need help
-sidebar_position: 2.1
+sidebar_position: 0.1
---
>This article mainly guides you on how to ask for help from the community. If you have any questions or doubts about the use of the software, you can seek help from the community through the following guidelines.
diff --git a/community/how-to-verify.md b/community/how-to-verify.md
index 008dbf3b38..dca114b64a 100644
--- a/community/how-to-verify.md
+++ b/community/how-to-verify.md
@@ -1,5 +1,5 @@
---
-title: How to Verify
+title: How to Verify Release
sidebar_position: 4
---
diff --git a/doap.rdf b/doap.rdf
index f6fced8ae3..b100a24d92 100644
--- a/doap.rdf
+++ b/doap.rdf
@@ -28,13 +28,13 @@
<homepage rdf:resource="http://linkis.apache.org/" />
<asfext:pmc rdf:resource="http://incubator.apache.org" />
<shortdesc>Apache Linkis builds a layer of computation middleware between upper applications and underlying engines.</shortdesc>
- <description>Apache Linkis is a computation middleware project, which decouples the upper applications and the underlying data engines, provides standardized interfaces (REST, JDBC, WebSocket etc.) to easily connect to various underlying engines (Spark, Presto, Flink, etc.).</description>
+ <description>Apache Linkis is a computation middleware project, which decouples the upper applications and the underlying data engines, provides standardized interfaces (REST, JDBC etc.) to easily connect to various underlying engines (Spark, Presto, Flink, etc.).</description>
<bug-database rdf:resource="https://github.com/apache/incubator-linkis/issues" />
<mailing-list rdf:resource="https://linkis.apache.org/community/how-to-subscribe" />
<download-page rdf:resource="https://linkis.apache.org/download/main" />
<repository>
<GitRepository>
- <location rdf:resource="https://github.com/apache/incubator-linkis.git"/>
+ <location rdf:resource="https://github.com/apache/incubator-linkis"/>
<browse rdf:resource="https://github.com/apache/incubator-linkis"/>
</GitRepository>
</repository>
diff --git a/docs/deployment/cluster-deployment.md b/docs/deployment/cluster-deployment.md
index 4f17b282a0..2438437dc1 100644
--- a/docs/deployment/cluster-deployment.md
+++ b/docs/deployment/cluster-deployment.md
@@ -3,9 +3,6 @@ title: Cluster Deployment
sidebar_position: 2
---
-Introduction to Distributed Deployment Scheme
-==================
-
Linkis's stand-alone deployment is simple, but it cannot be used in a production environment, because too many processes on the same server will make the server too stressful. The choice of deployment plan is related to the company's user scale, user habits, and the number of simultaneous users of the cluster. Generally speaking, we will choose the deployment method based on the number of simultaneous users using Linkis and the user's preference for the execution engine.
1.Multi-node deployment method reference
diff --git a/docs/deployment/deploy-linkis-without-hdfs.md b/docs/deployment/deploy-linkis-without-hdfs.md
index 46bc972830..0482921a5e 100644
--- a/docs/deployment/deploy-linkis-without-hdfs.md
+++ b/docs/deployment/deploy-linkis-without-hdfs.md
@@ -1,5 +1,5 @@
---
-title: Deploy Linkis without HDFS
+title: Deploy without HDFS
sidebar_position: 8
---
diff --git a/docs/deployment/engine-conn-plugin-installation.md b/docs/deployment/engine-conn-plugin-installation.md
index 94e6e71357..6f483bdd13 100644
--- a/docs/deployment/engine-conn-plugin-installation.md
+++ b/docs/deployment/engine-conn-plugin-installation.md
@@ -1,12 +1,9 @@
---
-title: EngineConnPlugin Installation
-sidebar_position: 3
+title: Installation EngineConn Plugin
+sidebar_position: 4
---
-EngineConnPlugin installation
-===============================
-
-This article mainly introduces the use of Linkis EngineConnPlugins, mainly from the aspects of compilation and installation.
+> This article mainly introduces the use of Linkis EngineConnPlugins, mainly from the aspects of compilation and installation.
## 1. Compilation and packaging of EngineConnPlugins
diff --git a/docs/deployment/installation-hierarchical-structure.md b/docs/deployment/installation-hierarchical-structure.md
index 83e726d5aa..5a2a763e17 100644
--- a/docs/deployment/installation-hierarchical-structure.md
+++ b/docs/deployment/installation-hierarchical-structure.md
@@ -1,11 +1,9 @@
---
-title: Installation Directory Structure
-sidebar_position: 4
+title: After Installation Directory Structure
+sidebar_position: 6.2
---
-Installation directory structure
-============
-The directory structure of Linkis 1.0 is very different from the 0.X version. Each microservice in 0.X has a root directory that exists independently. The main advantage of this directory structure is that it is easy to distinguish microservices and facilitate individual Microservices are managed, but there are some obvious problems:
+> The directory structure of Linkis 1.0 is very different from the 0.X version. Each microservice in 0.X has a root directory that exists independently. The main advantage of this directory structure is that it is easy to distinguish microservices and facilitate individual Microservices are managed, but there are some obvious problems:
1. The microservice catalog is too complicated and it is not convenient to switch catalog management
2. There is no unified startup script, which makes it more troublesome to start and stop microservices
diff --git a/docs/deployment/involve-knife4j-into-linkis.md b/docs/deployment/involve-knife4j-into-linkis.md
index badddfe774..c77b32705d 100644
--- a/docs/deployment/involve-knife4j-into-linkis.md
+++ b/docs/deployment/involve-knife4j-into-linkis.md
@@ -1,5 +1,5 @@
---
-title: Involve Knife4j into Linkis
+title: Involve Knife4j
sidebar_position: 12
---
diff --git a/docs/deployment/involve-prometheus-into-linkis.md b/docs/deployment/involve-prometheus-into-linkis.md
index af516b675a..be2a1c1f2d 100644
--- a/docs/deployment/involve-prometheus-into-linkis.md
+++ b/docs/deployment/involve-prometheus-into-linkis.md
@@ -1,5 +1,5 @@
---
-title: Involve Prometheus into Linkis
+title: Involve Prometheus
sidebar_position: 11
---
This article describes how to enable Prometheus to monitor all running Linkis services.
diff --git a/docs/deployment/involve-skywalking-into-linkis.md b/docs/deployment/involve-skywalking-into-linkis.md
index f8abbfbbb6..813ad893a3 100644
--- a/docs/deployment/involve-skywalking-into-linkis.md
+++ b/docs/deployment/involve-skywalking-into-linkis.md
@@ -1,6 +1,6 @@
---
-title: Involve SkyWaling into Linkis
-sidebar_position: 7
+title: Involve SkyWaling
+sidebar_position: 10
---
This article describes how to enable SkyWalking when starting the Linkis service to facilitate subsequent distributed trace and troubleshooting.
diff --git a/docs/deployment/linkis-scriptis-install.md b/docs/deployment/linkis-scriptis-install.md
index d27647808e..52f4fc587a 100644
--- a/docs/deployment/linkis-scriptis-install.md
+++ b/docs/deployment/linkis-scriptis-install.md
@@ -1,6 +1,6 @@
---
-title: Installation and deployment of the tool scriptis
-sidebar_position: 10
+title: Installation Scriptis Tool
+sidebar_position: 4.1
---
## 1 Introduction
diff --git a/docs/deployment/sourcecode-hierarchical-structure.md b/docs/deployment/sourcecode-hierarchical-structure.md
index ae0941d77c..437f3872bd 100644
--- a/docs/deployment/sourcecode-hierarchical-structure.md
+++ b/docs/deployment/sourcecode-hierarchical-structure.md
@@ -1,6 +1,6 @@
---
title: Source Code Directory Structure
-sidebar_position: 5
+sidebar_position: 6
---
# Source Code Directory Structure
diff --git a/docs/deployment/start-metadatasource.md b/docs/deployment/start-metadatasource.md
index 6e81fa3b26..9fbd72ee36 100644
--- a/docs/deployment/start-metadatasource.md
+++ b/docs/deployment/start-metadatasource.md
@@ -1,5 +1,5 @@
---
-title: DataSource
+title: Data Source Usage
sidebar_position: 7
---
diff --git a/docs/deployment/unpack-hierarchical-structure.md b/docs/deployment/unpack-hierarchical-structure.md
index 2745303c81..41bd242279 100644
--- a/docs/deployment/unpack-hierarchical-structure.md
+++ b/docs/deployment/unpack-hierarchical-structure.md
@@ -1,6 +1,6 @@
---
-title: installation package directory structure
-sidebar_position: 4.5
+title: Installation Package Directory Structure
+sidebar_position: 6.1
---
## Linkis installation package decompressed directory structure
diff --git a/docs/deployment/web-install.md b/docs/deployment/web-install.md
index f2b452fac0..2c2ff0b529 100644
--- a/docs/deployment/web-install.md
+++ b/docs/deployment/web-install.md
@@ -1,6 +1,6 @@
---
-title: Linkis Console Deployment
-sidebar_position: 6
+title: Console Deployment
+sidebar_position: 3
---
```
The linkis web service uses nginx as a static resource server. The access request process is as follows :
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/apache-product-name-usage-guide.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/apache-product-name-usage-guide.md
index a3b3d30fda..7bcc699ee1 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/apache-product-name-usage-guide.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/apache-product-name-usage-guide.md
@@ -1,5 +1,5 @@
---
-title: APACHE 产品名称使用指南
+title: Apache 产品名称使用指南
sidebar_position: 12
---
> 详细完整说明见 https://www.apache.org/foundation/marks/guide
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-ask-for-help.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-ask-for-help.md
index 4bc94888c2..010c9ddf79 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-ask-for-help.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-ask-for-help.md
@@ -1,6 +1,6 @@
---
title: 需求帮助
-sidebar_position: 2.1
+sidebar_position: 0.1
---
>本文主要指导大家如何需求社区的帮助，任何关于软件使用的问题或则疑惑，都可以通过以下指引来寻求社区同学的帮助。
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md
index de29150bbe..8edef620a9 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-subscribe.md
@@ -1,5 +1,5 @@
---
-title: 订阅邮件列表
+title: 如何订阅邮件列表
sidebar_position: 1
---
# 订阅邮件列表
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
index c68b5d6587..da9bc2b168 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-verify.md
@@ -1,5 +1,5 @@
---
-title: 发布版本验证
+title: 版本物料的验证
sidebar_position: 4
---
# 验证候选版本
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md
index 50707682c7..2cb1cca119 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/security.md
@@ -1,5 +1,5 @@
---
-title: 安全
+title: 安全问题
sidebar_position: 5
---
diff --git a/maturity.md b/i18n/zh-CN/docusaurus-plugin-content-docs-download/current/maturity.md
similarity index 54%
copy from maturity.md
copy to i18n/zh-CN/docusaurus-plugin-content-docs-download/current/maturity.md
index 1da52bc76a..bf33fbf2d5 100644
--- a/maturity.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-download/current/maturity.md
@@ -1,8 +1,95 @@
-> 参考[Doris](https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris)
+# English
+# Maturity Self Assessment for Apache Linkis (incubating)
+
+The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.
+
+More details can be found [here](https://community.apache.org/apache-way/apache-project-maturity-model.html).
+
+## Status of this assessment
+
+Mentors and community members are encouraged to contribute to this page and comment on it, the following tables summarize our self-assessment against the **Apache Project Maturity Model**.
+
+- :white_check_mark: means that the related item is in good status.
+- :white_large_square: means that the related item need long-term attention.
+- :x: means that the related item need to be fixed ASAP.
+
+
+## Maturity model assessment
+
+**CODE**
+
+| **ID** | **Description** | **Status** |
+| -------- | ----- | ---------- |
+| **CD10** | The project produces Open Source software for distribution to the public, at no charge. | :white_check_mark: The project source code is licensed under the `Apache License 2.0`. |
+| **CD20** | Anyone can easily discover and access the project's code. | :white_check_mark: The [offical website](https://linkis.incubator.apache.org/) includes `Github` link which can access GitHub directly. |
+| **CD30** | Anyone using standard, widely-available tools, can build the code in a reproducible way. | :white_check_mark: Apache Linkis provide [how-to-build](https://linkis.apache.org/docs/latest/development/linkis-compile-and-package) document to tell user how to compile on bare metal. |
+| **CD40** | The full history of the project's code is available via a source code control system, in a way that allows anyone to recreate any released version. | :white_check_mark: It depends on git, and anyone can view the full history of the project via commit logs. |
+| **CD50** | The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the committer. When third parties contribute code, commit messages provide reliable information about the code provenance. | :white_check_mark: The project uses GitHub and managed by Apache Infra, it ensuring provenance of each line of code to a committer. |
+
+**Licenses and Copyright**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **LC10** | The Apache License, version 2.0, covers the released code. | :white_check_mark: The [LICENSE](https://github.com/apache/incubator-linkis/blob/master/LICENSE) is in GitHub repository. And all source files are with APLv2 header, check by `apache-rat:check`. |
+| **LC20** | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | :white_check_mark: All [dependencies](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE) has been checked and non of them create more restrictions than the Apache Lic [...]
+| **LC30** | The libraries mentioned in LC20 are available as Open Source software. | :white_check_mark: See [dependencies](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE). |
+| **LC40** | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they may commit and how they need to identify code that is not their own. | :white_check_mark: All committers have iCLAs. |
+| **LC50** | The project clearly defines and documents the copyright ownership of everything that the project produces. | :white_check_mark: And all source files are with APLv2 header, check by `apache-rat:check`. |
+
+**Releases**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **RE10** | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | :white_check_mark: Source release is distributed via [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis) and linked from [download page](https://linkis.incubator.apache.org/down [...]
+| **RE20** | The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation. | :white_check_mark: All releases have been voted at dev@linkis and general@incubator, and have at least 3 PPMC's/IPMC's votes. |
+| **RE30** | Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives. | :white_check_mark: All releases are signed, and the [KEYS](https://downloads.apache.org/incubator/linkis/KEYS) is available. |
+| **RE40** | The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee. | :white_check_mark: User can easily build binaries from source code. Convenience binaries are distributed alongside source code at the same time via <ul><li>[Maven Central Repository](https://mvnrepository.com/artifact/org.apache.linkis)</li><li>[dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/)</li></ul> |
+| **RE50** | The project documents a repeatable release process so that someone new to the project can independently generate the complete set of artifacts required for a release. | :white_check_mark: We can follow the [release guide](http://linkis.incubator.apache.org/community/release-process.html) to make new Apache Linkis release. And so far we had 7 different release managers. |
+
+**Quality**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **QU10** | The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated. | :white_check_mark: We encourage user to [report issues](https://github.com/apache/incubator-linkis/issues) |
+| **QU20** | The project puts a very high priority on producing secure software. | :white_check_mark: All safety issues will be resolved in priority. |
+| **QU30** | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | :white_check_mark: Website provides a [security page](http://linkis.incubator.apache.org/community/security) |
+| **QU40** | The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. | :white_check_mark: All releases are backwards compatibility. Apache Linkis provides [upgrade guide](https://linkis.apache.org/docs/latest/upgrade/upgrade-guide) docs |
+| **QU50** | The project strives to respond to documented bug reports in a timely manner. | :white_check_mark: The project has resolved 1200+ issues and 1700+ pull requests so far, with very prompt response. |
+
+**Community**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **CO10** | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | :white_check_mark: The [website](https://linkis.apache.org/) includes all information user need to run Apache Linkis. |
+| **CO20** | The community welcomes contributions from anyone who acts in good faith and in a respectful manner, and who adds value to the project. | :white_check_mark: Apache Linkis provides [code submission guide](http://linkis.incubator.apache.org/community/how-to-contribute) and welcome all good contributions. |
+| **CO30** | Contributions include source code, documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | :white_check_mark: All good contributions including code and non-code are welcomed. |
+| **CO40** | The community strives to be meritocratic and gives more rights and responsibilities to contributors who, over time, add value to the project. | :white_check_mark: The community has elected 4 new PPMC members and 12 new committers so far. |
+| **CO50** | The project documents how contributors can earn more rights such as commit access or decision power, and applies these principles consistently. | :white_check_mark: With the document [committer guide](http://linkis.incubator.apache.org/community/how-to-contribute). |
+| **CO60** | The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects. | :white_check_mark: All decisions are made after vote by community members. |
+| **CO70** | The project strives to answer user questions in a timely manner. | :white_check_mark: We use dev@linkis, [github issue](https://github.com/apache/incubator-linkis/issues) and [github discussion](https://github.com/apache/incubator-linkis/discussions) to do this in a timely manner. |
+
+**Consensus**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **CS10** | The project maintains a public list of its contributors who have decision power. The project's PMC (Project Management Committee) consists of those contributors. | :white_check_mark: See [members](http://linkis.incubator.apache.org/team) with all PPMC members and committers. |
+| **CS20** | Decisions require a consensus among PMC members and are documented on the project's main communications channel. The PMC takes community opinions into account, but the PMC has the final word. | :white_check_mark: All decisions are made by votes on dev@linkis, and with at least 3 PPMC's/IPMC's +1 binding |
+| **CS30** | The project uses documented voting rules to build consensus when discussion is not sufficient. | :white_check_mark: The project uses the standard ASF voting rules. |
+| **CS40** |In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30. | :white_check_mark: Apache Linkis community has not used the veto power yet except for code commits. |
+| **CS50** | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | :white_check_mark: All important discussions and conclusions are recorded in written form. |
+
+**Independence**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **IN10** | The project is independent from any corporate or organizational influence. | :white_check_mark: The PPMC members and committer of Apache Linkis are from 10+ companies, and majority of them are NOT From the company that donated this project. |
+| **IN20** | Contributors act as themselves, not as representatives of a corporation or organization. | :white_check_mark: The contributors act on their own initiative without representing a corporation or organization. |
+
+----------------
# 中文
-# Apache Linkis 的成熟度评估（孵化中）
+# Apache Linkis 的成熟度自我评估（孵化中）
这个成熟度模型的目标是描述 Apache 项目如何以简洁和高级的方式运行，并提供一个项目可以选择用来评估自己的基本框架。
@@ -10,51 +97,51 @@
## 本次评估的状态
-该评估仍在进行中。
-
-## 成熟度模型评估
+鼓励导师和社区成员对此页面做出贡献并发表评论，下表总结了我们对 **Apache 项目成熟度模型**的自我评估。
-下表根据【Apache成熟度模型】（https://community.apache.org/apache-way/apache-project-maturity-model.html）填写。欢迎导师和社区成员发表评论和修改。
+- :white_check_mark: 表示相关项目状态良好。
+- :white_large_square: 表示相关项目需要长期关注。
+- :x: 表示相关项目需要尽快修复。
**代码**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **CD10** |该项目免费生产开源软件以向公众分发。 | **YES** 项目源代码在 `Apache License 2.0` 下获得许可。 |
-| **CD20** |任何人都可以轻松发现和访问该项目的代码.. | **YES** [官方网站](https://linkis.incubator.apache.org/) 包含`Github`图标链接，可以直接访问GitHub。 |
-| **CD30** |任何使用标准的、广泛可用的工具的人都可以以可重现的方式构建代码。 | **YES** Apache Linkis 提供如何构建文档来告诉用户如何在裸机上编译。 |
-| **CD40** |项目代码的完整历史可通过源代码控制系统获得，任何人都可以重新创建任何已发布的版本。 | **YES** 它依赖于 git，任何人都可以通过提交日志查看项目的完整历史。 |
-| **CD50** |源代码控制系统基于提交者的强身份验证，以可靠的方式确定每一行代码的出处。当第三方贡献代码时，提交消息会提供有关代码来源的可靠信息。 | |
+| **CD10** |该项目免费生产开源软件以向公众分发。 | :white_check_mark: 项目源代码在 `Apache License 2.0` 下获得许可。 |
+| **CD20** |任何人都可以轻松发现和访问该项目的代码.. | :white_check_mark: [官方网站](https://linkis.incubator.apache.org/) 包含`Github`图标链接，可以直接访问GitHub。 |
+| **CD30** |任何使用标准的、广泛可用的工具的人都可以以可重现的方式构建代码。 | :white_check_mark: Apache Linkis 提供如何构建文档来告诉用户如何在裸机上编译。 |
+| **CD40** |项目代码的完整历史可通过源代码控制系统获得，任何人都可以重新创建任何已发布的版本。 | :white_check_mark: 它依赖于 git，任何人都可以通过提交日志查看项目的完整历史。 |
+| **CD50** |源代码控制系统基于提交者的强身份验证，以可靠的方式确定每一行代码的出处。当第三方贡献代码时，提交消息会提供有关代码来源的可靠信息。 | :white_check_mark: |
**许可和版权**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **LC10** | Apache 许可证 2.0 版涵盖了已发布的代码。 | **YES** [许可](https://github.com/apache/incubator-linkis/blob/master/LICENSE) 位于 GitHub 存储库中。并且所有源文件都带有 APLv2 头文件，请通过 `apache-rat:check` 检查。 |
-| **LC20** |作为项目代码的强制依赖项的库不会产生比 Apache 许可更严格的限制。 | **YES** |
-| **LC30** | LC20 中提到的库可作为开源软件使用。 | **YES** |
-| **LC40** |提交者受个人贡献者协议（“Apache iCLA”）的约束，该协议定义了他们可以提交的代码以及他们需要如何识别不合法的代码继承人。 | **YES**所有提交者都有 iCLA。 |
-| **LC50** |该项目清楚地定义并记录了项目产生的所有内容的版权所有权。 | **YES** 所有源文件都带有 APLv2 标头，请通过 ``apache-rat:check` ` 检查。 与LC10的差异??? |
+| **LC10** | Apache 许可证 2.0 版涵盖了已发布的代码。 | :white_check_mark: [许可](https://github.com/apache/incubator-linkis/blob/master/LICENSE) 位于 GitHub 存储库中。并且所有源文件都带有 APLv2 头文件，请通过 `apache-rat:check` 检查。 |
+| **LC20** | 作为项目代码的强制依赖项的库不会产生比 Apache 许可证更多的限制。 | :white_check_mark: 所有 [依赖项](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE) 都已检查，并且没有一个比 Apache 许可证产生更多限制 做。 |
+| **LC30** | LC20 中提到的库可作为开源软件使用。 | :white_check_mark: 请参阅 [依赖项](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE)。 |
+| **LC40** |提交者受个人贡献者协议（“Apache iCLA”）的约束，该协议定义了他们可以提交的代码以及他们需要如何识别不合法的代码继承人。 | :white_check_mark: 所有提交者都有 iCLA。 |
+| **LC50** |该项目清楚地定义并记录了项目产生的所有内容的版权所有权。 | :white_check_mark: 所有源文件都带有 APLv2 标头，请通过 `apache-rat:check` 检查。 |
**发布**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **RE10** |版本由源代码组成，使用标准和开放的存档格式分发，预计将长期保持可读性。 | **YES** 源版本通过 [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/) 分发，并从 [下载页面](http://linkis.incubator.apache.org/download/main)。 |
-| **RE20** |项目的 PMC（项目管理委员会，参见 CS10）批准每个软件发布，以使发布成为基金会的行为。 | **YES**所有版本均已在 dev@linkis 和 general@incubator 投票，并且至少有 3 个 PPMC 投票。 |
-| **RE30** |版本与摘要一起签名和/或分发，任何人都可以可靠地使用它来验证下载的档案。 | **YES**所有版本都已签名，并且 [KEYS](https://dist.apache.org/repos/dist/release/incubator/linkis/KEYS) 可用。 |
-| **RE40** |该项目可以与源代码一起分发便利二进制文件，但它们不是 Apache 版本，它们不提供任何保证。 | **YES** 用户可以轻松地从源代码构建二进制文件。而且我们不提供二进制文件作为 Apache 版本。 |
-| **RE50** |该项目记录了一个可重复的发布过程，以便项目的新手可以独立生成发布所需的完整工件集。 | **YES**我们可以按照 [发布指南](https://linkis.apache.org/community/how-to-release) 来制作新的 Apache Linkis 版本。到目前为止，我们有 5 个不同的发布经理。 |
+| **RE10** |版本由源代码组成，使用标准和开放的存档格式分发，预计将长期保持可读性。 | :white_check_mark: 源版本通过 [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/) 分发，并从 [下载页面](http://linkis.incubator.apache.org/download/main)。 |
+| **RE20** |项目的 PMC（项目管理委员会，参见 CS10）批准每个软件发布，以使发布成为基金会的行为。 | :white_check_mark: 所有版本均已在 dev@linkis 和 general@incubator 投票，并且至少有 3 个 PPMC/IPMC +1 binding 投票。 |
+| **RE30** |版本与摘要一起签名和/或分发，任何人都可以可靠地使用它来验证下载的档案。 | :white_check_mark: 所有版本都已签名，并且 [KEYS](https://downloads.apache.org/incubator/linkis/KEYS) 可用。 |
+| **RE40** |该项目可以与源代码一起分发便利二进制文件，但它们不是 Apache 版本，它们不提供任何保证。 | :white_check_mark: 用户可以轻松地从源代码构建二进制文件。而且我们不提供二进制文件作为 Apache 版本。 |
+| **RE50** |该项目记录了一个可重复的发布过程，以便项目的新手可以独立生成发布所需的完整工件集。 | :white_check_mark: 我们可以按照 [发布指南](https://linkis.apache.org/community/how-to-release) 来制作新的 Apache Linkis 版本。到目前为止，我们有 7 个不同的发布经理。 |
**质量**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **QU10** |该项目对其代码的质量是开放和诚实的。各种模块的各种质量和成熟度级别是自然的和可接受的，只要它们被清楚地传达。 | **YES** 我们鼓励用户[报告问题](http://linkis.incubator.apache.org/community/feedback.html) |
-| **QU20** |该项目高度重视生产安全软件。 | **YES** 所有安全问题将在 3 天内解决。 |
-| **QU30** |该项目提供了一个有据可查、安全且私密的渠道来报告安全问题，以及有记录的响应方式。 | **YES** 网站提供 [安全上报](https://linkis.incubator.apache.org/community/security) |
-| **QU40** |该项目高度重视向后兼容性，旨在记录任何不兼容的更改，并提供工具和文档来帮助用户过渡到新功能。 | **YES** 所有版本都向后兼容,并提供了[升级指引文档](https://linkis.incubator.apache.org/docs/latest/upgrade/upgrade_guide) |
-| **QU50** |该项目力求及时响应记录在案的错误报告。 | **是** 到目前为止，该项目已经解决了 1175 多个问题和 1150 多个拉取请求，并且响应非常迅速。 |
+| **QU10** |该项目对其代码的质量是开放和诚实的。各种模块的各种质量和成熟度级别是自然的和可接受的，只要它们被清楚地传达。 | :white_check_mark: 我们鼓励用户[报告问题](https://github.com/apache/incubator-linkis/issues) |
+| **QU20** |该项目高度重视生产安全软件。 | :white_check_mark: 所有安全问题将优先解决。 |
+| **QU30** |该项目提供了一个有据可查、安全且私密的渠道来报告安全问题，以及有记录的响应方式。 | :white_check_mark: 网站提供 [安全上报](https://linkis.incubator.apache.org/community/security) |
+| **QU40** |该项目高度重视向后兼容性，旨在记录任何不兼容的更改，并提供工具和文档来帮助用户过渡到新功能。 | :white_check_mark: 所有版本都向后兼容,并提供了[升级指引文档](http://linkis.incubator.apache.org/docs/latest/upgrade/upgrade-guide) |
+| **QU50** |该项目力求及时响应记录在案的错误报告。 | :white_check_mark: 到目前为止，该项目已经解决了 1200 多个问题和 1700 多个拉取请求，并且响应非常迅速。 |
@@ -62,115 +149,28 @@
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **CO10** |该项目有一个主页，其中指向了根据此成熟度模型进行操作所需的所有信息。 | **是** [网站](https://linkis.apache.org/) 包含用户运行 Apache Linkis 所需的所有信息。 |
-| **二氧化碳** |社区欢迎任何以诚信和尊重的方式行事并为项目增加价值的人的贡献。 | **YES** Apache Linkis 提供 [代码提交指南](http://linkis.incubator.apache.org/community/pull-request.html) 并欢迎所有好的贡献。 |
-| **CO30** |贡献包括源代码、文档、建设性的错误报告、建设性的讨论、营销以及通常为项目增加价值的任何东西。 | **是**欢迎所有好的贡献，包括代码和非代码。 |
-| **CO40** |社区努力做到任人唯贤，并为随着时间的推移为项目增加价值的贡献者赋予更多的权利和责任。 | **YES** 到目前为止，社区已经选出了 6 名新的提交者。 |
-| **CO50** |该项目记录了贡献者如何获得更多权利，例如提交访问权或决策权，并始终如一地应用这些原则。 | **YES** 附上文档 [committer guide](https://linkis.apache.org/community/how-to-contribute)。 |
-| **CO60** |社区的运作基于拥有决策权的成员（参见 CS10）的共识。 Apache 项目不欢迎独裁者，无论仁慈与否。 | |
-| **CO70** |该项目力求及时回答用户的问题。 | **YES** 我们使用 dev@linkis, [Github issue](https://github.com/apache/incubator-linkis/issues) 和 [Github Discussion](https://github.com/apache/incubator-linkis/discussions) 及时完成此操作。 |
+| **CO10** |该项目有一个主页，其中指向了根据此成熟度模型进行操作所需的所有信息。 | :white_check_mark: [网站](https://linkis.apache.org/) 包含用户运行 Apache Linkis 所需的所有信息。 |
+| **CO20** |社区欢迎任何以诚信和尊重的方式行事并为项目增加价值的人的贡献。 | :white_check_mark: Apache Linkis 提供 [代码提交指南](http://linkis.incubator.apache.org/community/pull-request.html) 并欢迎所有好的贡献。 |
+| **CO30** |贡献包括源代码、文档、建设性的错误报告、建设性的讨论、营销以及通常为项目增加价值的任何东西。 | :white_check_mark: 欢迎所有好的贡献，包括代码和非代码。 |
+| **CO40** |社区努力做到任人唯贤，并为随着时间的推移为项目增加价值的贡献者赋予更多的权利和责任。 | :white_check_mark: 到目前为止，社区已经选出了 12 名新的提交者。 |
+| **CO50** |该项目记录了贡献者如何获得更多权利，例如提交访问权或决策权，并始终如一地应用这些原则。 | :white_check_mark: 附上文档 [committer guide](https://linkis.apache.org/community/how-to-contribute)。 |
+| **CO60** |社区的运作基于拥有决策权的成员（参见 CS10）的共识。 Apache 项目不欢迎独裁者，无论仁慈与否。 | :white_check_mark: 所有决定都是在社区成员投票后做出的。 |
+| **CO70** |该项目力求及时回答用户的问题。 | :white_check_mark: 我们使用 dev@linkis, [Github issue](https://github.com/apache/incubator-linkis/issues) 和 [Github Discussion](https://github.com/apache/incubator-linkis/discussions) 及时完成此操作。 |
**共识**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **CS10** |该项目维护其具有决策权的贡献者的公开列表。项目的 PMC（项目管理委员会）由这些贡献者组成。 | **是** 请参阅所有 PPMC 成员和提交者的 [members](https://linkis.apache.org/team)。 |
-| **CS20** |决策需要 PMC 成员之间达成共识，并记录在项目的主要沟通渠道上。 PMC 会考虑社区意见，但 PMC 拥有最终决定权。 | |
-| **CS30** |当讨论不足时，该项目使用记录在案的投票规则来建立共识。 | **YES** 该项目使用标准的 ASF 投票规则。 |
-| **CS40** |在 Apache 项目中，否决仅对代码提交有效。根据 CS30 中定义的 Apache 投票规则，行使否决权的人必须通过技术解释来证明其合理性。 | **是** 除了代码提交之外，Apache Linkis 社区尚未使用否决权。 |
-| **CS50** |所有“重要”的讨论都是在项目的主要沟通渠道上以书面形式异步进行的。影响项目的线下、面对面或私人讨论也记录在该频道上。 | 所有重要的讨论和结论都以书面形式记录下来。 |
+| **CS10** |该项目维护其具有决策权的贡献者的公开列表。项目的 PMC（项目管理委员会）由这些贡献者组成。 | :white_check_mark: 请参阅所有 PPMC 成员和提交者的 [members](https://linkis.apache.org/team)。 |
+| **CS20** |决策需要 PMC 成员之间达成共识，并记录在项目的主要沟通渠道上。 PMC 会考虑社区意见，但 PMC 拥有最终决定权。 | :white_check_mark: 所有决定都是通过 dev@linkis 投票做出的，并且至少有 3 个 PPMC/IPMC 的 +1 绑定。 |
+| **CS30** |当讨论不足时，该项目使用记录在案的投票规则来建立共识。 | :white_check_mark: 该项目使用标准的 ASF 投票规则。 |
+| **CS40** |在 Apache 项目中，否决仅对代码提交有效。根据 CS30 中定义的 Apache 投票规则，行使否决权的人必须通过技术解释来证明其合理性。 | :white_check_mark: 除了代码提交之外，Apache Linkis 社区尚未使用否决权。 |
+| **CS50** |所有“重要”的讨论都是在项目的主要沟通渠道上以书面形式异步进行的。影响项目的线下、面对面或私人讨论也记录在该频道上。 | :white_check_mark: 所有重要的讨论和结论都以书面形式记录下来。 |
**独立**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **IN10** |该项目独立于任何公司或组织的影响。 | |
-| **IN20** |贡献者以他们自己的身份行事，而不是作为公司或组织的代表。 | |
-
-
-
-# English
-# Maturity Assessment for Apache Linkis (incubating)
-
-The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.
-
-More details can be found [here](https://community.apache.org/apache-way/apache-project-maturity-model.html).
-
-## Status of this assessment
-
-This assessment is still working in progress.
-
-## Maturity model assessment
-
-The following table is filled according to the [Apache Maturity Model](https://community.apache.org/apache-way/apache-project-maturity-model.html). Mentors and community members are welcome to comment and modify it.
-
-**CODE**
-
-| **ID** | **Description** | **Status** |
-| -------- | ----- | ---------- |
-| **CD10** | The project produces Open Source software for distribution to the public, at no charge. | **YES** The project source code is licensed under the `Apache License 2.0`. |
-| **CD20** | Anyone can easily discover and access the project's code.. | **YES** The [offical website](https://linkis.incubator.apache.org/) includes `Github` link which can access GitHub directly. |
-| **CD30** | Anyone using standard, widely-available tools, can build the code in a reproducible way. | **YES** Apache Linkis provide how-to-build document to tell user how to compile on bare metal. |
-| **CD40** | The full history of the project's code is available via a source code control system, in a way that allows anyone to recreate any released version. | **YES** It depends on git, and anyone can view the full history of the project via commit logs. |
-| **CD50** | The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the committer. When third parties contribute code, commit messages provide reliable information about the code provenance. | **YES** The project uses GitHub and managed by Apache Infra, it ensuring provenance of each line of code to a committer. And the third-party contributions are accepted in accordance with the [Code submission Guide](https:/ [...]
-
-**Licenses and Copyright**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **LC10** | The Apache License, version 2.0, covers the released code. | **YES** The [LICENSE](https://github.com/apache/incubator-linkis/blob/master/LICENSE.txt) is in GitHub repository. And all source files are with APLv2 header, check by `apache/skywalking-eyes@v0.2`. |
-| **LC20** | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | **YES** All [dependencies](https://github.com/apache/incubator-linkis/blob/master/thirdparty/vars.sh) has been checked and non of them create more restrictions than the Apache License does. |
-| **LC30** | The libraries mentioned in LC20 are available as Open Source software. | **YES** See [dependencies](https://github.com/apache/incubator-linkis/blob/master/thirdparty/vars.sh). |
-| **LC40** | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they may commit and how they need to identify code that is not their own. | **YES** All committers have iCLAs. |
-| **LC50** | The project clearly defines and documents the copyright ownership of everything that the project produces. | **YES** And all source files are with APLv2 header, check by `apache/skywalking-eyes@v0.2`. |
-
-**Releases**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **RE10** | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | **YES** Source release is distributed via [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/) and linked from [download page](http://linkis.incubator.apache.org/downloads/downlo [...]
-| **RE20** | The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation. | **YES** All releases have been voted at dev@linkis and general@incubator, and have at least 3 PPMC's votes. |
-| **RE30** | Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives. | **YES** All releases are signed, and the [KEYS](https://dist.apache.org/repos/dist/release/incubator/linkis/KEYS) is available. |
-| **RE40** | The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee. | **YES** User can easily build binaries from source code. And we don't provide binaries as Apache Releases. |
-| **RE50** | The project documents a repeatable release process so that someone new to the project can independently generate the complete set of artifacts required for a release. | **YES** We can follow the [Release guide](http://linkis.incubator.apache.org/community/release-process.html) to make new Apache Linkis release. And so far we had 6 different release managers. |
-
-**Quality**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **QU10** | The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated. | **YES** We encourage user to [report issues](http://linkis.incubator.apache.org/community/feedback.html) |
-| **QU20** | The project puts a very high priority on producing secure software. | **YES** All security issues will be addressed within 3 days. |
-| **QU30** | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | **YES** Website provides a [security page](http://linkis.incubator.apache.org/community/security.html) |
-| **QU40** | The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. | **YES** All releases are backwards compatibility. |
-| **QU50** | The project strives to respond to documented bug reports in a timely manner. | **YES** The project has resolved 2000+ issues and 4000+ pull requests so far, with very prompt response. |
-
-**Community**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **CO10** | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | **YES** The [website](https://linkis.apache.org/) includes all information user need to run Apache Linkis. |
-| **CO20** | The community welcomes contributions from anyone who acts in good faith and in a respectful manner, and who adds value to the project. | **YES** Apache Linkis provides [Code submission guide](http://linkis.incubator.apache.org/community/pull-request.html) and welcome all good contributions. |
-| **CO30** | Contributions include source code, documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | **YES** All good contributions including code and non-code are welcomed. |
-| **CO40** | The community strives to be meritocratic and gives more rights and responsibilities to contributors who, over time, add value to the project. | **YES** The community has elected 6 new PPMC members and 17 new committers so far. |
-| **CO50** | The project documents how contributors can earn more rights such as commit access or decision power, and applies these principles consistently. | **YES** With the document [committer guide](http://linkis.incubator.apache.org/community/committer-guide.html). |
-| **CO60** | The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects. | **YES** All decisions are made after vote by community members. |
-| **CO70** | The project strives to answer user questions in a timely manner. | **YES** We use dev@linkis, [Github issue](https://github.com/apache/incubator-linkis/issues) and [Github discussion](https://github.com/apache/incubator-linkis/discussions) to do this in a timely manner. |
-
-**Consensus**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **CS10** | The project maintains a public list of its contributors who have decision power. The project's PMC (Project Management Committee) consists of those contributors. | **YES** See [members](http://linkis.incubator.apache.org/community/members.html) with all PPMC members and committers. |
-| **CS20** | Decisions require a consensus among PMC members and are documented on the project's main communications channel. The PMC takes community opinions into account, but the PMC has the final word. | **YES** All decisions are made by votes on dev@linkis, and with at least 3 PPMC's +1 |
-| **CS30** | The project uses documented voting rules to build consensus when discussion is not sufficient. | **YES** The project uses the standard ASF voting rules. |
-| **CS40** |In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30. | **YES** Apache Linkis community has not used the veto power yet except for code commits. |
-| **CS50** | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | **YES** All important discussions and conclusions are recorded in written form. |
-
-**Independence**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **IN10** | The project is independent from any corporate or organizational influence. | **YES** The PPMC members and committer of Apache Linkis are from 6+ companies, and majority of them are NOT From the company that donated this project. |
-| **IN20** | Contributors act as themselves, not as representatives of a corporation or organization. | **YES** The contributors act on their own initiative without representing a corporation or organization. |
-
+|**IN10**|项目独立于任何公司或组织影响。|:white_check_mark: Apache Linkis的PPMC成员和提交人来自家 15 以上的公司|
+|**IN20**|贡献者以自己的身份行事，而不是作为公司或组织的代表。|:white_check_mark: 贡献者自行行动，不代表公司或组织|
diff --git a/maturity.md b/maturity.md
index 1da52bc76a..bf33fbf2d5 100644
--- a/maturity.md
+++ b/maturity.md
@@ -1,8 +1,95 @@
-> 参考[Doris](https://cwiki.apache.org/confluence/display/DORIS/Maturity+Assessment+for+Doris)
+# English
+# Maturity Self Assessment for Apache Linkis (incubating)
+
+The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.
+
+More details can be found [here](https://community.apache.org/apache-way/apache-project-maturity-model.html).
+
+## Status of this assessment
+
+Mentors and community members are encouraged to contribute to this page and comment on it, the following tables summarize our self-assessment against the **Apache Project Maturity Model**.
+
+- :white_check_mark: means that the related item is in good status.
+- :white_large_square: means that the related item need long-term attention.
+- :x: means that the related item need to be fixed ASAP.
+
+
+## Maturity model assessment
+
+**CODE**
+
+| **ID** | **Description** | **Status** |
+| -------- | ----- | ---------- |
+| **CD10** | The project produces Open Source software for distribution to the public, at no charge. | :white_check_mark: The project source code is licensed under the `Apache License 2.0`. |
+| **CD20** | Anyone can easily discover and access the project's code. | :white_check_mark: The [offical website](https://linkis.incubator.apache.org/) includes `Github` link which can access GitHub directly. |
+| **CD30** | Anyone using standard, widely-available tools, can build the code in a reproducible way. | :white_check_mark: Apache Linkis provide [how-to-build](https://linkis.apache.org/docs/latest/development/linkis-compile-and-package) document to tell user how to compile on bare metal. |
+| **CD40** | The full history of the project's code is available via a source code control system, in a way that allows anyone to recreate any released version. | :white_check_mark: It depends on git, and anyone can view the full history of the project via commit logs. |
+| **CD50** | The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the committer. When third parties contribute code, commit messages provide reliable information about the code provenance. | :white_check_mark: The project uses GitHub and managed by Apache Infra, it ensuring provenance of each line of code to a committer. |
+
+**Licenses and Copyright**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **LC10** | The Apache License, version 2.0, covers the released code. | :white_check_mark: The [LICENSE](https://github.com/apache/incubator-linkis/blob/master/LICENSE) is in GitHub repository. And all source files are with APLv2 header, check by `apache-rat:check`. |
+| **LC20** | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | :white_check_mark: All [dependencies](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE) has been checked and non of them create more restrictions than the Apache Lic [...]
+| **LC30** | The libraries mentioned in LC20 are available as Open Source software. | :white_check_mark: See [dependencies](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE). |
+| **LC40** | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they may commit and how they need to identify code that is not their own. | :white_check_mark: All committers have iCLAs. |
+| **LC50** | The project clearly defines and documents the copyright ownership of everything that the project produces. | :white_check_mark: And all source files are with APLv2 header, check by `apache-rat:check`. |
+
+**Releases**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **RE10** | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | :white_check_mark: Source release is distributed via [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis) and linked from [download page](https://linkis.incubator.apache.org/down [...]
+| **RE20** | The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation. | :white_check_mark: All releases have been voted at dev@linkis and general@incubator, and have at least 3 PPMC's/IPMC's votes. |
+| **RE30** | Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives. | :white_check_mark: All releases are signed, and the [KEYS](https://downloads.apache.org/incubator/linkis/KEYS) is available. |
+| **RE40** | The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee. | :white_check_mark: User can easily build binaries from source code. Convenience binaries are distributed alongside source code at the same time via <ul><li>[Maven Central Repository](https://mvnrepository.com/artifact/org.apache.linkis)</li><li>[dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/)</li></ul> |
+| **RE50** | The project documents a repeatable release process so that someone new to the project can independently generate the complete set of artifacts required for a release. | :white_check_mark: We can follow the [release guide](http://linkis.incubator.apache.org/community/release-process.html) to make new Apache Linkis release. And so far we had 7 different release managers. |
+
+**Quality**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **QU10** | The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated. | :white_check_mark: We encourage user to [report issues](https://github.com/apache/incubator-linkis/issues) |
+| **QU20** | The project puts a very high priority on producing secure software. | :white_check_mark: All safety issues will be resolved in priority. |
+| **QU30** | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | :white_check_mark: Website provides a [security page](http://linkis.incubator.apache.org/community/security) |
+| **QU40** | The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. | :white_check_mark: All releases are backwards compatibility. Apache Linkis provides [upgrade guide](https://linkis.apache.org/docs/latest/upgrade/upgrade-guide) docs |
+| **QU50** | The project strives to respond to documented bug reports in a timely manner. | :white_check_mark: The project has resolved 1200+ issues and 1700+ pull requests so far, with very prompt response. |
+
+**Community**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **CO10** | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | :white_check_mark: The [website](https://linkis.apache.org/) includes all information user need to run Apache Linkis. |
+| **CO20** | The community welcomes contributions from anyone who acts in good faith and in a respectful manner, and who adds value to the project. | :white_check_mark: Apache Linkis provides [code submission guide](http://linkis.incubator.apache.org/community/how-to-contribute) and welcome all good contributions. |
+| **CO30** | Contributions include source code, documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | :white_check_mark: All good contributions including code and non-code are welcomed. |
+| **CO40** | The community strives to be meritocratic and gives more rights and responsibilities to contributors who, over time, add value to the project. | :white_check_mark: The community has elected 4 new PPMC members and 12 new committers so far. |
+| **CO50** | The project documents how contributors can earn more rights such as commit access or decision power, and applies these principles consistently. | :white_check_mark: With the document [committer guide](http://linkis.incubator.apache.org/community/how-to-contribute). |
+| **CO60** | The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects. | :white_check_mark: All decisions are made after vote by community members. |
+| **CO70** | The project strives to answer user questions in a timely manner. | :white_check_mark: We use dev@linkis, [github issue](https://github.com/apache/incubator-linkis/issues) and [github discussion](https://github.com/apache/incubator-linkis/discussions) to do this in a timely manner. |
+
+**Consensus**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **CS10** | The project maintains a public list of its contributors who have decision power. The project's PMC (Project Management Committee) consists of those contributors. | :white_check_mark: See [members](http://linkis.incubator.apache.org/team) with all PPMC members and committers. |
+| **CS20** | Decisions require a consensus among PMC members and are documented on the project's main communications channel. The PMC takes community opinions into account, but the PMC has the final word. | :white_check_mark: All decisions are made by votes on dev@linkis, and with at least 3 PPMC's/IPMC's +1 binding |
+| **CS30** | The project uses documented voting rules to build consensus when discussion is not sufficient. | :white_check_mark: The project uses the standard ASF voting rules. |
+| **CS40** |In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30. | :white_check_mark: Apache Linkis community has not used the veto power yet except for code commits. |
+| **CS50** | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | :white_check_mark: All important discussions and conclusions are recorded in written form. |
+
+**Independence**
+
+| **ID** | **Description** | **Status** |
+| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
+| **IN10** | The project is independent from any corporate or organizational influence. | :white_check_mark: The PPMC members and committer of Apache Linkis are from 10+ companies, and majority of them are NOT From the company that donated this project. |
+| **IN20** | Contributors act as themselves, not as representatives of a corporation or organization. | :white_check_mark: The contributors act on their own initiative without representing a corporation or organization. |
+
+----------------
# 中文
-# Apache Linkis 的成熟度评估（孵化中）
+# Apache Linkis 的成熟度自我评估（孵化中）
这个成熟度模型的目标是描述 Apache 项目如何以简洁和高级的方式运行，并提供一个项目可以选择用来评估自己的基本框架。
@@ -10,51 +97,51 @@
## 本次评估的状态
-该评估仍在进行中。
-
-## 成熟度模型评估
+鼓励导师和社区成员对此页面做出贡献并发表评论，下表总结了我们对 **Apache 项目成熟度模型**的自我评估。
-下表根据【Apache成熟度模型】（https://community.apache.org/apache-way/apache-project-maturity-model.html）填写。欢迎导师和社区成员发表评论和修改。
+- :white_check_mark: 表示相关项目状态良好。
+- :white_large_square: 表示相关项目需要长期关注。
+- :x: 表示相关项目需要尽快修复。
**代码**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **CD10** |该项目免费生产开源软件以向公众分发。 | **YES** 项目源代码在 `Apache License 2.0` 下获得许可。 |
-| **CD20** |任何人都可以轻松发现和访问该项目的代码.. | **YES** [官方网站](https://linkis.incubator.apache.org/) 包含`Github`图标链接，可以直接访问GitHub。 |
-| **CD30** |任何使用标准的、广泛可用的工具的人都可以以可重现的方式构建代码。 | **YES** Apache Linkis 提供如何构建文档来告诉用户如何在裸机上编译。 |
-| **CD40** |项目代码的完整历史可通过源代码控制系统获得，任何人都可以重新创建任何已发布的版本。 | **YES** 它依赖于 git，任何人都可以通过提交日志查看项目的完整历史。 |
-| **CD50** |源代码控制系统基于提交者的强身份验证，以可靠的方式确定每一行代码的出处。当第三方贡献代码时，提交消息会提供有关代码来源的可靠信息。 | |
+| **CD10** |该项目免费生产开源软件以向公众分发。 | :white_check_mark: 项目源代码在 `Apache License 2.0` 下获得许可。 |
+| **CD20** |任何人都可以轻松发现和访问该项目的代码.. | :white_check_mark: [官方网站](https://linkis.incubator.apache.org/) 包含`Github`图标链接，可以直接访问GitHub。 |
+| **CD30** |任何使用标准的、广泛可用的工具的人都可以以可重现的方式构建代码。 | :white_check_mark: Apache Linkis 提供如何构建文档来告诉用户如何在裸机上编译。 |
+| **CD40** |项目代码的完整历史可通过源代码控制系统获得，任何人都可以重新创建任何已发布的版本。 | :white_check_mark: 它依赖于 git，任何人都可以通过提交日志查看项目的完整历史。 |
+| **CD50** |源代码控制系统基于提交者的强身份验证，以可靠的方式确定每一行代码的出处。当第三方贡献代码时，提交消息会提供有关代码来源的可靠信息。 | :white_check_mark: |
**许可和版权**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **LC10** | Apache 许可证 2.0 版涵盖了已发布的代码。 | **YES** [许可](https://github.com/apache/incubator-linkis/blob/master/LICENSE) 位于 GitHub 存储库中。并且所有源文件都带有 APLv2 头文件，请通过 `apache-rat:check` 检查。 |
-| **LC20** |作为项目代码的强制依赖项的库不会产生比 Apache 许可更严格的限制。 | **YES** |
-| **LC30** | LC20 中提到的库可作为开源软件使用。 | **YES** |
-| **LC40** |提交者受个人贡献者协议（“Apache iCLA”）的约束，该协议定义了他们可以提交的代码以及他们需要如何识别不合法的代码继承人。 | **YES**所有提交者都有 iCLA。 |
-| **LC50** |该项目清楚地定义并记录了项目产生的所有内容的版权所有权。 | **YES** 所有源文件都带有 APLv2 标头，请通过 ``apache-rat:check` ` 检查。 与LC10的差异??? |
+| **LC10** | Apache 许可证 2.0 版涵盖了已发布的代码。 | :white_check_mark: [许可](https://github.com/apache/incubator-linkis/blob/master/LICENSE) 位于 GitHub 存储库中。并且所有源文件都带有 APLv2 头文件，请通过 `apache-rat:check` 检查。 |
+| **LC20** | 作为项目代码的强制依赖项的库不会产生比 Apache 许可证更多的限制。 | :white_check_mark: 所有 [依赖项](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE) 都已检查，并且没有一个比 Apache 许可证产生更多限制 做。 |
+| **LC30** | LC20 中提到的库可作为开源软件使用。 | :white_check_mark: 请参阅 [依赖项](https://github.com/apache/incubator-linkis/blob/master/linkis-dist/release-docs/LICENSE)。 |
+| **LC40** |提交者受个人贡献者协议（“Apache iCLA”）的约束，该协议定义了他们可以提交的代码以及他们需要如何识别不合法的代码继承人。 | :white_check_mark: 所有提交者都有 iCLA。 |
+| **LC50** |该项目清楚地定义并记录了项目产生的所有内容的版权所有权。 | :white_check_mark: 所有源文件都带有 APLv2 标头，请通过 `apache-rat:check` 检查。 |
**发布**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **RE10** |版本由源代码组成，使用标准和开放的存档格式分发，预计将长期保持可读性。 | **YES** 源版本通过 [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/) 分发，并从 [下载页面](http://linkis.incubator.apache.org/download/main)。 |
-| **RE20** |项目的 PMC（项目管理委员会，参见 CS10）批准每个软件发布，以使发布成为基金会的行为。 | **YES**所有版本均已在 dev@linkis 和 general@incubator 投票，并且至少有 3 个 PPMC 投票。 |
-| **RE30** |版本与摘要一起签名和/或分发，任何人都可以可靠地使用它来验证下载的档案。 | **YES**所有版本都已签名，并且 [KEYS](https://dist.apache.org/repos/dist/release/incubator/linkis/KEYS) 可用。 |
-| **RE40** |该项目可以与源代码一起分发便利二进制文件，但它们不是 Apache 版本，它们不提供任何保证。 | **YES** 用户可以轻松地从源代码构建二进制文件。而且我们不提供二进制文件作为 Apache 版本。 |
-| **RE50** |该项目记录了一个可重复的发布过程，以便项目的新手可以独立生成发布所需的完整工件集。 | **YES**我们可以按照 [发布指南](https://linkis.apache.org/community/how-to-release) 来制作新的 Apache Linkis 版本。到目前为止，我们有 5 个不同的发布经理。 |
+| **RE10** |版本由源代码组成，使用标准和开放的存档格式分发，预计将长期保持可读性。 | :white_check_mark: 源版本通过 [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/) 分发，并从 [下载页面](http://linkis.incubator.apache.org/download/main)。 |
+| **RE20** |项目的 PMC（项目管理委员会，参见 CS10）批准每个软件发布，以使发布成为基金会的行为。 | :white_check_mark: 所有版本均已在 dev@linkis 和 general@incubator 投票，并且至少有 3 个 PPMC/IPMC +1 binding 投票。 |
+| **RE30** |版本与摘要一起签名和/或分发，任何人都可以可靠地使用它来验证下载的档案。 | :white_check_mark: 所有版本都已签名，并且 [KEYS](https://downloads.apache.org/incubator/linkis/KEYS) 可用。 |
+| **RE40** |该项目可以与源代码一起分发便利二进制文件，但它们不是 Apache 版本，它们不提供任何保证。 | :white_check_mark: 用户可以轻松地从源代码构建二进制文件。而且我们不提供二进制文件作为 Apache 版本。 |
+| **RE50** |该项目记录了一个可重复的发布过程，以便项目的新手可以独立生成发布所需的完整工件集。 | :white_check_mark: 我们可以按照 [发布指南](https://linkis.apache.org/community/how-to-release) 来制作新的 Apache Linkis 版本。到目前为止，我们有 7 个不同的发布经理。 |
**质量**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **QU10** |该项目对其代码的质量是开放和诚实的。各种模块的各种质量和成熟度级别是自然的和可接受的，只要它们被清楚地传达。 | **YES** 我们鼓励用户[报告问题](http://linkis.incubator.apache.org/community/feedback.html) |
-| **QU20** |该项目高度重视生产安全软件。 | **YES** 所有安全问题将在 3 天内解决。 |
-| **QU30** |该项目提供了一个有据可查、安全且私密的渠道来报告安全问题，以及有记录的响应方式。 | **YES** 网站提供 [安全上报](https://linkis.incubator.apache.org/community/security) |
-| **QU40** |该项目高度重视向后兼容性，旨在记录任何不兼容的更改，并提供工具和文档来帮助用户过渡到新功能。 | **YES** 所有版本都向后兼容,并提供了[升级指引文档](https://linkis.incubator.apache.org/docs/latest/upgrade/upgrade_guide) |
-| **QU50** |该项目力求及时响应记录在案的错误报告。 | **是** 到目前为止，该项目已经解决了 1175 多个问题和 1150 多个拉取请求，并且响应非常迅速。 |
+| **QU10** |该项目对其代码的质量是开放和诚实的。各种模块的各种质量和成熟度级别是自然的和可接受的，只要它们被清楚地传达。 | :white_check_mark: 我们鼓励用户[报告问题](https://github.com/apache/incubator-linkis/issues) |
+| **QU20** |该项目高度重视生产安全软件。 | :white_check_mark: 所有安全问题将优先解决。 |
+| **QU30** |该项目提供了一个有据可查、安全且私密的渠道来报告安全问题，以及有记录的响应方式。 | :white_check_mark: 网站提供 [安全上报](https://linkis.incubator.apache.org/community/security) |
+| **QU40** |该项目高度重视向后兼容性，旨在记录任何不兼容的更改，并提供工具和文档来帮助用户过渡到新功能。 | :white_check_mark: 所有版本都向后兼容,并提供了[升级指引文档](http://linkis.incubator.apache.org/docs/latest/upgrade/upgrade-guide) |
+| **QU50** |该项目力求及时响应记录在案的错误报告。 | :white_check_mark: 到目前为止，该项目已经解决了 1200 多个问题和 1700 多个拉取请求，并且响应非常迅速。 |
@@ -62,115 +149,28 @@
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **CO10** |该项目有一个主页，其中指向了根据此成熟度模型进行操作所需的所有信息。 | **是** [网站](https://linkis.apache.org/) 包含用户运行 Apache Linkis 所需的所有信息。 |
-| **二氧化碳** |社区欢迎任何以诚信和尊重的方式行事并为项目增加价值的人的贡献。 | **YES** Apache Linkis 提供 [代码提交指南](http://linkis.incubator.apache.org/community/pull-request.html) 并欢迎所有好的贡献。 |
-| **CO30** |贡献包括源代码、文档、建设性的错误报告、建设性的讨论、营销以及通常为项目增加价值的任何东西。 | **是**欢迎所有好的贡献，包括代码和非代码。 |
-| **CO40** |社区努力做到任人唯贤，并为随着时间的推移为项目增加价值的贡献者赋予更多的权利和责任。 | **YES** 到目前为止，社区已经选出了 6 名新的提交者。 |
-| **CO50** |该项目记录了贡献者如何获得更多权利，例如提交访问权或决策权，并始终如一地应用这些原则。 | **YES** 附上文档 [committer guide](https://linkis.apache.org/community/how-to-contribute)。 |
-| **CO60** |社区的运作基于拥有决策权的成员（参见 CS10）的共识。 Apache 项目不欢迎独裁者，无论仁慈与否。 | |
-| **CO70** |该项目力求及时回答用户的问题。 | **YES** 我们使用 dev@linkis, [Github issue](https://github.com/apache/incubator-linkis/issues) 和 [Github Discussion](https://github.com/apache/incubator-linkis/discussions) 及时完成此操作。 |
+| **CO10** |该项目有一个主页，其中指向了根据此成熟度模型进行操作所需的所有信息。 | :white_check_mark: [网站](https://linkis.apache.org/) 包含用户运行 Apache Linkis 所需的所有信息。 |
+| **CO20** |社区欢迎任何以诚信和尊重的方式行事并为项目增加价值的人的贡献。 | :white_check_mark: Apache Linkis 提供 [代码提交指南](http://linkis.incubator.apache.org/community/pull-request.html) 并欢迎所有好的贡献。 |
+| **CO30** |贡献包括源代码、文档、建设性的错误报告、建设性的讨论、营销以及通常为项目增加价值的任何东西。 | :white_check_mark: 欢迎所有好的贡献，包括代码和非代码。 |
+| **CO40** |社区努力做到任人唯贤，并为随着时间的推移为项目增加价值的贡献者赋予更多的权利和责任。 | :white_check_mark: 到目前为止，社区已经选出了 12 名新的提交者。 |
+| **CO50** |该项目记录了贡献者如何获得更多权利，例如提交访问权或决策权，并始终如一地应用这些原则。 | :white_check_mark: 附上文档 [committer guide](https://linkis.apache.org/community/how-to-contribute)。 |
+| **CO60** |社区的运作基于拥有决策权的成员（参见 CS10）的共识。 Apache 项目不欢迎独裁者，无论仁慈与否。 | :white_check_mark: 所有决定都是在社区成员投票后做出的。 |
+| **CO70** |该项目力求及时回答用户的问题。 | :white_check_mark: 我们使用 dev@linkis, [Github issue](https://github.com/apache/incubator-linkis/issues) 和 [Github Discussion](https://github.com/apache/incubator-linkis/discussions) 及时完成此操作。 |
**共识**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **CS10** |该项目维护其具有决策权的贡献者的公开列表。项目的 PMC（项目管理委员会）由这些贡献者组成。 | **是** 请参阅所有 PPMC 成员和提交者的 [members](https://linkis.apache.org/team)。 |
-| **CS20** |决策需要 PMC 成员之间达成共识，并记录在项目的主要沟通渠道上。 PMC 会考虑社区意见，但 PMC 拥有最终决定权。 | |
-| **CS30** |当讨论不足时，该项目使用记录在案的投票规则来建立共识。 | **YES** 该项目使用标准的 ASF 投票规则。 |
-| **CS40** |在 Apache 项目中，否决仅对代码提交有效。根据 CS30 中定义的 Apache 投票规则，行使否决权的人必须通过技术解释来证明其合理性。 | **是** 除了代码提交之外，Apache Linkis 社区尚未使用否决权。 |
-| **CS50** |所有“重要”的讨论都是在项目的主要沟通渠道上以书面形式异步进行的。影响项目的线下、面对面或私人讨论也记录在该频道上。 | 所有重要的讨论和结论都以书面形式记录下来。 |
+| **CS10** |该项目维护其具有决策权的贡献者的公开列表。项目的 PMC（项目管理委员会）由这些贡献者组成。 | :white_check_mark: 请参阅所有 PPMC 成员和提交者的 [members](https://linkis.apache.org/team)。 |
+| **CS20** |决策需要 PMC 成员之间达成共识，并记录在项目的主要沟通渠道上。 PMC 会考虑社区意见，但 PMC 拥有最终决定权。 | :white_check_mark: 所有决定都是通过 dev@linkis 投票做出的，并且至少有 3 个 PPMC/IPMC 的 +1 绑定。 |
+| **CS30** |当讨论不足时，该项目使用记录在案的投票规则来建立共识。 | :white_check_mark: 该项目使用标准的 ASF 投票规则。 |
+| **CS40** |在 Apache 项目中，否决仅对代码提交有效。根据 CS30 中定义的 Apache 投票规则，行使否决权的人必须通过技术解释来证明其合理性。 | :white_check_mark: 除了代码提交之外，Apache Linkis 社区尚未使用否决权。 |
+| **CS50** |所有“重要”的讨论都是在项目的主要沟通渠道上以书面形式异步进行的。影响项目的线下、面对面或私人讨论也记录在该频道上。 | :white_check_mark: 所有重要的讨论和结论都以书面形式记录下来。 |
**独立**
| **ID** | **描述** | **状态** |
| -------- | ----- | ---------- |
-| **IN10** |该项目独立于任何公司或组织的影响。 | |
-| **IN20** |贡献者以他们自己的身份行事，而不是作为公司或组织的代表。 | |
-
-
-
-# English
-# Maturity Assessment for Apache Linkis (incubating)
-
-The goals of this maturity model are to describe how Apache projects operate in a concise and high-level way, and to provide a basic framework that projects may choose to use to evaluate themselves.
-
-More details can be found [here](https://community.apache.org/apache-way/apache-project-maturity-model.html).
-
-## Status of this assessment
-
-This assessment is still working in progress.
-
-## Maturity model assessment
-
-The following table is filled according to the [Apache Maturity Model](https://community.apache.org/apache-way/apache-project-maturity-model.html). Mentors and community members are welcome to comment and modify it.
-
-**CODE**
-
-| **ID** | **Description** | **Status** |
-| -------- | ----- | ---------- |
-| **CD10** | The project produces Open Source software for distribution to the public, at no charge. | **YES** The project source code is licensed under the `Apache License 2.0`. |
-| **CD20** | Anyone can easily discover and access the project's code.. | **YES** The [offical website](https://linkis.incubator.apache.org/) includes `Github` link which can access GitHub directly. |
-| **CD30** | Anyone using standard, widely-available tools, can build the code in a reproducible way. | **YES** Apache Linkis provide how-to-build document to tell user how to compile on bare metal. |
-| **CD40** | The full history of the project's code is available via a source code control system, in a way that allows anyone to recreate any released version. | **YES** It depends on git, and anyone can view the full history of the project via commit logs. |
-| **CD50** | The source code control system establishes the provenance of each line of code in a reliable way, based on strong authentication of the committer. When third parties contribute code, commit messages provide reliable information about the code provenance. | **YES** The project uses GitHub and managed by Apache Infra, it ensuring provenance of each line of code to a committer. And the third-party contributions are accepted in accordance with the [Code submission Guide](https:/ [...]
-
-**Licenses and Copyright**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **LC10** | The Apache License, version 2.0, covers the released code. | **YES** The [LICENSE](https://github.com/apache/incubator-linkis/blob/master/LICENSE.txt) is in GitHub repository. And all source files are with APLv2 header, check by `apache/skywalking-eyes@v0.2`. |
-| **LC20** | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | **YES** All [dependencies](https://github.com/apache/incubator-linkis/blob/master/thirdparty/vars.sh) has been checked and non of them create more restrictions than the Apache License does. |
-| **LC30** | The libraries mentioned in LC20 are available as Open Source software. | **YES** See [dependencies](https://github.com/apache/incubator-linkis/blob/master/thirdparty/vars.sh). |
-| **LC40** | Committers are bound by an Individual Contributor Agreement (the "Apache iCLA") that defines which code they may commit and how they need to identify code that is not their own. | **YES** All committers have iCLAs. |
-| **LC50** | The project clearly defines and documents the copyright ownership of everything that the project produces. | **YES** And all source files are with APLv2 header, check by `apache/skywalking-eyes@v0.2`. |
-
-**Releases**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **RE10** | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | **YES** Source release is distributed via [dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/linkis/) and linked from [download page](http://linkis.incubator.apache.org/downloads/downlo [...]
-| **RE20** | The project's PMC (Project Management Committee, see CS10) approves each software release in order to make the release an act of the Foundation. | **YES** All releases have been voted at dev@linkis and general@incubator, and have at least 3 PPMC's votes. |
-| **RE30** | Releases are signed and/or distributed along with digests that anyone can reliably use to validate the downloaded archives. | **YES** All releases are signed, and the [KEYS](https://dist.apache.org/repos/dist/release/incubator/linkis/KEYS) is available. |
-| **RE40** | The project can distribute convenience binaries alongside source code, but they are not Apache Releases, they are provided with no guarantee. | **YES** User can easily build binaries from source code. And we don't provide binaries as Apache Releases. |
-| **RE50** | The project documents a repeatable release process so that someone new to the project can independently generate the complete set of artifacts required for a release. | **YES** We can follow the [Release guide](http://linkis.incubator.apache.org/community/release-process.html) to make new Apache Linkis release. And so far we had 6 different release managers. |
-
-**Quality**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **QU10** | The project is open and honest about the quality of its code. Various levels of quality and maturity for various modules are natural and acceptable as long as they are clearly communicated. | **YES** We encourage user to [report issues](http://linkis.incubator.apache.org/community/feedback.html) |
-| **QU20** | The project puts a very high priority on producing secure software. | **YES** All security issues will be addressed within 3 days. |
-| **QU30** | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | **YES** Website provides a [security page](http://linkis.incubator.apache.org/community/security.html) |
-| **QU40** | The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition to new features. | **YES** All releases are backwards compatibility. |
-| **QU50** | The project strives to respond to documented bug reports in a timely manner. | **YES** The project has resolved 2000+ issues and 4000+ pull requests so far, with very prompt response. |
-
-**Community**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **CO10** | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | **YES** The [website](https://linkis.apache.org/) includes all information user need to run Apache Linkis. |
-| **CO20** | The community welcomes contributions from anyone who acts in good faith and in a respectful manner, and who adds value to the project. | **YES** Apache Linkis provides [Code submission guide](http://linkis.incubator.apache.org/community/pull-request.html) and welcome all good contributions. |
-| **CO30** | Contributions include source code, documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | **YES** All good contributions including code and non-code are welcomed. |
-| **CO40** | The community strives to be meritocratic and gives more rights and responsibilities to contributors who, over time, add value to the project. | **YES** The community has elected 6 new PPMC members and 17 new committers so far. |
-| **CO50** | The project documents how contributors can earn more rights such as commit access or decision power, and applies these principles consistently. | **YES** With the document [committer guide](http://linkis.incubator.apache.org/community/committer-guide.html). |
-| **CO60** | The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects. | **YES** All decisions are made after vote by community members. |
-| **CO70** | The project strives to answer user questions in a timely manner. | **YES** We use dev@linkis, [Github issue](https://github.com/apache/incubator-linkis/issues) and [Github discussion](https://github.com/apache/incubator-linkis/discussions) to do this in a timely manner. |
-
-**Consensus**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **CS10** | The project maintains a public list of its contributors who have decision power. The project's PMC (Project Management Committee) consists of those contributors. | **YES** See [members](http://linkis.incubator.apache.org/community/members.html) with all PPMC members and committers. |
-| **CS20** | Decisions require a consensus among PMC members and are documented on the project's main communications channel. The PMC takes community opinions into account, but the PMC has the final word. | **YES** All decisions are made by votes on dev@linkis, and with at least 3 PPMC's +1 |
-| **CS30** | The project uses documented voting rules to build consensus when discussion is not sufficient. | **YES** The project uses the standard ASF voting rules. |
-| **CS40** |In Apache projects, vetoes are only valid for code commits. The person exercising the veto must justify it with a technical explanation, as per the Apache voting rules defined in CS30. | **YES** Apache Linkis community has not used the veto power yet except for code commits. |
-| **CS50** | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions that affect the project are also documented on that channel. | **YES** All important discussions and conclusions are recorded in written form. |
-
-**Independence**
-
-| **ID** | **Description** | **Status** |
-| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- |
-| **IN10** | The project is independent from any corporate or organizational influence. | **YES** The PPMC members and committer of Apache Linkis are from 6+ companies, and majority of them are NOT From the company that donated this project. |
-| **IN20** | Contributors act as themselves, not as representatives of a corporation or organization. | **YES** The contributors act on their own initiative without representing a corporation or organization. |
-
+|**IN10**|项目独立于任何公司或组织影响。|:white_check_mark: Apache Linkis的PPMC成员和提交人来自家 15 以上的公司|
+|**IN20**|贡献者以自己的身份行事，而不是作为公司或组织的代表。|:white_check_mark: 贡献者自行行动，不代表公司或组织|
diff --git a/src/pages/home/config.json b/src/pages/home/config.json
index 592a4f973a..57dee63bd8 100644
--- a/src/pages/home/config.json
+++ b/src/pages/home/config.json
@@ -21,7 +21,7 @@
},
"home": {
"banner": {
- "slogan": "Linkis 在上层应用和底层引擎之间构建了一层计算中间件。通过使用Linkis 提供的REST/WebSocket/JDBC 等标准接口，上层应用可以方便地连接访问Spark, Presto, Flink 等底层引擎,同时实现跨引擎上下文共享、统一的计算任务和引擎治理与编排能力。"
+ "slogan": "Linkis 构建了一层计算中间件，方便上层应用与底层数据引擎之间的连接、治理和编"
},
"introduce": {
"title": "计算中间件概念",
@@ -67,7 +67,7 @@
},
"home": {
"banner": {
- "slogan": "Linkis builds a computation middleware layer to decouple the upper applications and the underlying data engines, provides standardized interfaces (REST, JDBC, WebSocket etc.) to easily connect to various underlying engines (Spark, Presto, Flink, etc.), while enables cross engine context sharing, unified job& engine governance and orchestration."
+ "slogan": "Linkis builds a computation middleware layer to facilitate connection, governance and orchestration between the upper applications and the underlying data engines."
},
"introduce": {
"title": "Computation Middleware",
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@linkis.apache.org
For additional commands, e-mail: commits-help@linkis.apache.org