Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Open Issues

  • slack.streampipes.org still used as a Slack channel
  • streampipes.org still owned by FZI and should be deleted or transferred to ASF


CODE


CD10The 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.
CD20The project's code is easily discoverable and publicly accessible.YES. The website includes links to the Github repos.
CD30The 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.

CD40The 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.
CD50The 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.WIP. 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.

...