Apache Maturity Model Assessment

Mentors and community members are encouraged to contribute to this page and comment on it, the following table summarizes the project's self-assessment against the Apache Maturity Model.

ID	Description	Status
Code
CD10	The project produces Open Source software, for distribution to the public at no charge.	YES. Everything is hosted at the Apache Software Foundation Github
CD20	The project's code is easily discoverable and publicly accessible.	YES. Everything is hosted at the Apache Software Foundation
CD30	The code can be built in a reproducible way using widely available standard tools.	YES.
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. 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.	YES. Superset tracks code change using Github, all PRs required reviews by committers before changes are merged.
Licenses and Copyright
LC10	The code is released under the Apache License, version 2.0.	YES. See license
LC20	Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.[3], [4]	YES. See below OS dependencies, database dependencies
LC30	The libraries mentioned in LC20 are available as Open Source software.	YES. See below OS dependencies, database dependencies
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 registered iCLAs
LC50	The copyright ownership of everything that the project produces is clearly defined and documented.	YES. see details
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. 7 releases have been produced so far and have been reviewed by IPMCs within Apache structure
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 community and the Incubator.
RE30	Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.	YES. 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.	YES. see the releases here
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. The release process is documented here
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. The project records all bugs in the GitHub issues.
QU20	The project puts a very high priority on producing secure software.[7]	YES. 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.	YES. 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.	YES. This file includes all backward compatibility issues between different versions of Superset.
QU50	The project strives to respond to documented bug reports in a timely manner.	YES. The project uses github issues 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
CO10	The project has a well-known homepage that points to all the information required to operate according to this maturity model.	Our website contains information including technical details, installation, community contribution, security information, contribution guide that is required by ASF. All items on the apache poddling website checklist are checked. superset.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. The community welcomes all forms of contribution. Contribution guide is documented in github.
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. Please see the contribution guide page. The contribution guide page includes orientation, pull request guidelines and different types of contributions.
CO40	The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project.	YES. The community has elected 33 new committers and 21 PPMC members during incubation.
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 criteria is documented in the contribution guide.
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.	YES. The project typically provides detailed answers to user questions within a few hours via mailing list.
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. 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.	YES. All decisions, including adding new PPMC and committers, have been made via mailing list.
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 hasn’t used a veto at any point and relies on robust code reviews.
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. Minor decisions may occasionally happen during code reviews, which are also asynchronous and in written form.
Independence
IN10	The project is independent from any corporate or organizational influence.	YES. Superset originated from a donation by Airbnb, however it has strived to add external contributors and has now PPMC members that are mainly from 4 different companies (Preset, Airbnb, Lyft, Dropbox) and contributors from worldwide.
IN20	Contributors act as themselves as opposed to representatives of a corporation or organization.	YES. All Superset committers and contributors act on their own initiative without representing any corporation.