You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@groovy.apache.org by bd...@apache.org on 2015/10/15 11:03:26 UTC

incubator-groovy git commit: Add document status section

Repository: incubator-groovy
Updated Branches:
  refs/heads/master 9161ff15c -> cb8904411


Add document status section


Project: http://git-wip-us.apache.org/repos/asf/incubator-groovy/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-groovy/commit/cb890441
Tree: http://git-wip-us.apache.org/repos/asf/incubator-groovy/tree/cb890441
Diff: http://git-wip-us.apache.org/repos/asf/incubator-groovy/diff/cb890441

Branch: refs/heads/master
Commit: cb89044119c815f6dfd8872ac0e1dcaa9c026da1
Parents: 9161ff1
Author: Bertrand Delacretaz <bd...@apache.org>
Authored: Thu Oct 15 11:03:20 2015 +0200
Committer: Bertrand Delacretaz <bd...@apache.org>
Committed: Thu Oct 15 11:03:20 2015 +0200

----------------------------------------------------------------------
 MATURITY.adoc | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-groovy/blob/cb890441/MATURITY.adoc
----------------------------------------------------------------------
diff --git a/MATURITY.adoc b/MATURITY.adoc
index 984085c..bf2849f 100644
--- a/MATURITY.adoc
+++ b/MATURITY.adoc
@@ -13,8 +13,12 @@ Maintaining such a file is a new, experimental idea as part of the continuous
 improvement of the ASF incubation process. Groovy is the first podling where 
 that happens.
 
+== Status of this document
+At this point this is just a skeleton with the maturity items spelled out but
+no detailed assessment.
+
 == Overall assessment
-Groovy looks ready to graduate, discussions are ongoing on the project's
+Groovy looks ready to graduate, discussions and votes are ongoing on the project's
 dev list as I write this (October 2015).
 
 == Maturity model assessment 
@@ -124,7 +128,7 @@ _Documented voting rules are used to build consensus when discussion is not suff
 _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._ 
+_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._ 
 
 === Independence