Unomi Podling Maturity Assessment

Overview

This is an assessment of the Unomi podling’s maturity, meant to help inform the decision (of the mentors, community, Incubator PMC and ASF Board of Directors) to graduate it as a top-level Apache project. It is based on the ASF project maturity model at https://community.apache.org/apache-way/apache-project-maturity-model.html Maintaining such a file is a new, experimental idea as part of the continuous improvement of the ASF incubation process.

Status of this document

Updated 2018-10-09 with the latest status of the project.

Overall assessment

Just introduced this report card, we will need to evaluate all the model’s parts to see how we fare so far.

Maturity model assessment

Mentors and community members are encouraged to contribute to this and comment on it.

Code

Code	Description	Status	Comment
CD10	The project produces Open Source software, for distribution to the public at no charge.		everything is hosted at the Apache Software Foundation
CD10	The project produces Open Source software, for distribution to the public at no charge.		everything is hosted at the Apache Software Foundation
CD20	The project’s code is easily discoverable and publicly accessible.		it is linked from the main project site and accessible in the public ASF git repository
CD30	The code can be built in a reproducible way using widely available standard tools.		Apache Unomi can be built with Apache Maven in the usual way, using "mvn clean install" from the root of the project.
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.		everything is in the ASF Git repository.
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.		Only ASF committers with CLAs may contribute to the project.

License and Copyright

Code	Description	Status	Comment
LC10	The code is released under the Apache License, version 2.0.		A LICENSE file is also at the root of the ASF Git repository
LC20	Libraries that are mandatory dependencies of the project’s code do not create more restrictions than the Apache License does.		NOTICE files contain all the information and has been reviewed on two releases already
LC30	The libraries mentioned in LC20 are available as Open Source software.		See LC20
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.		All committers have registered iCLAs
LC50	The copyright ownership of everything that the project produces is clearly defined and documented.		NOTICE file is up-to-date with all copyright ownership.

Releases

Code	Description	Status	Comment
RE10	Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.		Three major releases have been produced so far and have been reviewed by IPMCs
RE20	Releases are approved by the project’s PMC (see CS10), in order to make them an act of the Foundation.		Happened for three major releases already
RE30	Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.		See the releases here
RE40	Convenience binaries can be distributed alongside source code but they are not Apache Releases – they are just a convenience provided with no guarantee.		See the releases here

Quality

Code	Description	Status	Comment
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.		The project's quality is tracked through Apache's JIRA issue tracking system, and is released regularly to improve both overall quality as well as performance.
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 channel to report security issues, along with a documented way of responding to them.		The website provides a link to the ASF security information.
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.		The project exposes an API that is specified by an OASIS standard. Also, for APIs outside of the specification, compatibility is a major focus but if not always possible, deprecations and migration documents are produced.
QU50	The project strives to respond to documented bug reports in a timely manner.		The project uses Apache's JIRA platform to handle bugs as well as any other types of issues reported on it. A focus is put on making sure that issues are responded to swiftly.

Community

Code	Description	Status	Comment
CO10	The project has a well-known homepage that points to all the information required to operate according to this maturity model.		See the project’s home page that includes a contribute section that describes how to become a committer as well as several documents for on-board newcomers quickly
CO20	The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project.		This is a part of the contribution guide. Here is an example of a recent addition of a committer and the way he was welcome, e.g., this
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.		The contribution guide specifically calls out many avenues for contribution. Specifically, several contributors have contributed documentation or bug fixes.
CO40	The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project.		A specific "become a contributor" page is publicly available that describes the process of how to gain more rights and responsibilities
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.		Again, the same "become a contributor" page contains all this information.
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.		The project works to build consensus. All votes have been unanimous so far. Usually a discussion happens before a vote on a technical or release issue, so the voting process is rarely a problem. Also, in the become a contributor page, a code of conduct is put in place to ensure contributors have a reference to it.
CO70	The project strives to answer user questions in a timely manner.		The project typically provides detailed answers to user questions within a few hours via its users@ mailing list.

Consensus Building

Code	Description	Status	Comment
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.		The project has a team page that lists all the contributors along with their associated roles.
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.		PPMC decisions have been unonimous so far, including voting new committers and new PPMC members. The project has been making important decisions on the project mailing lists. All community decisions have had a consensus without any PPMC action needed.
CS30	Documented voting rules are used to build consensus when discussion is not sufficient.		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.		The project hasn’t used a veto at any point and relies on robust code reviews, especially for any issues around licenses problems.
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.		The project has been making important decisions on the project mailing lists. When communication occurs on side channels (Slack, face-to-face mostly), the mailing list is always used to communicate important information to the community.

Independence

Code	Description	Status	Comment
IN10	The project is independent from any corporate or organizational influence.		Although the project originated from a donation by a single corporate entity, it has strived to add external contributors and has now PPMC members that are part of 4 different corporations (Adobe, Talend, Yupiik, Jahia) and some contributors have also moved on to new corporations.
IN20	Contributors act as themselves as opposed to representatives of a corporation or organization.		The project has experienced PPMC members that will make sure that contributors will be acting freely as individuals.