This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-plc4x-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new b3bf180  Site checkin for project PLC4X: Jenkins Tools
b3bf180 is described below

commit b3bf1806c3e74d277d5777c4fc76aba02a8402e6
Author: jenkins <[email protected]>
AuthorDate: Wed Mar 20 11:59:59 2019 +0000

    Site checkin for project PLC4X: Jenkins Tools
---
 developers/maturity.html | 32 +++++++++++++++++---------------
 1 file changed, 17 insertions(+), 15 deletions(-)

diff --git a/developers/maturity.html b/developers/maturity.html
index 299a4ee..5a7102d 100644
--- a/developers/maturity.html
+++ b/developers/maturity.html
@@ -339,70 +339,72 @@
       <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
Bug reports are treated with priority and are automatically posted to our 
developer mailing list <a href="https://lists.apache.org/list.html?<a href=" 
mailto:[email protected]";>[email protected]</a>" 
class="bare"&gt;https://lists.apache.org/list.html?<a 
href="mailto:[email protected]";>[email protected]</a> so they are 
prominently recognised.</p></td> 
      </tr> 
      <tr> 
-      <td class="tableblock halign-left valign-top" colspan="3"><p 
class="tableblock"><strong>Community</strong></p></td> 
+      <td class="tableblock halign-left valign-top" colspan="2"><p 
class="tableblock"><strong>Community</strong></p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa 
fa-check"></i></span></p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CO10</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">The 
project has a well-known homepage that points to all the information required 
to operate according to this maturity model.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
The project website has a <a href="http://plc4x.apache.org/";>description of the 
project</a> with technical details, <a 
href="http://plc4x.apache.org/developers/contributing.html";>how to 
contribute</a>, <a 
href="http://plc4x.apache.org/developers/team.html";>team</a>.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CO20</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">The 
community welcomes contributions from anyone who acts in good faith and in a 
respectful manner and adds value to the project.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
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.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CO30</p></td> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">Contributions include not only source code, but also 
documentation, constructive bug reports, constructive discussions, marketing 
and generally anything that adds value to the project.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
It’s part of the <a 
href="http://plc4x.apache.org/developers/contributing.html";>contribution 
guide</a> and the current committers are really keen to welcome 
contributions.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CO40</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">The 
community is meritocratic and over time aims to give more rights and 
responsibilities to contributors who add value to the project.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
So far the community has elected 4 committers, all of them also being added to 
the PPMC.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CO50</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">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.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
The criteria is documented in the <a 
href="http://plc4x.apache.org/developers/contributing.html";>contribution 
guide</a>.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CO60</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">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.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
The project works to build consensus. All votes have been unanimous so 
far.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CO70</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">The 
project strives to answer user questions in a timely manner.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
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).</p></td> 
      </tr> 
      <tr> 
-      <td class="tableblock halign-left valign-top" colspan="3"><p 
class="tableblock"><strong>Consensus Building</strong></p></td> 
+      <td class="tableblock halign-left valign-top" colspan="2"><p 
class="tableblock"><strong>Consensus Building</strong></p></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon red"><i class="fa 
fa-times"></i></span></p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CS10</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">The 
project maintains a public list of its contributors who have decision power — 
the project’s PMC (Project Management Committee) consists of those 
contributors.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon yellow"><i class="fa 
fa-wrench"></i></span> We’re currently working on filling the <a 
href="http://plc4x.apache.org/developers/team.html";>team page</a>.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CS20</p></td> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">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.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
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.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CS30</p></td> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">Documented voting rules are used to build consensus when 
discussion is not sufficient.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
We have documented our decision making rule on our <a 
href="http://plc4x.apache.org/developers/decisions.html";>website</a>.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CS40</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">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.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon red"><i class="fa fa-times"></i></span> 
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 <a 
href="http://plc4x.apache.org/developers/decisions.html";>website</a>.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">CS50</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">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.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa fa-check"></i></span> 
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.</p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top" colspan="3"><p 
class="tableblock"><strong>Independence</strong></p></td> 
@@ -410,7 +412,7 @@
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">IN10</p></td> 
       <td class="tableblock halign-left valign-top"><p class="tableblock">The 
project is independent from any corporate or organizational influence.</p></td> 
-      <td class="tableblock halign-left valign-top"></td> 
+      <td class="tableblock halign-left valign-top"><p 
class="tableblock"><span class="icon green"><i class="fa 
fa-check"></i></span></p></td> 
      </tr> 
      <tr> 
       <td class="tableblock halign-left valign-top"><p 
class="tableblock">IN20</p></td> 

Reply via email to