|
Quality |
QU10
| 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. | YES. All bugs are recorded in Apache's JIRA issue tracker at https://issues.apache.org/jira/browse/RYA.
|
QU20 | The project puts a very high priority on producing secure software. | Security issues are treated with the highest priority. |
QU30 | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | We follow the generic Apache way of handling security issues. Per https://www.apache.org/security/ and https://www.apache.org/security/committers.html |
QU40 | 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. | YES. Release notes describe changes made by that release (extracted for Jira). The project aims to make no backward incompatible changes within a given major version. |
QU50 | The project strives to respond to documented bug reports in a timely manner. | 101 out of 163 JIRA bug reports have been closed. |
Community |
CO10 | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | YES. https://rya.apache.org |
CO20 | The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. | YES. Allcontributions are welcome and discussions on the mailing lists are courteous. |
CO30 | Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project. | YES. The "Get involved" section on the website welcomes contributions in any category https://rya.apache.org/community/. More details are are provided in contributor guide |
CO40 | The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. | YES. Two new committers and PPMC members have been added during incubation, based on meritocracy. |
CO50 | 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. | YES. The contributor guide includes how to become a committer. |
CO60 | 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. | YES. The project works to build consensus. All votes have been unanimous so far. |
CO70 | The project strives to answer user questions in a timely manner. | Most questions are answered within a couple of days. |
Consensus Building |
CS10 | The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors. | YES. https://rya.apache.org/community-members/ lists the committers. All committers are part of the PPMC. Rya project incubation status file at http://incubator.apache.org/projects/rya.html also lists all committers |
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. | YES. Mailing lists are used for discussions and decision making. |
CS30 | Documented voting rules are used to build consensus when discussion is not sufficient. | YES. The project uses the standard ASF voting rules. Voting rules are clearly stated before the voting starts for each individual vote. |
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. | YES. The project did not use a veto so far. |
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. | YES. The project has been making important decisions on the project mailing lists. Synchronous discussions ("Rya office hours") were documented back on the dev mailing list. |
Independence |
IN10 | The project is independent from any corporate or organizational influence. | YES. The project team gathers people from different companies. |
IN20 | Contributors act as themselves as opposed to representatives of a corporation or organization. | YES. The committers and contributors act as themselves not as representatives of their organization. |
|
|
|