Evaluate and populate "Consensus Building" section of maturity evaluation.
Project: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-website/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-website/commit/96b8457c Tree: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-website/tree/96b8457c Diff: http://git-wip-us.apache.org/repos/asf/incubator-guacamole-website/diff/96b8457c Branch: refs/heads/master Commit: 96b8457c9df5a5497e68dbc2b6bff3dc47e1d8e7 Parents: 864f6dc Author: Michael Jumper <[email protected]> Authored: Sun Oct 22 16:39:26 2017 -0700 Committer: Michael Jumper <[email protected]> Committed: Sun Oct 22 16:39:26 2017 -0700 ---------------------------------------------------------------------- maturity-evaluation.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-guacamole-website/blob/96b8457c/maturity-evaluation.md ---------------------------------------------------------------------- diff --git a/maturity-evaluation.md b/maturity-evaluation.md index 9328bb0..5340f9d 100644 --- a/maturity-evaluation.md +++ b/maturity-evaluation.md @@ -280,33 +280,38 @@ CS10 power -- the project's PMC (Project Management Committee) consists of those contributors. - ? + **OK:** This list is automatically produced by people.apache.org and can be + found at: <http://people.apache.org/committers-by-project.html#guacamole>. CS20 : 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. - ? + **OK:** All decisions affecting the project are made on the mailing lists + (see CO60) and are inherently documented through the mail archives. + Development itself is documented in JIRA. CS30 : Documented voting rules are used to build consensus when discussion is not sufficient. - ? + **OK:** Discussion has always been sufficient. If/when consensus cannot be + reached via discussion, voting is the next logical step. 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. - ? + **OK:** The project has never used vetoes. CS50 : 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. - ? + **OK:** All decisions affecting the project are made on the mailing lists + (see CO60). Independence ------------
