CD10: The project produces Open Source software, for distribution to the public at no charge.
Yes: https://druid.apache.org/downloads.html
CD20: The project's code is easily discoverable and publicly accessible.
Yes: https://github.com/apache/druid.
CD30: The code can be built in a reproducible way using widely available standard tools.
Yes, the code is built using Maven.
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.
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, provenance is verified as part of the pull request review process.
LC10: The code is released under the Apache License, version 2.0.
Yes.
LC20: Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does.
Yes.
LC30: The libraries mentioned in LC20 are available as Open Source software.
Yes.
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.
LC50: The copyright ownership of everything that the project produces is clearly defined and documented.
Yes, in our LICENSE and NOTICE files.
RE10: Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.
Yes.
RE20: Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation.
Yes.
RE30: Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.
Yes.
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.
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.
Partially, so this is an area we could improve in. There is some unwritten wisdom stored in the minds of previous release managers.
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. We clearly mark less mature areas of code with an 'experimental' label.
QU20: The project puts a very high priority on producing secure software.
Yes. Ever since adding a security layer to Druid in the past, we take seriously any issues that arise.
QU30: The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them.
No. Perhaps we should post up a notice saying security issues can be reported to private@druid.apache.org.
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. We have a policy that describes the contract with our users with regard to backwards compatibility, and document any incompatible changes in the release notes.
QU50: The project strives to respond to documented bug reports in a timely manner.
Yes.
CO10: The project has a well-known homepage that points to all the information required to operate according to this maturity model.
Yes: https://druid.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.
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.
CO40: The community strives to be meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project.
Yes.
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: https://druid.apache.org/community/
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.
CO70: The project strives to answer user questions in a timely manner.
Yes.
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.
We maintain a list of committers at: https://druid.apache.org/community/. After graduation we should add a PMC member list as well.
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.
CS30: Documented voting rules are used to build consensus when discussion is not sufficient.
Yes.
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.
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.
IN10: The project is independent from any corporate or organizational influence.
Yes.
IN20: Contributors act as themselves as opposed to representatives of a corporation or organization.
Yes, evidenced by the fact that we see robust discussion and even sometimes disagreement between contributors that are affiliated with the same outside organizations as each other.