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/linkis-website.git
The following commit(s) were added to refs/heads/dev by this push:
new 7892aec7a1 update after graduate (#643)
7892aec7a1 is described below
commit 7892aec7a15d1056f6a95d7573737a614d22af1f
Author: Casion <[email protected]>
AuthorDate: Thu Dec 29 12:07:09 2022 +0800
update after graduate (#643)
---
community/how-to-email.md | 6 +-
community/how-to-release.md | 20 ++---
community/how-to-verify.md | 44 ++++-------
community/site-map.md | 17 ++++-
.../current/how-to-release.md | 21 ++----
.../current/how-to-verify.md | 46 ++++--------
.../current/site-map.md | 20 +++--
maturity.md | 87 ----------------------
8 files changed, 73 insertions(+), 188 deletions(-)
diff --git a/community/how-to-email.md b/community/how-to-email.md
index 8f7d2d33b9..7964d5f97a 100644
--- a/community/how-to-email.md
+++ b/community/how-to-email.md
@@ -24,8 +24,8 @@ The following takes 163 mailboxes as an example:
The subject of the email can be roughly divided into the following types
- **\[DISCUSS]** Discussion on a feature/function/logic modification/CI/CD,
which can be implementation/design/optimization suggestion, etc.
- **\[PROPOSAL]** Proposals, such as adding/removing certain features, are not
much different from \[DISCUSS]
-- **\[VOTE]** Vote for changes/elect Committer/elect new PPMC members, etc.,
such as version release, each version will be voted on in the community dev
mailing list; you can also choose multiple options ,Poll.
-- **\[ANNOUNCE]** Announce the completion of the release of the new version,
announcing the new Committer/PPMC elected, etc.
+- **\[VOTE]** Vote for changes/elect Committer/elect new PMC members, etc.,
such as version release, each version will be voted on in the community dev
mailing list; you can also choose multiple options ,Poll.
+- **\[ANNOUNCE]** Announce the completion of the release of the new version,
announcing the new Committer/PMC elected, etc.
- **\[NOTICE]** Mainly used to notify some temporary announcements, etc., such
as the community sandbox environment is suspended for maintenance/upgrade, the
web official website is abnormally unavailable, etc.; as well as online and
offline weekly meetings/exchange meetings and various Event information
announcements, etc.
- **\[HELP]** Ask for help, because there are many git code notifications, and
sometimes it is impossible to check them in time; in addition, github network
access is limited, and some students may not be able to submit issues through
github smoothly. Initiated by email, it is easier to identify and be perceived.
- **\[VOTE]\[RESULT]** Announce the results of the release vote
@@ -36,7 +36,7 @@ The subject of the email can be roughly divided into the
following types
** General**
- Whenever possible do not send plain HTML messages, but plain text. If you
use QQ mailbox, its email content is in html format by default. Please switch
to plain text text format when writing. For detailed switching instructions,
see the appendix of this article.
-- Developers/community users/PPMC members initiate email discussions/needs for
help/notifications for the content of the above scenarios, please send them to
[email protected]
+- Developers/community users/PMC members initiate email discussions/needs for
help/notifications for the content of the above scenarios, please send them to
[email protected]
- Please put the corresponding type prefix before the email subject: such as
`[HELP] XXXXXXX`, `[DISCUSS] XXXXXXX`
For more information, please refer to the official [Mail
Etiquette](https://infra.apache.org/contrib-email-tips)
https://infra.apache.org/contrib-email-tips
diff --git a/community/how-to-release.md b/community/how-to-release.md
index 081a0c2d13..2865f82c70 100644
--- a/community/how-to-release.md
+++ b/community/how-to-release.md
@@ -4,6 +4,7 @@ sidebar_position: 3
---
# Apache publishing guide
+
> This article takes the release of 1.0.3 Apache version as an example. If it
> is a non-Apache version, please refer to the [detailed
> information](https://incubator.apache.org/guides/releasemanagement.html)
> https://incubator.apache.org/guides/releasemanagement.html
Understand the content and process of Apache's release. Source Release is the
focus of Apache’s attention and is also a required content for release; Binary
Release is optional. Please refer to the following link to find more ASF
release guidelines:
@@ -219,7 +220,7 @@ For encryption settings, please refer to
[here](http://maven.apache.org/guides/m
## 2 Prepare material package & release of apache nexus
-### 2.1 Prepare branch/tag/\release notes
+### 2.1 Prepare branch/tag/release notes
Pull the new branch from the branch to be released as the branch to be
released. If you want to release the $`{release_version}` version now, check
out the new branch `release-${release_version}-${condition_version}` from the
branch to be released, and all after that The operations are all performed on
the `release-${release_version}-${condition_version}` branch, and merge into
the main branch after the final release is completed.
@@ -451,14 +452,10 @@ Please use your apache.org mailbox to send emails, and
use `plain text mode`, fo
:::
:::caution Note
-
All links to checksums, signatures, and public keys must refer to the main
Apache website https://downloads.apache.org/ and should use https://(SSL). For
example: https://downloads.apache.org/linkis/KEYS
-
-The DISCLAIMER-WIP disclaimer is currently used, please add this description
`As the DISCLAIMER-WIP shows....` to the email. If the WIP pending problem is
solved later, it can be removed. Use of WIP, see
https://issues.apache.org/jira/browse/LEGAL-469 for details
:::
- To vote in the Linkis community, send an email to: `[email protected]`
-- To vote in the incubator community, send an email to:
`[email protected]` After Linkis graduates, you only need to vote in
the Linkis community
### 5.1 Linkis community voting stage
@@ -495,8 +492,6 @@ Hello Linkis Community,
GPG user ID:
${YOUR.GPG.USER.ID}
- As the DISCLAIMER-WIP shows, this release still left some license
problems, which will be gradually resolved during incubation.
-
The vote will be open for at least 72 hours or until necessary number of
votes are reached.
Please vote accordingly:
@@ -514,9 +509,6 @@ Hello Linkis Community,
[] All files have license headers if necessary.
[] No unlicensed compiled archives bundled in source archive.
- More detail checklist please refer:
-
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
-
Thanks,
${Linkis Release Manager}
```
@@ -528,18 +520,16 @@ title:
[RESULT][VOTE] Release Apache Linkis ${release_version} ${rc_version}
content:
-Hello Apache Linkis PPMC and Community,
+Hello Apache Linkis PMC and Community,
The vote closes now as 72hr have passed. The vote PASSES with
- xx (+1 non-binding) votes from the PPMC,
- xx (+1 binding) votes from the IPMC,
+ xx (+1 non-binding) votes from the PMC,
xx (+1 non-binding) votes from the rest of the developer community,
and no further 0 or -1 votes.
The vote thread: {vote_mail_address}
- I will now bring the vote to [email protected] to get approval
by the IPMC.
If this vote passes also, the release is accepted and will be published.
Thank you for your support.
@@ -626,7 +616,7 @@ After waiting and confirming that the new release version
is synced to the Apach
> Please make sure that the Apache Staging repository has been published
> successfully, usually mail is published 24 hours after this step
-Send email to `[email protected]`, `[email protected]` and
`[email protected]`
+Send email to `[email protected]`, `[email protected]`
```html
title:
[ANNOUNCE] Apache Linkis ${release_version} available
diff --git a/community/how-to-verify.md b/community/how-to-verify.md
index 83c318494d..f2fa39fbea 100644
--- a/community/how-to-verify.md
+++ b/community/how-to-verify.md
@@ -82,7 +82,7 @@ check result
> If something like the following appears, it means the signature is correct.
> Keyword: **`Good signature`**
```shell
-apache-linkis-xxx-incubating-src.tar.gz
+apache-linkis-xxx-src.tar.gz
gpg: Signature made XXXX
gpg: using RSA key XXXXX
gpg: Good signature from "xxx @apache.org>"
@@ -107,18 +107,18 @@ $ sha512sum --check
apache-linkis-${release_version}-bin.tar.gz.sha512
> Windows
```shell
-$ certUtil -hashfile apache-linkis-${release_version}-incubating-xxx.tar.gz
SHA512
-#Compare the output content with the content of the
apache-linkis-${release_version}-incubating-xxx.tar.gz.sha512 file
+$ certUtil -hashfile apache-linkis-${release_version}-xxx.tar.gz SHA512
+#Compare the output content with the content of the
apache-linkis-${release_version}-xxx.tar.gz.sha512 file
```
### 2.4. Check the file content of the source package
-Unzip `apache-linkis-${release_version}-incubating-src.tar.gz`
+Unzip `apache-linkis-${release_version}-src.tar.gz`
```text
-$ tar -xvf apache-linkis-${release_version}-incubating-src.tar.gz
+$ tar -xvf apache-linkis-${release_version}-src.tar.gz
-$ cd apache-linkis-${release_version}-incubating-src
+$ cd apache-linkis-${release_version}-src
```
#### 2.4.1 Asf license rat check
Mac OS/Linux
@@ -174,7 +174,7 @@ Next, build the project：
```shell
npm run build
```
-The console installation package
`apache-linkis-${version}-incubating-web-bin.tar.gz` will be generated after
the above command is successfully executed
+The console installation package `apache-linkis-${version}-web-bin.tar.gz`
will be generated after the above command is successfully executed
:::caution
1.An error occured when running `npm install`:
@@ -209,7 +209,6 @@ and check as follows:
- [ ] Check whether the source package contains unnecessary files, which makes
the tar package too large
- [ ] Folder contains the word `incubating`
- [ ] There are `LICENSE` and `NOTICE` files
-- [ ] There is a `DISCLAIMER` or `DISCLAIMER-WIP` file
- [ ] The year in the `NOTICE` file is correct
- [ ] Only text files exist, not binary files
- [ ] All files have ASF license at the beginning
@@ -220,16 +219,15 @@ and check as follows:
### 2.5 Check the binary package
> If the binary/web-binary package is uploaded, check the binary package.
-Unzip `apache-linkis-${release_version}-incubating-bin.tar.gz`
+Unzip `apache-linkis-${release_version}-bin.tar.gz`
```shell
-$ mkdir apache-linkis-${release_version}-incubating-bin
-$ tar -xvf apache-linkis-${release_version}-incubating-bin.tar.gz -C
apache-linkis-${release_version}-incubating-bin
-$ cd apache-linkis-${release_version}-incubating-bin
+$ mkdir apache-linkis-${release_version}-bin
+$ tar -xvf apache-linkis-${release_version}-bin.tar.gz -C
apache-linkis-${release_version}-bin
+$ cd apache-linkis-${release_version}-bin
```
and check as follows:
- [ ] There are `LICENSE` and `NOTICE` files
-- [ ] There is a `DISCLAIMER` or `DISCLAIMER-WIP` file
- [ ] The year in the `NOTICE` file is correct
- [ ] All text files have ASF license at the beginning
- [ ] Check the third-party dependent license:
@@ -247,23 +245,11 @@ If you initiate a posting vote, you can refer to this
response example to reply
<font color="red">
When replying to the email, you must bring the information that you have
checked by yourself. Simply replying to `+1 approve` is invalid.
-When PPMC votes in the [email protected] linkis community, Please bring
the binding suffix to indicate that it has a binding vote for the vote in the
linkis community, and it is convenient to count the voting results.
-
-When IPMC votes in the [email protected] incubator community.
Please bring the binding suffix to indicate that the voting in the incubator
community has a binding vote, which is convenient for counting the voting
results.
+When PMC votes in the [email protected] linkis community, Please bring
the binding suffix to indicate that it has a binding vote for the vote in the
linkis community, and it is convenient to count the voting results.
</font>
-:::caution note
-If you have already voted on [email protected], you can take it directly
to the incubator community when you reply to the vote, such as:
-```html
-//Incubator community voting, only IPMC members have binding binding，PPMC
needs to be aware of binding changes
-Forward my +1 from dev@linkis (non-binding)
-Copy my +1 from linkis DEV ML (non-binding)
-````
-:::
-
-
-Non-PPMC/Non-IPMC member
+Non-PMC member
```html
+1 (non-binding)
I checked:
@@ -274,9 +260,8 @@ I checked:
5.
````
-PPMC/IPMC member
+PMC member
```html
-//Incubator community voting, only IPMC members have binding binding
+1 (binding)
I checked:
1. All download links are valid
@@ -293,5 +278,4 @@ If you have maven tools installed, you can replace ./mvnw
or mvnw.cmd with your
mvnw is short for Maven Wrapper. It can support running Maven projects without
installing Maven and configuring environment variables. If it can't find it, it
will download the corresponding Maven version according to the configuration
file
-
</font>
\ No newline at end of file
diff --git a/community/site-map.md b/community/site-map.md
index f8f8a45f6e..3a7f138c48 100644
--- a/community/site-map.md
+++ b/community/site-map.md
@@ -37,6 +37,11 @@ sidebar_position: 12
- The incubator homepage https://incubator.apache.org/ has related video
sharing and ppt
+- Project chairs https://people.apache.org/phonebook.html?service=pmc-chairs
+
+- How to perform the duties of the PMC chair
https://www.apache.org/dev/pmc.html#chair%7D
+
+- Project VP Information https://www.apache.org/foundation/#who-runs-the-asf
## Linkis related links
- linkis-logo https://svn.apache.org/repos/asf/comdev/project-logos/originals/
@@ -45,11 +50,14 @@ sidebar_position: 12
- Board Reports https://whimsy.apache.org/board/minutes/Linkis.html
- Linkis name application jira
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-192?filter=allissues
- Project status file https://incubator.apache.org/projects/linkis.html
-- Official website legitimacy check
https://whismy.apache.org/pods/project/linkis
+
- View ppmc mail and other information
https://whhimsy.apache.org/roster/ppmc/linkis
- project file
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/linkis.xml
- podling file
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/linkis.yml
-- clutch https://incubator.apache.org/clutch/linkis.html
+
+- Report reporting tool after graduation https://reporter.apache.org/wizard/
(Chair and PMC can view it)
+- Project Health Score https://reporter.apache.org/chi.py#linkis
+- PMC information update
https://svn.apache.org/repos/private/committers/board/committee-info.txt (Chair
and PMC can view it)
- View submitting users over a period of time
@@ -62,4 +70,7 @@
https://github.com/apache/linkis/pulls?q=is%3Apr+is%3Aclosed+closed%3A%3E2021-08
- View closed issues within a certain period of time
`\[Filters] is:pr is:closed closed:>2021-08-02 `
-https://github.com/apache/linkis/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-08-02
\ No newline at end of file
+https://github.com/apache/linkis/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-08-02
+
+- ~~Official website legitimacy check
https://whismy.apache.org/pods/project/linkis~~
+- ~~clutch https://incubator.apache.org/clutch/linkis.html~~
\ No newline at end of file
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
index 584614eafd..7e19f2a65f 100644
---
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
+++
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/how-to-release.md
@@ -571,18 +571,17 @@ git tag 一旦创建不可删除(分支可以删除)，所以在创建tag前 确
:::
-> Linkis 仍在孵化阶段，需要进行两次投票
+> Linkis 已经孵化毕业，自需要进行社区投票
- Linkis 社区投票，发送邮件至：`[email protected]`
-- incubator 社区投票，发送邮件至：`[email protected]` Linkis毕业后，只需要在Linkis社区投票
- 在社区投票的邮件正文中的${Linkis Release Manager}，填写负责本次发布的人员，一般是邮件发送人，如`Shuai Di`
### 5.1 Linkis 社区投票阶段
-1. Linkis 社区投票，发起投票邮件到`[email protected]`。PMC需要先按照文档检查版本的正确性，然后再进行投票。
经过至少72小时并统计到3个`+1` PMC member票后，才可进入下一阶段的投票。
+1. Linkis 社区投票，发起投票邮件到`[email protected]`。PMC需要先按照文档检查版本的正确性，然后再进行投票。
经过至少72小时并统计到3个`+1` PMC member票后，才能结束投票。
-2. 宣布投票结果,发起投票结果邮件到`[email protected]`。
+2. 宣布投票结果, 发起投票结果邮件到`[email protected]`。
#### 5.1.1 Linkis 社区投票模板
@@ -635,8 +634,6 @@ Hello Linkis Community,
[ ] All files have license headers if necessary.
[ ] No unlicensed compiled archives bundled in source archive.
- More detail checklist please refer:
-
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
Steps to validate the release，Please refer to:
https://linkis.apache.org/community/how-to-verify
@@ -694,26 +691,23 @@ ${Linkis Release Manager}
[RESULT][VOTE] Release Apache Linkis ${release_version} ${rc_version}
邮件正文：
-Hello Apache Linkis PPMC and Community,
+Hello Apache Linkis PMC and Community,
The vote closes now as 72hr have passed. The vote PASSES with
- xx (+1 binding) votes from the PPMC,
- xx (+1 binding) votes from the IPMC,
+ xx (+1 binding) votes from the PMC,
xx (+1 non-binding) votes from the rest of the developer community,
and no further 0 or -1 votes.
The vote thread: {vote_mail_address}
- I will now bring the vote to [email protected] to get approval
by the IPMC.
If this vote passes also, the release is accepted and will be published.
Thank you for your support.
${Linkis Release Manager}
```
注:
-- PPMC:podling Project Management Committee (PPMC) linkis的ppmc
-- IPMC: Incubator Project Management Committee (IPMC)
一般是孵化社区的PMC，linkis的导师都是这个角色
+- PMC: Project Management Committee (PMC) linkis的pmc
### 5.2 其他
@@ -803,7 +797,8 @@ linkis的官网下载地址应该指向apache的官方地址
> 请确保Apache Staging仓库已发布成功，一般是在该步骤的24小时后发布邮件
-发邮件到 `[email protected]` 、
`[email protected]`和`[email protected]`
+发邮件到 `[email protected]` 、 `[email protected]`
+
```html
邮件标题：
[ANNOUNCE] Apache Linkis ${release_version} available
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 3ab9e98aa0..ec5814b4df 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
@@ -82,7 +82,7 @@ $ gpg --verify
apache-linkis-${release_version}-bin.tar.gz.asc apache-linkis-${r
> 出现类似以下内容则说明签名正确，关键字：**`Good signature`**
```shell
-apache-linkis-xxx-incubating-src.tar.gz
+apache-linkis-xxx-src.tar.gz
gpg: Signature made XXXX
gpg: using RSA key XXXXX
gpg: Good signature from "xxx @apache.org>"
@@ -107,18 +107,18 @@ $ sha512sum --check
apache-linkis-${release_version}-bin.tar.gz.sha512
> Windows
```shell
-$ certUtil -hashfile apache-linkis-${release_version}-incubating-xxx.tar.gz
SHA512
-#并将输出内容与 apache-linkis-${release_version}-incubating-xxx.tar.gz.sha512文件内容作对比
+$ certUtil -hashfile apache-linkis-${release_version}-xxx.tar.gz SHA512
+#并将输出内容与 apache-linkis-${release_version}-xxx.tar.gz.sha512文件内容作对比
```
### 2.4. 检查源码包的文件内容
-解压缩`apache-linkis-${release_version}-incubating-src.tar.gz`
+解压缩`apache-linkis-${release_version}-src.tar.gz`
```text
-$ tar -xvf apache-linkis-${release_version}-incubating-src.tar.gz
+$ tar -xvf apache-linkis-${release_version}-src.tar.gz
-$ cd apache-linkis-${release_version}-incubating-src
+$ cd apache-linkis-${release_version}-src
```
#### 2.4.1 ASF许可证RAT检查
@@ -208,25 +208,21 @@ $ npm install
- [ ] 检查源码包是否包含由于包含不必要文件，致使tar包过于庞大
- [ ] 存在`LICENSE`和`NOTICE`文件
-- [ ] 存在`DISCLAIMER`或`DISCLAIMER-WIP`文件
- [ ] `NOTICE`文件中的年份正确
- [ ] 只存在文本文件，不存在二进制文件
- [ ] 所有文件的开头都有ASF许可证
- [ ] 能够正确编译
-- [ ] 检查是否有多余文件或文件夹，例如空文件夹等
-- [ ] .....
-
### 2.5 检查二进制包
>如果上传了项目的二进制包/linkis-web的编译包
-解压缩`apache-linkis-${release_version}-incubating-bin.tar.gz`，
+解压缩`apache-linkis-${release_version}-bin.tar.gz`，
```shell
-$ mkdir apache-linkis-${release_version}-incubating-bin
-$ tar -xvf apache-linkis-${release_version}-incubating-bin.tar.gz -C
apache-linkis-${release_version}-incubating-bin
-$ cd apache-linkis-${release_version}-incubating-bin
+$ mkdir apache-linkis-${release_version}-bin
+$ tar -xvf apache-linkis-${release_version}-bin.tar.gz -C
apache-linkis-${release_version}-bin
+$ cd apache-linkis-${release_version}-bin
```
进行如下检查：
@@ -250,27 +246,13 @@ $ cd apache-linkis-${release_version}-incubating-bin
<font color="red">
回复的邮件一定要带上自己检查了那些项信息，仅仅回复`+1 approve`，是无效的。
-PPMC在[email protected] linkis的社区投票时，请带上
binding后缀，表示对linkis社区中的投票具有约束性投票，方便统计投票结果。
-
-IPMC在[email protected] incubator社区投票，请带上
binding后缀，表示对incubator社区中的投票具有约束性投票，方便统计投票结果。
+PMC在[email protected] linkis的社区投票时，请带上
binding后缀，表示对linkis社区中的投票具有约束性投票，方便统计投票结果。
</font>
-:::caution 注意
-如果在[email protected]已经投过票，在incubator社区进行投票回复时，可以直接带过去,<font
color="red">需要注意约束性</font> 如:
-
-```html
-//incubator社区 投票时，只有IPMC成员才具有约束性 binding，PPMC需要注意约束性的变化
-Forward my +1 from dev@linkis (non-binding)
-Copy my +1 from linkis DEV ML (non-binding)
-```
-:::
-
-
-
-非PPMC/IPMC成员
+非PMC成员
```html
+1 (non-binding)
I checked:
@@ -281,9 +263,9 @@ I checked:
5. ....
```
-PPMC/IPMC成员
+PMC成员
```html
-//incubator社区 投票时，只有IPMC成员才具有约束性 binding
+
+1 (binding)
I checked:
1. All download links are valid
diff --git
a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md
b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md
index 19e19f2be7..dc9c439fd4 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs-community/current/site-map.md
@@ -37,20 +37,27 @@ sidebar_position: 12
- 孵化器主页 https://incubator.apache.org/ 有相关的视频分享和ppt
+- 项目主席查询 https://people.apache.org/phonebook.html?service=pmc-chairs
+
+- 如何履行PMC主席的职责 https://www.apache.org/dev/pmc.html#chair%7D
+
+- 项目VP信息表 https://www.apache.org/foundation/#who-runs-the-asf
+
+
## Linkis相关的链接
- linkis-logo https://svn.apache.org/repos/asf/comdev/project-logos/originals/
- 项目列表 https://projects.apache.org/project.html?linkis
-- 维护IP Clearance
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/
+- IP Clearance
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/
- Board Reports https://whimsy.apache.org/board/minutes/Linkis.html
-- Linkis的名字申请jira
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-192?filter=allissues
+- Linkis的名字申请工单
https://issues.apache.org/jira/projects/PODLINGNAMESEARCH/issues/PODLINGNAMESEARCH-192?filter=allissues
- 项目状态文件 https://incubator.apache.org/projects/linkis.html
-- 官网合法性检查 https://whimsy.apache.org/pods/project/linkis
- ppmc 邮件等信息查看 https://whimsy.apache.org/roster/ppmc/linkis
- project 文件
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/linkis.xml
- podling 文件
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/linkis.yml
-- clutch https://incubator.apache.org/clutch/linkis.html
-
+- 毕业后report上报工具 https://reporter.apache.org/wizard/ （主席和PMC可查看）
+- 项目健康度评分 https://reporter.apache.org/chi.py#linkis
+- PMC信息更新
https://svn.apache.org/repos/private/committers/board/committee-info.txt
（主席和PMC可查看）
- 查看某段时间内的提交用户
https://github.com/apache/linkis/graphs/contributors?from=2021-08-02&to=2022-07-21&type=c
@@ -63,3 +70,6 @@
https://github.com/apache/linkis/pulls?q=is%3Apr+is%3Aclosed+closed%3A%3E2021-08
- 查看某段时间内 close的issue
`\[Filters] is:pr is:closed closed:>2021-08-02 `
https://github.com/apache/linkis/issues?q=is%3Aissue+is%3Aclosed+closed%3A%3E2021-08-02
+
+- ~~官网合法性检查 https://whimsy.apache.org/pods/project/linkis~~
+- ~~clutch https://incubator.apache.org/clutch/linkis.html~~
diff --git a/maturity.md b/maturity.md
deleted file mode 100644
index 441963ee3b..0000000000
--- a/maturity.md
+++ /dev/null
@@ -1,87 +0,0 @@
-# Maturity Self Assessment for Apache Linkis
-
-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 [official
website](https://linkis.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/build)
document to tell user how to compile from source code. |
-| **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 is 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/linkis/blob/master/LICENSE) is in GitHub
repository. And all source files are with APLv2 header, all change will trigger
Git Action auto check by [...]
-| **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/linkis/blob/master/linkis-dist/release-docs/LICENSE)
has been checked and none of them create more restrictions than the Apache
License does. |
-| **LC30** | The libraries mentioned in LC20 are available as Open Source
software.
| :white_check_mark: See
[dependencies](https://github.com/apache/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.apache.org/download/main). |
-| **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.apache.org/community/release-process.html) to
make new Apache Linkis release. And so far we had 7 different release
managers(2022/10/26). |
-
-**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/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.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 1400+ issues and
1800+ pull requests so far(2022/10/26), 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.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 13 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.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/linkis/issues) and [github
discussion](https://github.com/apache/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.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 of Linkis are from 15
different organizations(Beluga Open Source, Binance.us, Boss Zhipin, ByteDance,
Clory and Smy Cloud, Guanzhou Bank, HONOR, Hangzhou Link Cloud Technology Co.,
Ltd., Huawei, Kyligence Inc, Sensors Data, Tencent, Tianyi Cloud, WeBank,
iQIYI)(2022/10/26).|
-| **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. |
-
-----------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
