Overview
This is an assessment of the StreamPipes 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
Status of this document
2020-17-04. Initial assessment.
2020-08-17. Updated assessment, added open issues
2021-10-07. Added logo and provided numbers for PPMC diversity.
2022-03-16. Updated PPMC diversity and contribution guide
2022-10-21. Update note on code quality & backwards compatibility.
Maturity model assessment
Mentors and community members are encouraged to contribute to this page and comment on it, the following table summarizes project’s self-assessment against the Apache Maturity Model.
CODE
| CD10 | 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 2.0. |
| CD20 | The project's code is easily discoverable and publicly accessible. | YES. The website includes links to the Github repos. |
| CD30 | The code can be built in a reproducible way using widely available standard tools. | YES. The project uses Maven to build the Java-based projects and NPM to build the StreamPipes UI. The documentation at https://streampipes.apache.org and the README file contain information on how to build StreamPipes. The confluent wiki includes information on how to start a development instance: Test StreamPipes. |
| 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. The project uses Git to manage source code, documentation and website. Previous non-Apache-releases are tagged and clearly marked as pre-asf versions. |
| 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. The project uses GitHub, belongs to the apache group on Github, and it is ensuring provenance of each line of code to a committer. The wiki contains various onboarding guides. for committers, PPMC members and release managers. |
Licenses and Copyright
| LC10 | The code is released under the Apache License, version 2.0. | YES. License files are present in all Github repositories related to StreamPipes. |
| LC20 | Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. | YES. All dependencies have been reviewed to be compliant to the Apache License and are listed in the LICENSE-binary file. |
| LC30 | The libraries mentioned in LC20 are available as Open Source software. | YES. Yes, see above. |
| 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 current committers have signed an ICLA with the ASF. |
| LC50 | The copyright ownership of everything that the project produces is clearly defined and documented. | YES. All files in the source code have appropriate headers, which is also checked by the build system upon every commit. |
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. Releases are available at: |
| RE20 | Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation. | YES. The Apache StreamPipes (incubating) releases were approved by an Incubator PPMC vot e and a following binding IPMC vote. |
| RE30 | Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives. | YES. Releases are signed and release keys are also provided on the download page: |
| 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 libraries are published to Maven central and Docker Hub: |
| 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. There is a complete release guide at Release Process. |
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. Open issues are listed in the public Jira and discussed on the mailing list. |
| QU20 | The project puts a very high priority on producing secure software. | YES. Security issues are treated with the highest priority. |
| QU30 | The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them. | YES. We use the ASF security channel, which is linked on the website. |
| 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. A release contains a list of issues related to the release. There are also migration guides for breaking changes. Since 0.70.0, we introduced migration scripts for backwards compatibility. |
| QU50 | The project strives to respond to documented bug reports in a timely manner. | YES. The community is very active in responding to bug reports and usually fixes them within a short time period. |
Community
| CO10 | The project has a well-known homepage that points to all the information required to operate according to this maturity model. | YES. The website describes the project and contains links to all relevant systems (e.g., issue tracker, confluence, source repos, mailing lists). |
| CO20 | The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project. | YES. Committers are really welcome contributions and the commuity is actively seeking for new committers. |
| 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. The community welcomes all contributions, e.g., also blog posts or other marketing material. |
| 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. Several committers and PPMC members have been elected during the incubation phase so far. |
| 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. There are discussions on the mailing list and a wiki entry for contributors describing the process: Contribute |
| 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 days via the mailing list and issue tracker. |
Consensus
| 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 team page contains a list of some current committers who wanted to have their name listed on the website. |
| 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. So far, all. important decisions were made by consensus. |
| CS30 | Documented voting rules are used to build consensus when discussion is not sufficient. | YES. The project uses the standard ASF voting rules. |
| 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 has not used a veto at any point during incubation. |
| CS50 | All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions 11 that affect the project are also documented on that channel. | YES. The main communication channel is the mailing list. |
Independence
| IN10 | The project is independent from any corporate or organizational influence. | YES. The PPMC (excluding mentors) consists of members from at least 7 different organisations. Committers also come from various other organizations which are not represented in the PPMC. |
| IN20 | Contributors act as themselves as opposed to representatives of a corporation or organization. | YES. The contributors act on their own initiative without representing a corporation or organization. |