THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Project maturity evaluation for Apache Rya based on the Apache Project Maturity Model
| Id | Description (from maturity model) | Assessment | Committers agreeing with assessment |
|---|---|---|---|
| Code | |||
| CD10 | The project produces Open Source software, for distribution to the public at no charge. | YES. Project source code is licensed under Apache License version 2.0 | adina |
| CD20 | The project's code is easily discoverable and publicly accessible. | YES. Search for "Apache Rya" easily finds the website https://rya.apache.org/ and GitHub mirror https://github.com/apache/incubator-rya | adina |
| CD30 | The code can be built in a reproducible way using widely available standard tools. | YES. Maven is used to build Rya. Instructions for building the code can be found at https://github.com/apache/incubator-rya | adina |
| CD40 | 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. | YES. Using Git, repository available at https://git-wip-us.apache.org/repos/asf?p=incubator-rya.git. All releases are tagged. | adina |
| CD50 | 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. | YES. Established via the git commit history. https://github.com/apache/incubator-rya | adina |
| Licenses and Copyright | |||
| LC10 | The code is released under the Apache License, version 2.0. | YES. Source distributions clearly state Apache License, version 2.0 https://github.com/apache/incubator-rya/blob/master/LICENSE | adina |
| LC20 | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | YES. The list of mandatory dependencies have been reviewed to have approved licenses only. | adina |
| LC30 | The libraries mentioned in LC20 are available as Open Source software. | YES. All mandatory dependencies are available as Open Source software. | adina |
| LC40 | 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. | YES. All committers have an ICLA on file. | adina |
| LC50 | The copyright ownership of everything that the project produces is clearly defined and documented. | YES. All appropriate files in the source repository have Apache License v2.0 headers. Software Grant Agreement for the initial donations and Corporate CLAs have been filed. | adina |
| Releases | |||
| RE10 | Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. | YES. Source releases are distributed via http://www.apache.org/dyn/closer.lua/incubator/rya/ and linked from the project website https://rya.apache.org/download/ | adina |
| RE20 | Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation. | YES. All incubating releases have been approved by the Rya community and Incubator, with at least three Incubator PMC votes. | adina |
| RE30 | Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives. | YES. Releases are signed with a committer key, public pgp keys being available in KEYS file. Digests are available at https://www.apache.org/dist/incubator/rya/. | adina |
| RE40 | Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee. | YES. Convenience binaries are only distributed via Maven Central https://search.maven.org/search?q=g:org.apache.rya | adina |
| RE50 | The release process is documented and repeatable to the extent that someone new to the project is able to independently generate the complete set of artifacts required for a release. | YES. Release process is documented on Rya Confluence at How To Release Rya. Rya releases have been performed by three different release managers. | adina |
| 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. | ||
| QU20 | The project puts a very high priority on producing secure software. | ||
| QU30 | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | ||
| 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. | ||
| QU50 | The project strives to respond to documented bug reports in a timely manner. | ||
| Community | |||
| CO10 | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | ||
| CO20 | The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. | ||
| 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. | ||
| CO40 | The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. | ||
| 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. | ||
| 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. | ||
| CO70 | The project strives to answer user questions in a timely manner. | ||
| 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. | ||
| 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. | ||
| CS30 | Documented voting rules are used to build consensus when discussion is not sufficient. | ||
| 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. | ||
| 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. | ||
| Independence | |||
| IN10 | The project is independent from any corporate or organizational influence. | ||
| IN20 | Contributors act as themselves as opposed to representatives of a corporation or organization. | ||