polygene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From paulmer...@apache.org
Subject svn commit: r1686056 - in /zest/site: content/atom.xml content/community/maturity.html src/community/maturity.html
Date Wed, 17 Jun 2015 15:55:06 GMT
Author: paulmerlin
Date: Wed Jun 17 15:55:06 2015
New Revision: 1686056

URL: http://svn.apache.org/r1686056
Log:
zest: maturity: replace YES/NO with green checks and red crosses

Modified:
    zest/site/content/atom.xml
    zest/site/content/community/maturity.html
    zest/site/src/community/maturity.html

Modified: zest/site/content/atom.xml
URL: http://svn.apache.org/viewvc/zest/site/content/atom.xml?rev=1686056&r1=1686055&r2=1686056&view=diff
==============================================================================
--- zest/site/content/atom.xml (original)
+++ zest/site/content/atom.xml Wed Jun 17 15:55:06 2015
@@ -4,7 +4,7 @@
  <title></title>
  <link href="http://zest.apache.org/atom.xml" rel="self"/>
  <link href="http://zest.apache.org"/>
- <updated>2015-06-17T15:09:02+02:00</updated>
+ <updated>2015-06-17T17:54:02+02:00</updated>
  <id>http://zest.apache.org</id>
  <author>
    <name></name>

Modified: zest/site/content/community/maturity.html
URL: http://svn.apache.org/viewvc/zest/site/content/community/maturity.html?rev=1686056&r1=1686055&r2=1686056&view=diff
==============================================================================
--- zest/site/content/community/maturity.html (original)
+++ zest/site/content/community/maturity.html Wed Jun 17 15:55:06 2015
@@ -114,165 +114,165 @@
                 <script type="text/javascript" src="http://www.ohloh.net/p/13150/widgets/project_factoids.js"></script>
             </div>
         </div>
-        <h3>CD10 - YES</h3>
+        <h3>CD10 <i class="icon-ok text-success"></i></h3>
         <p>
             The project produces Open Source software, for distribution to the public at
no charge.
         </p>
-        <h3>CD20  -  YES</h3>
+        <h3>CD20 <i class="icon-ok text-success"></i></h3>
         <p>
             The project's code is easily discoverable and publicly accessible. 
         </p>
-        <h3>CD30  -  YES</h3>
+        <h3>CD30 <i class="icon-ok text-success"></i></h3>
         <p>
             The code can be built in a reproducible way using widely available standard tools.

         </p>
-        <h3>CD40  -  YES</h3>
+        <h3>CD40 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>CD50  -  YES</h3>
+        <h3>CD50 <i class="icon-ok text-success"></i></h3>
         <p>
             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.
         </p>
-        <h3>LC10  -  YES</h3>
+        <h3>LC10 <i class="icon-ok text-success"></i></h3>
         <p>
             The code is released under the Apache License, version 2.0. 
         </p>
-        <h3>LC20  -  YES</h3>
+        <h3>LC20 <i class="icon-ok text-success"></i></h3>
         <p>
             Libraries that are mandatory dependencies of the project's code do not create
more 
             restrictions than the Apache License does. 
         </p>
-        <h3>LC30  -  YES</h3>
+        <h3>LC30 <i class="icon-ok text-success"></i></h3>
         <p>
             The libraries mentioned in LC20 are available as Open Source software. 
         </p>
-        <h3>LC40  -  YES</h3>
+        <h3>LC40 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>LC50  -  YES</h3>
+        <h3>LC50 <i class="icon-ok text-success"></i></h3>
         <p>
             The copyright ownership of everything that the project produces is clearly defined
and 
             documented.
         </p>
-        <h3>RE10  -  YES</h3>
+        <h3>RE10 <i class="icon-ok text-success"></i></h3>
         <p>
             Releases consist of source code, distributed using standard and open archive
formats that 
             are expected to stay readable in the long term.
         </p>
-        <h3>RE20  -  YES</h3>
+        <h3>RE20 <i class="icon-ok text-success"></i></h3>
         <p>
             Releases are approved by the project's PMC (see CS10), in order to make them
an act of 
             the Foundation. 
         </p>
-        <h3>RE30  -  YES</h3>
+        <h3>RE30 <i class="icon-ok text-success"></i></h3>
         <p>
             Releases are signed and/or distributed along with digests that can be reliably
used to 
             validate the downloaded archives. 
         </p>
-        <h3>RE40  -  YES</h3>
+        <h3>RE40 <i class="icon-ok text-success"></i></h3>
         <p>
             Convenience binaries can be distributed alongside source code but they are not
Apache 
             Releases -- they are just a convenience provided with no guarantee. 
         </p>
-        <h3>QU10  -  YES</h3>
+        <h3>QU10 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>QU20  -  YES</h3>
+        <h3>QU20 <i class="icon-ok text-success"></i></h3>
         <p>
             The project puts a very high priority on producing secure software.
         </p>
-        <h3>QU30  -  NO</h3>
+        <h3>QU30 <i class="icon-remove text-error"></i></h3>
         <p>
             The project provides a well-documented channel to report security issues, along
with a 
-            documented way of responding to them. 8 
+            documented way of responding to them.
         </p>
-        <h3>QU40  -  NO</h3>
+        <h3>QU40 <i class="icon-remove text-error"></i></h3>
         <p>
             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. 
         </p>
-        <h3>QU50  - YES</h3>
+        <h3>QU50 <i class="icon-ok text-success"></i></h3>
         <p>
             The project strives to respond to documented bug reports in a timely manner.

         </p>
-        <h3>CO10  -  NO</h3>
+        <h3>CO10 <i class="icon-remove text-error"></i></h3>
         <p>
             The project has a well-known homepage that points to all the information required
to operate 
             according to this maturity model. 
         </p>
-        <h3>CO20  -  YES</h3>
+        <h3>CO20 <i class="icon-ok text-success"></i></h3>
         <p>
             The community welcomes contributions from anyone who acts in good faith and in
a respectful 
             manner and adds value to the project. 
         </p>
-        <h3>CO30  -  YES</h3>
+        <h3>CO30 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CO40  -  YES</h3>
+        <h3>CO40 <i class="icon-ok text-success"></i></h3>
         <p>
             The community is meritocratic and over time aims to give more rights and responsibilities

             to contributors who add value to the project. 
         </p>
-        <h3>CO50  -  YES</h3>
+        <h3>CO50 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CO60  -  YES</h3>
+        <h3>CO60 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CO70  -  YES</h3>
+        <h3>CO70 <i class="icon-ok text-success"></i></h3>
         <p>
             The project strives to answer user questions in a timely manner. 
         </p>
-        <h3>CS10  -  NO</h3>
+        <h3>CS10 <i class="icon-remove text-error"></i></h3>
         <p>
             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>
-        <h3>CS20  -  YES</h3>
+        <h3>CS20 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>CS30  -  NO</h3>
+        <h3>CS30 <i class="icon-remove text-error"></i></h3>
         <p>
             Documented voting rules are used to build consensus when discussion is not sufficient.
         </p>
-        <h3>CS40  -  YES</h3>
+        <h3>CS40 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CS50  -  YES</h3>
+        <h3>CS50 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>IN10  -  YES</h3>
+        <h3>IN10 <i class="icon-ok text-success"></i></h3>
         <p>
             The project is independent from any corporate or organizational influence.
         </p>
-        <h3>IN20  -  YES</h3>
+        <h3>IN20 <i class="icon-ok text-success"></i></h3>
         <p>
             Contributors act as themselves as opposed to representatives of a corporation
or organization. 
         </p>

Modified: zest/site/src/community/maturity.html
URL: http://svn.apache.org/viewvc/zest/site/src/community/maturity.html?rev=1686056&r1=1686055&r2=1686056&view=diff
==============================================================================
--- zest/site/src/community/maturity.html (original)
+++ zest/site/src/community/maturity.html Wed Jun 17 15:55:06 2015
@@ -19,165 +19,165 @@ layout: default
                 <script type="text/javascript" src="http://www.ohloh.net/p/13150/widgets/project_factoids.js"></script>
             </div>
         </div>
-        <h3>CD10 - YES</h3>
+        <h3>CD10 <i class="icon-ok text-success"></i></h3>
         <p>
             The project produces Open Source software, for distribution to the public at
no charge.
         </p>
-        <h3>CD20  -  YES</h3>
+        <h3>CD20 <i class="icon-ok text-success"></i></h3>
         <p>
             The project's code is easily discoverable and publicly accessible. 
         </p>
-        <h3>CD30  -  YES</h3>
+        <h3>CD30 <i class="icon-ok text-success"></i></h3>
         <p>
             The code can be built in a reproducible way using widely available standard tools.

         </p>
-        <h3>CD40  -  YES</h3>
+        <h3>CD40 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>CD50  -  YES</h3>
+        <h3>CD50 <i class="icon-ok text-success"></i></h3>
         <p>
             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.
         </p>
-        <h3>LC10  -  YES</h3>
+        <h3>LC10 <i class="icon-ok text-success"></i></h3>
         <p>
             The code is released under the Apache License, version 2.0. 
         </p>
-        <h3>LC20  -  YES</h3>
+        <h3>LC20 <i class="icon-ok text-success"></i></h3>
         <p>
             Libraries that are mandatory dependencies of the project's code do not create
more 
             restrictions than the Apache License does. 
         </p>
-        <h3>LC30  -  YES</h3>
+        <h3>LC30 <i class="icon-ok text-success"></i></h3>
         <p>
             The libraries mentioned in LC20 are available as Open Source software. 
         </p>
-        <h3>LC40  -  YES</h3>
+        <h3>LC40 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>LC50  -  YES</h3>
+        <h3>LC50 <i class="icon-ok text-success"></i></h3>
         <p>
             The copyright ownership of everything that the project produces is clearly defined
and 
             documented.
         </p>
-        <h3>RE10  -  YES</h3>
+        <h3>RE10 <i class="icon-ok text-success"></i></h3>
         <p>
             Releases consist of source code, distributed using standard and open archive
formats that 
             are expected to stay readable in the long term.
         </p>
-        <h3>RE20  -  YES</h3>
+        <h3>RE20 <i class="icon-ok text-success"></i></h3>
         <p>
             Releases are approved by the project's PMC (see CS10), in order to make them
an act of 
             the Foundation. 
         </p>
-        <h3>RE30  -  YES</h3>
+        <h3>RE30 <i class="icon-ok text-success"></i></h3>
         <p>
             Releases are signed and/or distributed along with digests that can be reliably
used to 
             validate the downloaded archives. 
         </p>
-        <h3>RE40  -  YES</h3>
+        <h3>RE40 <i class="icon-ok text-success"></i></h3>
         <p>
             Convenience binaries can be distributed alongside source code but they are not
Apache 
             Releases -- they are just a convenience provided with no guarantee. 
         </p>
-        <h3>QU10  -  YES</h3>
+        <h3>QU10 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>QU20  -  YES</h3>
+        <h3>QU20 <i class="icon-ok text-success"></i></h3>
         <p>
             The project puts a very high priority on producing secure software.
         </p>
-        <h3>QU30  -  NO</h3>
+        <h3>QU30 <i class="icon-remove text-error"></i></h3>
         <p>
             The project provides a well-documented channel to report security issues, along
with a 
-            documented way of responding to them. 8 
+            documented way of responding to them.
         </p>
-        <h3>QU40  -  NO</h3>
+        <h3>QU40 <i class="icon-remove text-error"></i></h3>
         <p>
             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. 
         </p>
-        <h3>QU50  - YES</h3>
+        <h3>QU50 <i class="icon-ok text-success"></i></h3>
         <p>
             The project strives to respond to documented bug reports in a timely manner.

         </p>
-        <h3>CO10  -  NO</h3>
+        <h3>CO10 <i class="icon-remove text-error"></i></h3>
         <p>
             The project has a well-known homepage that points to all the information required
to operate 
             according to this maturity model. 
         </p>
-        <h3>CO20  -  YES</h3>
+        <h3>CO20 <i class="icon-ok text-success"></i></h3>
         <p>
             The community welcomes contributions from anyone who acts in good faith and in
a respectful 
             manner and adds value to the project. 
         </p>
-        <h3>CO30  -  YES</h3>
+        <h3>CO30 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CO40  -  YES</h3>
+        <h3>CO40 <i class="icon-ok text-success"></i></h3>
         <p>
             The community is meritocratic and over time aims to give more rights and responsibilities

             to contributors who add value to the project. 
         </p>
-        <h3>CO50  -  YES</h3>
+        <h3>CO50 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CO60  -  YES</h3>
+        <h3>CO60 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CO70  -  YES</h3>
+        <h3>CO70 <i class="icon-ok text-success"></i></h3>
         <p>
             The project strives to answer user questions in a timely manner. 
         </p>
-        <h3>CS10  -  NO</h3>
+        <h3>CS10 <i class="icon-remove text-error"></i></h3>
         <p>
             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>
-        <h3>CS20  -  YES</h3>
+        <h3>CS20 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>CS30  -  NO</h3>
+        <h3>CS30 <i class="icon-remove text-error"></i></h3>
         <p>
             Documented voting rules are used to build consensus when discussion is not sufficient.
         </p>
-        <h3>CS40  -  YES</h3>
+        <h3>CS40 <i class="icon-ok text-success"></i></h3>
         <p>
             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>
-        <h3>CS50  -  YES</h3>
+        <h3>CS50 <i class="icon-ok text-success"></i></h3>
         <p>
             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. 
         </p>
-        <h3>IN10  -  YES</h3>
+        <h3>IN10 <i class="icon-ok text-success"></i></h3>
         <p>
             The project is independent from any corporate or organizational influence.
         </p>
-        <h3>IN20  -  YES</h3>
+        <h3>IN20 <i class="icon-ok text-success"></i></h3>
         <p>
             Contributors act as themselves as opposed to representatives of a corporation
or organization. 
         </p>



Mime
View raw message