...
| id | description (from maturity model) | evaluation | committers agreeing with evaluation |
|---|---|---|---|
| The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors. | Public list of contributors with decision power are available here:https http://githubincubator.com/orgs/apache.org/teamsprojects/airflow-committers/members.html | bolke |
| 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. | Decisions are documented in the dev mailing list, in JIRAs tracked in the Bugs link and on PRs on Github. | bolke |
| Documented voting rules are used to build consensus when discussion is not sufficient. | The Apache Airflow community fully accepts standard ASF voting rules as detailed here: https://www.apache.org/foundation/voting.html | bolke |
| 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. | Vetoes are only valid for code commits and are justified by a technical explanation | bolke |
| 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 in the documented communication channels, which is either the dev mailing list or in JIRAs. Any offline communication that happens is documented in those channels. | bolke |
...