This is an automated email from the ASF dual-hosted git repository. wwei pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/yunikorn-site.git
The following commit(s) were added to refs/heads/master by this push:
new 1b10a1344 [YUNIKORN-1226] Removed incubator maturity status page.
(#162)
1b10a1344 is described below
commit 1b10a13446bbff125eebce10403c26ad65a85f6e
Author: Saad Ur Rahman <[email protected]>
AuthorDate: Thu Jun 2 00:22:05 2022 -0400
[YUNIKORN-1226] Removed incubator maturity status page. (#162)
---
docusaurus.config.js | 4 --
.../community/maturity.md | 76 ----------------------
src/pages/community/maturity.md | 76 ----------------------
3 files changed, 156 deletions(-)
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 0b9a64d0c..04cb8a71b 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -114,10 +114,6 @@ module.exports = {
to: 'community/people',
label: 'People',
},
- {
- to: 'community/maturity',
- label: 'Incubation Maturity Assessment',
- },
]
},
{
diff --git a/i18n/zh-cn/docusaurus-plugin-content-pages/community/maturity.md
b/i18n/zh-cn/docusaurus-plugin-content-pages/community/maturity.md
deleted file mode 100644
index 705199887..000000000
--- a/i18n/zh-cn/docusaurus-plugin-content-pages/community/maturity.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-id: maturity
-title: Apache 成熟度模型
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-## Apache YuniKorn (Incubating) 成熟度自我评估
-
-这是对 Apache YuniKorn (Incubating) 作为 Apache 项目的成熟度评估。
-它旨在告知（导师、社区、孵化器 PMC 和 ASF 董事会）将 YuniKorn 作为顶级 Apache 项目毕业的决定。
-它基于 [ASF
项目成熟度模型](https://community.apache.org/apache-way/apache-project-maturity-model.html)。
-
-### 成熟度模型评估
-我们鼓励导师和社区成员对此页面做出贡献并发表评论，下表总结了项目对 Apache 成熟度模型的自我评估详情。
-
-| ID | 描述
| 说明
|
-|------|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------|
-| CD10 | 该项目免费向公众发布开源软件。
| 项目源代码在 Apache 许可证 2.0 版下获得许可。
|
-| CD20 | 任何人都可以轻松地发现和访问项目的代码。
| 源代码可从git存储库中获得，并链接自 YuniKorn 网站。
|
-| CD30 | 任何基于标准或广泛使用工具的人都可以以可复制的方式构建代码。
| 源代码是通过 GitHub
操作为每个拉取请求提交自动构建的，包括许可证检查、单元测试和端到端测试。网站上记录了在本地执行相同操作的开发环境设置和构建的说明。
|
-| CD40 | 项目代码的完整历史可通过源代码控制系统获得，任何人都可以重新创建任何已发布的版本。
| 提交历史从项目一开始就可用。在孵化期内发布的所有版本都在存储库中标记。
|
-| CD50 | 源代码控制系统基于提交者进行强身份验证，以可靠的方式确定每行代码的出处。当第三方贡献代码时，提交消息会提供有关代码来源的可靠信息。 |
该项目使用多个 git 存储库，全部由 Apache Infra 管理，确保每一行代码的来源都来自提交者。在审查和批准 GitHub
拉取请求后，将合并所有代码。 |
-| |
|
-| LC10 | Apache 许可证 2.0 版本涵盖了已发布的代码。
| 发布的源代码内明确指出了许可证。Docker的镜像内也有明确的许可证信息。
|
-| LC20 | 作为项目代码的强制性依赖项的库，项目内容不会产生比Apache许可证更多的限制。
| 强制性依赖项列表已经过审查，仅包含已批准的许可证。
|
-| LC30 | LC20 中提到的库可作为开源软件使用
| 所有强制性依赖项都可以作为开源软件使用。
|
-| LC40 | 提交者受个人贡献者协议（“Apache iCLA”）的约束，该协议定义了他们可以提交哪些代码以及他们需要如何识别不属于他们自己的代码。
| 该项目使用由 Apache Infra 管理的存储库，写入权限需要一个Apache帐户，该帐户需要一个ICLA文件。
|
-| LC50 | 该项目清楚地定义并记录了项目产生的所有内容的所有版权。
|
存储库中的所有文件都有适当的标头。作为预提交工作流程的一部分，自动化流程已到位并确保每个文件都具有预期的许可证标题。
|
-| |
|
[...]
-| RE10 | 发行版本由源代码组成，使用标准和开放存档格式分发，这些格式有望长期保持可读性。
| 最新版本可通过网站上的下载页面获得。所有版本都可以通过存档
https://archive.apache.org/dist/incubator/yunikorn/ 获取。源代码和 docker
镜像可以从网站的链接获取。 |
-| RE20 | 项目的 PMC（项目管理委员会，参见 CS10）批准每个软件的发行版本，以使该版本成为基金会的行为。
| 所有孵化版本均已获得 YuniKorn 社区和孵化成员的批准，均获得至少 3 (P)PMC 投票且 +1 多于 -1。
|
-| RE30 | 发行的版本与 digest 要一起签名和/或分发，任何人都可以使用 digest 来验证下载的档案的可靠性。
| 版本已签名，密钥可从 YuniKorn 下载页面获得。每个版本都有一个 SHA-512 校验和，以防止内容被篡改。
|
-| RE40 | 该项目可以将便利的二进制文件与源代码一起分发，但它们不是 Apache 版本，而且不提供任何保证。
| Docker镜像可以通过Apache帐户从Dockerhub获取。
|
-| RE50 | 该项目记录了一个可重复的发布过程，以便项目的新手可以独立生成发布所需的完整工具集。
| 创建和检查发布的过程已记录在案。发布过程几乎是完全自动化的。到目前为止，在孵化期间发布的五个版本中的每个都使用了不同的版本管理器。
|
-| |
|
|
-| QU10 | 该项目对其代码的质量公开且诚实。各个模块的不同质量和成熟度水平是自然的，只要能够清楚地沟通就可以接受。
| 未解决的问题在公共Jira中列出，并在JIRA、聊天和邮件列表中进行讨论。
|
-| QU20 | 该项目高度重视软件的生产安全性。
| 安全问题以最高优先级进行处理。我们使用Apache的默认方式来提交安全相关的信息。
|
-| QU30 | 该该项目提供了一个记录良好、安全且私有的报告安全问题的渠道，以及一种记录在案的应对方式。
|
报告安全问题的过程记录在网站上：https://yunikorn.apache.org/zh-cn/community/how_to_contribute#报告安全问题
。 |
-| QU40 | 该项目高度重视向后的兼容性，它旨在记录任何不兼容的更改，并提供工具和文档来帮助用户过渡到新功能。
| 每个版本在包含发行说明（摘自Jira）的网站上都有一个“发布公告”。它的目标是在给定的主要版本中对不进行向后不兼容的更改进行说明。
|
-| QU50 | 该项目会尽力及时地响应记录在案的错误报告。
| 我们的社区会非常积极地响应错误报告，通常会在短时间内修复它们。
|
-| |
|
-| CO10 | 该项目有一个被人熟知的主页，其中有指向了根据此成熟度模型进行操作所需的所有信息。
| 此网站描述了该项目的相关信息，并包含指向所有相关内容的链接（例如，问题跟踪器、源存储库、邮件列表和聊天频道）。
|
-| CO20 | 社区欢迎任何人以真诚和尊重的方式做出贡献，也欢迎这些为项目增加价值的人们。
| 社区非常欢迎Committer的加入，也正在积极寻找新的Committer。
|
-| CO30 | 项目贡献包括源代码、文档、建设性的错误报告、建设性的讨论、营销以及常规的为项目增加价值的任何事情。
| 社区欢迎所有贡献，例如文档翻译或网站改进，并且非常清楚贡献的内容不仅仅是代码。
|
-| CO40 | 社区致力于精英管理，并赋予贡献者更多的权利和责任，随着时间的推移，这些贡献者会为项目增加价值。
| 在孵化阶段我们选出了来自6个不同组织的2名新导师、8名新的committer、4名新的PPMC成员。
|
-| CO50 | 该项目记录了贡献者如何获得更多权利，例如提交访问权或决策权，并始终如一地应用这些原则。
| 成为committer或PPMC成员的过程已经记录在网站上。
|
-| CO60 | 社区的运作基于拥有决策权的成员的共识（见CS10）。独裁者——不管是否仁慈——在Apache项目中都不受欢迎。
| 该项目旨在建立共识。到目前为止，所有PPMC的投票都是一致的。
|
-| CO70 | 该项目力求及时地回答用户的问题。
| 对对报告的问题或提问的回复通常会由社区在几个小时内完成。
|
-| |
|
|
-| CS10 | 该项目保留有决策权的贡献者的公开名单。项目的PMC项目管理委员会由这些贡献者组成。
| Committer和PPMC成员列在网站的社区页面
https://yunikorn.apache.org/zh-cn/community/people 。
|
-| CS20 | 决策需要在PMC成员之间达成共识，并记录在项目的主要沟通渠道上。PMC会考虑社区的意见，但PMC拥有最终决定权。
| 所有重要的决定都是通过邮件列表上以协商一致的方式做出的。
|
-| CS30 | 当讨论不够充分时，该项目使用记录在案的投票规则来建立共识。
| 该项目使用标准的ASF投票规则来进行处理。
|
-| CS40 | 在Apache项目中，否决仅对代码提交有效。根据CS30中定义的Apache投票规则，行使否决权的人必须通过技术解释来证明其合理性。
| 该项目在孵化期间的任何时候都没有使用过否决权。
|
-| CS50 | 所有“重要”的讨论都是在项目的主要沟通渠道上以书面形式推进式地进行。该频道还记录了影响项目的离线、面对面或私人讨论的讨论。
| 项目的主要沟通渠道是邮件列表。不过还有其他频道，例如聊天频道，但不会用于重要的项目讨论。
|
-| |
|
[...]
-| IN10 | 该项目独立于任何公司或组织的影响。
| Committer和PPMC成员是一群来自至少14个不同组织的充满激情的人。
|
-| IN20 | 贡献者会以他们自己的身份行事，而不是作为公司或组织的代表。
| 贡献者在不代表公司或组织的情况下可以主动采取行动。
|
-| |
|
|
diff --git a/src/pages/community/maturity.md b/src/pages/community/maturity.md
deleted file mode 100644
index 01892ce59..000000000
--- a/src/pages/community/maturity.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-id: maturity
-title: Apache Maturity Model
----
-
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements. See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership. The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-"License"); you may not use this file except in compliance
-with the License. You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied. See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-## Apache YuniKorn (Incubating) Maturity self assessment
-
-This is an assessment of the maturity of Apache YuniKorn (Incubating) as an
Apache project.
-It is intended to inform the decision (of mentors, community, incubator PMC
and ASF Board of Directors) to graduate YuniKorn as a top-level Apache project.
-It is based on the [ASF project maturity
model](https://community.apache.org/apache-way/apache-project-maturity-model.html).
-
-### Maturity Model Assessment
-Mentors and community members are encouraged to contribute to this page and
comment on it, the following table summarizes project’s self-assessment against
the Apache Maturity Model.
-
-| ID | Description
| Status
[...]
-|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
-| CD10 | The project produces Open Source software for distribution to the
public, at no charge.
| The project source code is licensed under the
Apache License, version 2.0.
[...]
-| CD20 | Anyone can easily discover and access the project’s code.
| The source code is available from a set of git
repositories, linked from the YuniKorn website.
[...]
-| CD30 | Anyone using standard, widely-available tools, can build the code in
a reproducible way.
| The source code is automatically built for each
Pull Request commit, with license checks, unit and end to end tests, via GitHub
actions. Development environment setup and build instructions to do the same
locally are documente [...]
-| 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.
| The commit history is available from the beginning
of the project. All releases that have been made during the incubation period
are tagged in the repository.
[...]
-| 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. | The project uses multiple git
repositories, all managed by Apache Infra, ensuring provenance of each line of
code to a committer. All code is checked in after review and approval of a
GitHub pull-request. [...]
-| |
|
[...]
-| LC10 | The Apache License, version 2.0, covers the released code.
| Source distributions clearly states the license.
Docker images are clearly licensed.
[...]
-| LC20 | Libraries that are mandatory dependencies of the project’s code do
not create more restrictions than the Apache License does.
| The list of mandatory dependencies have been
reviewed to contain approved licenses only.
[...]
-| LC30 | The libraries mentioned in LC20 are available as Open Source software
| All mandatory dependencies are available as open
source software.
[...]
-| 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.
| The project uses a repository managed by
Apache Infra, write access requires an Apache account, which requires an ICLA
on file.
[...]
-| LC50 | The project clearly defines and documents the copyright ownership of
everything that the project produces.
| All files in the source repository have appropriate
headers. An automated process as part of the pre-commit workflow is in place to
ensure every file has the expected license header.
[...]
-| |
|
[...]
-| RE10 | Releases consist of source code, distributed using standard and open
archive formats that are expected to stay readable in the long term.
| Recent releases are available via the download page
on the website. All releases are available via the archive
https://archive.apache.org/dist/incubator/yunikorn/. Source code and docker
images are linked to from the website. [...]
-| 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.
| All incubating releases have been approved by the
YuniKorn community and the Incubator, all with at least 3 (P)PMC votes and more
+1 than -1.
[...]
-| RE30 | Releases are signed and/or distributed along with digests that anyone
can reliably use to validate the downloaded archives.
| Releases are signed, the keys are available from the
YuniKorn download page. Every release has a SHA-512 checksum to prevent content
tampering.
[...]
-| RE40 | The project can distribute convenience binaries alongside source
code, but they are not Apache Releases, they are provided with no guarantee.
| Docker images are available from Dockerhub
under the Apache account.
[...]
-| 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.
| The processes to create and check a release
are documented. The release process is almost fully automated. Each of the five
releases made so far during the incubation period has used a different release
manager. [...]
-| |
|
[...]
-| 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.
| Open issues are listed in the public Jira and
discussed in JIRA, on chat and the mailing list.
[...]
-| QU20 | The project puts a very high priority on producing secure software.
| Security issues are treated with the highest
priority. We use Apache's default way to submit security related information.
[...]
-| QU30 | The project provides a well-documented, secure and private channel to
report security issues, along with a documented way of responding to them.
| The process to report a security issue is documented
on the website:
https://yunikorn.apache.org/community/how_to_contribute#report-a-security-issue.
[...]
-| 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.
| Each release contains a "Release Announcement"
on the website containing the release notes (extracted from Jira). The project
aims to make no backward incompatible changes within a given major version.
[...]
-| QU50 | The project strives to respond to documented bug reports in a timely
manner.
| The community is very active in responding to bug
reports and usually fixes them within a short time period.
[...]
-| |
|
[...]
-| CO10 | The project has a well-known homepage that points to all the
information required to operate according to this maturity model.
| The website describes the project and
contains links to all relevant systems (e.g., issue tracker, source
repositories, mailing lists and chat channel).
[...]
-| CO20 | The community welcomes contributions from anyone who acts in good
faith and in a respectful manner, and who adds value to the project.
| Committers are really welcome contributions and
the community is actively seeking for new committers.
[...]
-| CO30 | Contributions include source code, documentation, constructive bug
reports, constructive discussions, marketing and generally anything that adds
value to the project.
| The community welcomes all contributions, e.g.,
also documentation translation or website improvements, and is very clear about
contributions being more than code.
[...]
-| CO40 | The community strives to be meritocratic and gives more rights and
responsibilities to contributors who, over time, add value to the project.
| 2 new mentors, 8 new committers, 4 new PPMC
members from 6 different organizations have been elected during the incubation
phase.
[...]
-| CO50 | The project documents how contributors can earn more rights such as
commit access or decision power, and applies these principles consistently.
| The process to become a committer or PPMC member
is documented on the website.
[...]
-| 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.
| The project works to build consensus. All
PPMC votes have been unanimous so far.
[...]
-| CO70 | The project strives to answer user questions in a timely manner.
| Responses to reported issues or asked questions
typically are handled by the community withing a matter of a few hours.
[...]
-| |
|
[...]
-| 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.
| Committers and PPMC members are listed on
the website’s community page https://yunikorn.apache.org/community/people.
[...]
-| 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.
| All important decisions were made by consensus
on the mailing list.
[...]
-| CS30 | The project uses documented voting rules to build consensus when
discussion is not sufficient.
| 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.
| The project has not used a veto at any point
during incubation.
[...]
-| CS50 | All "important" discussions happen asynchronously in written form on
the project’s main communications channel. Offline, face-to-face or private
discussions 11 that affect the project are also documented on that channel.
| The main communication channel is the mailing
list. There are other channels, such as the chat channel, which are not used
for important project discussions.
[...]
-| |
|
[...]
-| IN10 | The project is independent from any corporate or organizational
influence.
| The committers and PPMC members are a group of
passionate people from at least 14 different organizations.
[...]
-| IN20 | Contributors act as themselves, not as representatives of a
corporation or organization.
| The contributors act on their own
initiative without representing a corporation or organization.
[...]
-| |
|
[...]
