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 4f33f8c NO JIRA - Continued documenting the apache maturity model
compliance.
4f33f8c is described below
commit 4f33f8ca2b43af5f55d34c5d5daf2b4efeeb2ebf
Author: Christofer Dutz <[email protected]>
AuthorDate: Wed Mar 20 11:52:30 2019 +0100
NO JIRA
- Continued documenting the apache maturity model compliance.
---
src/site/asciidoc/developers/maturity.adoc | 30 +++++++++++++++---------------
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/src/site/asciidoc/developers/maturity.adoc
b/src/site/asciidoc/developers/maturity.adoc
index 1193fdf..08b1b55 100644
--- a/src/site/asciidoc/developers/maturity.adoc
+++ b/src/site/asciidoc/developers/maturity.adoc
@@ -56,21 +56,21 @@ Mentors and community members are encouraged to contribute
to this page and comm
|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.
-3+|*Community*
-|CO10 |The project has a well-known homepage that points to all the
information required to operate according to this maturity model. |
-|CO20 |The community welcomes contributions from anyone who acts in good faith
and in a respectful manner and adds value to the project. |
-|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. |
-|CO40 |The community is meritocratic and over time aims to give more rights
and responsibilities to contributors who add value to the project. |
-|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. |
-|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. |
-|CO70 |The project strives to answer user questions in a timely manner. |
-3+|*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. |
-|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. |
-|CS30 |Documented voting rules are used to build consensus when discussion is
not sufficient. |
-|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. |
-|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. |
+2+|*Community* |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.
+|CO40 |The community is meritocratic and over time aims to give more rights
and responsibilities to contributors who add value to the project.
|icon:check[role=green] So far the community has elected 4 committers, all of
them also being added to the PPMC.
+|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]
+|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. |
+|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. |
|=========================================================
