This is an automated email from the ASF dual-hosted git repository.
huxing pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-dubbo.wiki.git
The following commit(s) were added to refs/heads/master by this push:
new bb8c905 create apache maturity model assessment
bb8c905 is described below
commit bb8c905178f56206f095954921d8d69597f4a6fa
Author: Huxing Zhang <[email protected]>
AuthorDate: Tue Apr 2 17:48:39 2019 +0800
create apache maturity model assessment
---
Apache-Maturity-Model-Assessment-for-Dubbo.md | 57 +++++++++++++++++++++++++++
1 file changed, 57 insertions(+)
diff --git a/Apache-Maturity-Model-Assessment-for-Dubbo.md
b/Apache-Maturity-Model-Assessment-for-Dubbo.md
new file mode 100644
index 0000000..af83b77
--- /dev/null
+++ b/Apache-Maturity-Model-Assessment-for-Dubbo.md
@@ -0,0 +1,57 @@
+## Overview
+
+This is an assessment of the Apache Dubbo podling’s maturity, meant to help
inform the decision (of the mentors, community, Incubator PMC and ASF Board of
Directors) to graduate it as a top-level Apache project.
+
+It is based on the ASF project maturity model at
<https://community.apache.org/apache-way/apache-project-maturity-model.html>
+
+## Status of this document
+
+All open items are updated with the latest status.
+
+## 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 |
+| :------------------------- |
:----------------------------------------------------------- |
:----------------------------------------------------------- |
+| **Code** |
| |
+| CD10 | The project produces Open Source software, for
distribution to the public at no charge. | **YES.** The project source code is
[licensed](https://github.com/apache/incubator-dubbo/blob/master/LICENSE) under
the Apache License, version 2.0. |
+| CD20 | The project's code is easily discoverable and
publicly accessible. | **YES.** Linked from the
[website](http://dubbo.incubator.apache.org/), available via
[gitbox.apache.org](https://gitbox.apache.org/repos/asf) (searching Dubbo) and
[GitHub](https://github.com/search?q=org%3Aapache+dubbo&unscoped_q=dubbo). |
+| CD30 | The code can be built in a reproducible way
using widely available standard tools. | **YES.** <br>dubbo: the project uses
Apache Maven, and uses travis as the continuous integration tool, please find
the [how to build ](https://github.com/apache/incubator-dubbo#building)for more
information. <br>dubbo-spring-boot-project: The project uses Apache Maven, and
uses travis as the continuous integration tool, please check out [how to
build](https://github.com/apa [...]
+| CD40 | The full history of the project's code is
available via a source code control system, in a way that allows any released
version to be recreated. | **YES.** Using Git for source code, document, and
website. All the
[repositories](https://github.com/search?q=org%3Aapache+dubbo&unscoped_q=dubbo)
at Github, releases are cut from that repository. All releases are tagged. |
+| CD50 | The provenance of each line of code is
established via the source code control system, in a reliable way based on
strong authentication of the committer. When third-party contributions are
committed, commit messages provide reliable information about the code
provenance. | **YES.** The project uses the [git
repository](https://github.com/apache/incubator-dubbo), managed by Apache
Infra, ensuring provenance of each line of code to a committer. Third party co
[...]
+| **Licenses and Copyright** |
| |
+| LC10 | The code is released under the Apache License,
version 2.0. | **YES**. <br/>dubbo: Source releases clearly state
[license](https://github.com/apache/incubator-dubbo#license).
<br/>dubbo-spring-boot-starter: Source releases clearly state
[license](https://github.com/apache/incubator-dubbo-spring-boot-project#license).
<br/>dubbo-admin: Source releases clearly state
[license](https://github.com/apache/incubator-dubbo-admin#license). Convenience
binaries clea [...]
+| LC20 | Libraries that are mandatory dependencies of
the project's code do not create more restrictions than the Apache License
does.[3], [4] | **YES**. The list of mandatory dependencies have been reviewed
to contain approved licenses only. See below third party dependencies. |
+| LC30 | The libraries mentioned in LC20 are available
as Open Source software. | **YES**. All mandatory dependencies are available as
open source software. See below. |
+| LC40 | Committers are bound by an Individual
Contributor Agreement (the "Apache iCLA") that defines which code they are
allowed to commit and how they need to identify code that is not their own. |
**YES**. The project uses a repository managed by Apache Gitbox -- write access
requires an Apache account, which requires an ICLA on file. |
+| LC50 | The copyright ownership of everything that the
project produces is clearly defined and documented. | **YES.** All files in the
source repository have appropriate headers (see below).Even further, Software
Grant Agreements for the initial donations have been filed. |
+| **Releases** |
| |
+| 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
releases](https://dist.apache.org/repos/dist/release/incubator/dubbo/) are
distributed via [dist.apache.org](http://dist.apache.org/) and linked from the
[website](https://dubbo.incubator.apache.org/en-us/blog/download.html). |
+| RE20 | Releases are approved by the project's PMC (see
CS10), in order to make them an act of the Foundation. | **YES**. All
incubating releases have been unanimously approved by the Dubbo community and
the Incubator, all with at least 3 (P)PMC votes. |
+| RE30 | Releases are signed and/or distributed along
with digests that can be reliably used to validate the downloaded archives. |
**YES**. All releases are signed, and the [KEYS
file](https://dist.apache.org/repos/dist/release/incubator/dubbo/KEYS) is
provided on [dist.apache.org](http://dist.apache.org/). |
+| RE40 | Convenience binaries can be distributed
alongside source code but they are not Apache Releases -- they are just a
convenience provided with no guarantee. | **YES**. Convenience binaries are
distributed via [Maven Central
Repository](https://search.maven.org/search?q=g:org.apache.dubbo) and via
[dist.apache.org](https://dist.apache.org/repos/dist/release/incubator/dubbo/)
at the same time. |
+| RE50 | The release process is documented and
repeatable to the extent that someone new to the project is able to
independently generate the complete set of artifacts required for a release. |
**YES**. [Release
guide](https://dubbo.incubator.apache.org/en-us/docs/developers/committer-guide/release-guide_dev.html)
is available describing the entire process. The releases have been performed
by 7 different release managers. |
+| **Quality** |
| |
+| 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**.
The project records all bugs in the [Github
issue](https://github.com/apache/incubator-dubbo/issues). |
+| QU20 | The project puts a very high priority on
producing secure software. | **YES**. Security issues are treated with the
highest priority, according to the CVE/Security Advisory procedure. |
+| QU30 | The project provides a well-documented channel
to report security issues, along with a documented way of responding to them. |
**YES**. Website provides a dedicated page to describe how to report security
[issues](http://dubbo.apache.org/en-us/docs/developers/contributor-guide/reporting-security-issues_dev.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**. Each
release contains a “CHANGES” file on the GitHub containing the release notes .
Since 2.7.0, the package name has been renamed to org.apache.dubbo, the
community tries to minimized the issues introduced by package renaming, the
incompabilt changes are [well docu [...]
+| QU50 | The project strives to respond to documented
bug reports in a timely manner. | **YES**. The project has resolved [230+ pull
request](https://github.com/apache/incubator-dubbo-website/pulls) for website,
inculding documentation fix. And there are 92 contributors who help to improve
to the website. |
+| **Community** |
| |
+| CO10 | The project has a well-known homepage that
points to all the information required to operate according to this maturity
model. | **YES**. The project [website](https://dubbo.incubator.apache.org/)
has a description of the project with technical details, how to contribute,
team. |
+| CO20 | The community welcomes contributions from
anyone who acts in good faith and in a respectful manner and adds value to the
project. | **YES**. The [contribution
guide](https://dubbo.incubator.apache.org/en-us/docs/developers/contributor-guide/new-contributor-guide_dev.html)
is well documented and the current committers are keen to welcome
contributions. |
+| CO30 | Contributions include not only source code, but
also documentation, constructive bug reports, constructive discussions,
marketing and generally anything that adds value to the project. | **YES**. The
[contribution
guide](https://dubbo.incubator.apache.org/en-us/docs/developers/contributor-guide/new-contributor-guide_dev.html)
refers to non source code contribution, like documentation. |
+| CO40 | The community is meritocratic and over time
aims to give more rights and responsibilities to contributors who add value to
the project. | **YES**. The community has elected 18 new committers and 8 PPMC
members during incubation, based on meritocracy. |
+| CO50 | The way in which contributors can be granted
more rights such as commit access or decision power is clearly documented and
is the same for all contributors. | **YES**. The criteria is documented in the
[contribution
guide](http://dubbo.incubator.apache.org/en-us/docs/developers/contributor-guide/become-a-committer_dev.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**. The project works to build
consensus. All votes have been unanimous so far. |
+| CO70 | The project strives to answer user questions in
a timely manner. | **YES**. The project typically provides detailed answers to
user questions within a few hours via [mailing
list](https://lists.apache.org/[email protected]) and
GitHub [issues](https://github.com/apache/incubator-dubbo/issues) |
+| **Consensus Building** |
| |
+| 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**. The website contains the
[list of committers and PPMC
members](https://dubbo.incubator.apache.org/en-us/docs/developers/developers_dev.html).
|
+| CS20 | Decisions are made by consensus among PMC
members and are documented on the project's main communications channel.
Community opinions are taken into account but the PMC has the final word if
needed. | **YES**. The project has been making important decisions on the
project mailing lists. Vast majority of, if not all, decisions have had a
consensus without any PPMC action needed. |
+| CS30 | Documented voting rules are used to build
consensus when discussion is not sufficient. | **YES**. The project uses the
standard ASF voting rules. Voting rules are clearly stated before the voting
starts for each individual vote. |
+| CS40 | In Apache projects, vetoes are only valid for
code commits and are justified by a technical explanation, as per the Apache
voting rules defined in CS30. | **YES**. The project hasn’t used a veto at any
point and relies on robust code reviews. |
+| 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**. The project has been making important
decisions on the project mailing lists. Minor decisions may occasionally happen
during code reviews, which are also asynchronous and in written form. |
+| **Independence** |
| |
+| IN10 | The project is independent from any corporate
or organizational influence. | **YES**. The project team gathers people from
different companies (Alibaba, Weidian, Jingdong, Qunar, Youzan, Netease,
Meituan-Dianping, Rongguan, Handuyishe, Didi, NetsUnion, Caocaokeji, Huawei,
GomeFinance, Asiainfo-sec, iFlytek, Keep, and Lizhi FM). No company or
organization has significantly more influence than any other. We can note a
growth of the contributions coming from d [...]
+| IN20 | Contributors act as themselves as opposed to
representatives of a corporation or organization. | **YES**. The committers and
contributors act on their own initiative without representing a corporation or
organization. |
\ No newline at end of file
