-
Notifications
You must be signed in to change notification settings - Fork 56
Apache Maturity Model Assessment for DataLab
This is an assessment of the DataLab 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.
All open items are updated with the latest status.
The project produces Open Source software, for distribution to the public at no charge.
Yes. The project source code is licensed under the Apache License, version 2.0
The project's code is easily discoverable and publicly accessible.
Yes. Visit download in our website. On top of that it's available in GitHub.
The code can be built in a reproducible way using widely available standard tools.
Yes. Building instructions can be found in the readme in GitHub.
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.
- We use GitHub for source code, documents, and the website.
- All the releases are cut from the respective repository.
- All releases are tagged.
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.
- The project uses the git repository, managed by Apache Infra, ensuring provenance of each line of code to a committer.
- Third party contributions are accepted in accordance with the Apache Third-Party Licensing Policy only.
The code is released under the Apache License, version 2.0.
Yes.
- See license.
- All source code files have license headers.
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 has been reviewed to contain approved licenses only.
The libraries mentioned in LC20 are available as Open Source software.
Yes. All mandatory dependencies are available as open source software.
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. The project uses a repository managed by Apache under GitHub. So write access requires an Apache account, which requires an ICLA on file.
The copyright ownership of everything that the project produces is clearly defined and documented.
Yes.
- All files in the source repository have appropriate headers.
- Software Grant Agreements for the initial donations and Corporate CLAs have been filed.
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 Apache Download Mirrors and linked from the website download page.
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 DataLab community, PPMC, and the IPMC, all with at least 3 IPMC votes.
Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.
Yes. All releases are signed, and key file are provided on dist.apache.org.
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 distributed via GitHub Repository and via dist.apache.org at the same time.
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.
- All GitHub users have access to detailed release script.
- As of December 1, 2020, we have successfully completed 4 Apache releases since the start of our incubation.
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 Jira tickets.
The project puts a very high priority on producing secure software.
Yes. Security issues are treated with the highest priority, according to the CVE/Security Advisory procedure.
The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them.
Yes. See https://datalab.incubator.apache.org/#community.
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 aim do not to make backward incompatible changes within a given major version. For incompatible changes in two major versions, clear documentation states the changes and how to immigrate to new versions.
The project strives to respond to documented bug reports in a timely manner.
Yes. We respond ASAP to issue reports. So as a result we've received superb feedback from our data-scientist users concerning our fast reply.
The project has a well-known homepage that points to all the information required to operate according to this maturity model.
Yes. Visit website.
The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project.
Yes. See https://datalab.incubator.apache.org/#community.
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. See https://datalab.incubator.apache.org/#community.
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. Based on meritocracy we've elected 8 committers and 2 PPMC members during incubation.
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. See https://datalab.incubator.apache.org/#community.
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. We've been working to build consensus.
The project strives to answer user questions in a timely manner.
Yes. In general we answer as soon as possible. For communication users can use diverse channels, see https://datalab.incubator.apache.org/#community.
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. See project status.
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. Major project decisions have been documented via our [email protected] mail list.
Documented voting rules are used to build consensus when discussion is not sufficient.
Yes. We use the standard ASF voting rules. Voting rules are clearly stated before the voting starts for each individual vote.
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. We have had "-1" votes from two Mentors and from one IPMC member on a code release. The issues were fixed and resubmitted. We support this policy.
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. We have made important decisions on the project mailing lists. Minor decisions may occasionally happen during code reviews, which are also asynchronous and in written form.
The project is independent from any corporate or organizational influence.
Yes. Our project has committers and contributors from EPAM Systems, Newfire Global Partners, Grid Dynamics, OFM Cap, and other researchers and engineers.
Contributors act as themselves as opposed to representatives of a corporation or organization.
Yes. The committers and contributors act on their own initiative without representing a corporation or organization.