This is an automated email from the ASF dual-hosted git repository.
hulk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-kvrocks-website.git
The following commit(s) were added to refs/heads/main by this push:
new f2ecdd3 Update the maturity status (#98)
f2ecdd3 is described below
commit f2ecdd3743fbbeddbbe293ced5fd49d6d74a0626
Author: hulk <[email protected]>
AuthorDate: Wed May 3 22:35:06 2023 +0800
Update the maturity status (#98)
- Change the number of release managers from 3 to 4
- Fix typo: Github should be GitHub
---
maturity.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/maturity.md b/maturity.md
index 428cefe..c0d4576 100644
--- a/maturity.md
+++ b/maturity.md
@@ -17,7 +17,7 @@ The following table is filled according to the [Apache
Maturity Model](https://c
| **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://kvrocks.apache.org/) includes `Github` link which can access
GitHub directly. |
+| **CD20** | Anyone can easily discover and access the project's code..
| **YES** The [offical
website](https://kvrocks.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 Kvrocks provide
[how-to-build](/docs/getting-started#build-and-run-kvrocks-from-source)
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 [Contributing Guide](https://kv [...]
@@ -40,7 +40,7 @@ The following table is filled according to the [Apache
Maturity Model](https://c
| **RE20** | The project's PPMC (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
[email protected] and [email protected], 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/kvrocks/KEYS) are
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 do not 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](https://kvrocks.apache.org/community/create-a-release) to make new
Apache Kvrocks releases, and so far we had 3 different release managers. |
+| **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](https://kvrocks.apache.org/community/create-a-release) to make new
Apache Kvrocks releases, and so far we had 4 different release managers. |
### Quality
@@ -62,7 +62,7 @@ The following table is filled according to the [Apache
Maturity Model](https://c
| **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 2 new PPMC members and 4 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 [committer
guide](https://kvrocks.incubator.apache.org/community/vote-a-core-developer/)
in the community document. |
| **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 [email protected], [Github
issue](https://github.com/apache/incubator-kvrocks/issues) and [Github
discussion](https://github.com/apache/incubator-kvrocks/discussions) to do this
in a timely manner. |
+| **CO70** | The project strives to answer user questions in a timely manner.
| **YES** We use [email protected], [GitHub
issue](https://github.com/apache/incubator-kvrocks/issues) and [GitHub
discussion](https://github.com/apache/incubator-kvrocks/discussions) to do this
in a timely manner. |
### Consensus
