This is an automated email from the ASF dual-hosted git repository.
cdutz pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/incubator-plc4x.git
The following commit(s) were added to refs/heads/develop by this push:
new 1a7a853 NO JIRA - Finished the maturity page ...
1a7a853 is described below
commit 1a7a853fb33440af0a2650c79a38ea40ecd86fa7
Author: Christofer Dutz <[email protected]>
AuthorDate: Wed Mar 20 13:28:35 2019 +0100
NO JIRA
- Finished the maturity page ...
---
src/site/asciidoc/developers/maturity.adoc | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/src/site/asciidoc/developers/maturity.adoc
b/src/site/asciidoc/developers/maturity.adoc
index 08b1b55..51ae0c9 100644
--- a/src/site/asciidoc/developers/maturity.adoc
+++ b/src/site/asciidoc/developers/maturity.adoc
@@ -32,31 +32,31 @@ Mentors and community members are encouraged to contribute
to this page and comm
[width="100%",options="header"]
|=========================================================
|ID |Description |Status
-2+|*Code* |icon:check[role=green]
+|*Code* 2+|icon:check[role=green]
|CD10 |The project produces Open Source software, for distribution to the
public at no charge. |icon:check[role=green] The project source code is
licensed under the Apache License, version 2.0.
|CD20 |The project's code is easily discoverable and publicly accessible.
|icon:check[role=green] Our sourcecode is available at
https://gitbox.apache.org/repos/asf/incubator-plc4x.git[Apache GitBox] and
https://github.com/apache/incubator-plc4x[GitHub] and linked to from our
https://plc4x.apache.org/scm.html[website]
|CD30 |The code can be built in a reproducible way using widely available
standard tools. |icon:check[role=green] our https://maven.apache.org[Maven]
build has been tested on Linux, MacOS and Windows and build description is
available on our https://plc4x.apache.org/developers/building.html[website]
|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.
|icon:check[role=green] The entire commit history is available from the
https://gitbox.apache.org/repos/asf?p=incubator-plc4x.git;a=commit;h=dd1fcf4649107762e91f7c494a10e55319a18785[beginning].
|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. |icon:check[role=green]
The project uses the git repository, managed by Apache Infra, ensuring
provenance of each line of code to a committer, each line committed before
entering incubation was equally configured.
-2+|*Licenses and Copyright* |icon:check[role=green]
+|*Licenses and Copyright* 2+|icon:check[role=green]
|LC10 |The code is released under the Apache License, version 2.0.
|icon:check[role=green] Both the source distribution as well as the convenience
binary artifacts clearly declare that they are licensed under the Apache 2.0
license
|LC20 |Libraries that are mandatory dependencies of the project's code do not
create more restrictions than the Apache License does. |icon:check[role=green]
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.
|icon:check[role=green] All mandatory dependencies are available as open source
software.
|LC40 |Committers are bound by an Individual Contributor Agreement (the
http://www.apache.org/licenses/icla.txt["Apache iCLA"]) that defines which code
they are allowed to commit and how they need to identify code that is not their
own. |icon:check[role=green] 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. |All files in the source repository have
appropriate headers which is enforced by tooling included in the build. ICLAs
from all initial committers have been documented. CCLAs from all companies
involved have been documented. SGA is on file for the initial contribution.
-2+|*Releases* |icon:wrench[role=yellow]
+|*Releases* 2+|icon:wrench[role=yellow]
|RE10 |Releases consist of source code, distributed using standard and open
archive formats that are expected to stay readable in the long term.
|icon:check[role=green]
https://dist.apache.org/repos/dist/release/incubator/plc4x/[Current source
releases] are distributed via dist.apache.org and
http://archive.apache.org/dist/incubator/plc4x/[Older source releases] are
available from archive.apache.org. Both are linked from the
http://plc4x.apache.org/users/download.html[website].
|RE20 |Releases are approved by the project's PMC (see CS10), in order to make
them an act of the Foundation. |icon:check[role=green] All incubating releases
have been unanimously approved by the PLC4X 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 can be
reliably used to validate the downloaded archives. |icon:check[role=green] All
releases are signed, and the
https://dist.apache.org/repos/dist/release/incubator/plc4x/KEYS[KEYS] file is
provided on 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. |icon:wrench[role=yellow] Convenience binaries are distributed via
Maven Central Repository only. Currently due to the platform-dependency of C++
libraries, these are not distributed currently.
|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. |icon:check[role=green] We have a guide
for release managers, that has been tested by multiple release managers
available on our http://plc4x.apache.org/developers/release.html[website].
-2+|*Quality* |icon:check[role=green]
+|*Quality* 2+|icon:check[role=green]
|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. |icon:check[role=green] All issues
are documented in our https://issues.apache.org/jira/projects/PLC4X[JIRA]
instance, which is our primary bug and issue tracker.
|QU20 |The project puts a very high priority on producing secure software.
|icon:check[role=green] even if we haven't received any security issues
targeted at PLC4X yet, we pro-actively monitor our dependencies and if reported
would treat them with the highest priority, according to the
https://www.apache.org/security/committers.html[CVE/Security Advisory
procedure].
|QU30 |The project provides a well-documented, secure and private channel to
report security issues, along with a documented way of responding to them.
|icon:check[role=green] We are using Apaches default way to submit security
related information, which is described on our
http://plc4x.apache.org/users/security.html[website]
|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. |icon:check[role=green] We try to keep
everything as backward compatible as possible. If we are forced to introduce
incompatible changes, these is documented in a `Incompatible changes` section
as part of our release notes.
|QU50 |The project strives to respond to documented bug reports in a timely
manner. |icon:check[role=green] Bug reports are treated with priority and are
automatically posted to our developer mailing list
https://lists.apache.org/[email protected] so they are
prominently recognised.
-2+|*Community* |icon:check[role=green]
+|*Community* 2+|icon:check[role=green]
|CO10 |The project has a well-known homepage that points to all the
information required to operate according to this maturity model.
|icon:check[role=green] The project website has a
http://plc4x.apache.org/[description of the project] with technical details,
http://plc4x.apache.org/developers/contributing.html[how to contribute],
http://plc4x.apache.org/developers/team.html[team].
|CO20 |The community welcomes contributions from anyone who acts in good faith
and in a respectful manner and adds value to the project.
|icon:check[role=green] So far we have recognized any form of contribution and
every contributor with the desire to become part of the team has been invited
to join.
|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. |icon:check[role=green] It’s part of
the http://plc4x.apache.org/developers/contributing.html[contribution guide]
and the current committers are really keen to welcome contributions.
@@ -64,13 +64,13 @@ Mentors and community members are encouraged to contribute
to this page and comm
|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. |icon:check[role=green] The criteria is documented in the
http://plc4x.apache.org/developers/contributing.html[contribution guide].
|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. |icon:check[role=green] 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.
|icon:check[role=green] Responses to reported issues or asked questions
typically are handled by the community withing a matter of a few hours
(Responses being faster during typical European time-zone business-hours).
-2+|*Consensus Building* |icon:times[role=red]
+|*Consensus Building* 2+|icon:times[role=red]
|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. |icon:wrench[role=yellow] We're currently working on
filling the http://plc4x.apache.org/developers/team.html[team page].
|CS20 |Decisions are made by consensus among PMC members 9 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. |icon:check[role=green] All
decisions are made on one of our mailing lists. Every decision discussed
off-list has been taken back to the list for final discussion and we'll keep on
doing that.
|CS30 |Documented voting rules are used to build consensus when discussion is
not sufficient. |icon:check[role=green] We have documented our decision making
rule on our http://plc4x.apache.org/developers/decisions.html[website].
|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. |icon:times[role=red] This part actively contradicts the voting rules of
the Apache Incubator. This project follows the voting rules of the Apache
Incubator which we documented on our
http://plc4x.apache.org/developers/decisions.html[website].
|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.
|icon:check[role=green] As mentioned in CS20 it is impossible to prevent
off-list discussions when meeting in person. But we have always handled things
in a way that we always write up summaries of important discussions and post
them to the mailing lists.
-3+|*Independence*
-|IN10 |The project is independent from any corporate or organizational
influence. |icon:check[role=green]
-|IN20 |Contributors act as themselves as opposed to representatives of a
corporation or organization. |
+|*Independence* 2+|icon:check[role=green]
+|IN10 |The project is independent from any corporate or organizational
influence. |icon:check[role=green] The group of active committers and PPMCs
consists of members of more than independent 4 companies.
+|IN20 |Contributors act as themselves as opposed to representatives of a
corporation or organization. |icon:check[role=green] While there are several
cases where committers and PPMC members utilize corporate infrastructure or
these companies, no case has been found where any of these committers and PPMCs
have represented corporate interests.
|=========================================================
