OpenCue

Repository on GitHub, which provides public git repositories with URLs.

Repository on GitHub, which uses git. git can track the changes, who made them, and when they were made.

GitHub pull requests and branches satisfy this requirement.

Repository on GitHub, which uses git. git is distributed.

Every release is tagged with a Major.Minor.Patch version number. The version number is deterministic, in that every commit to master is identifiable by a version number, regardless of whether it has been officially released or not.

Release versions are provided as git tags.

Release notes are provided on our GitHub releases page: https://github.com/imageworks/OpenCue/releases

There have been no publicly known vulnerabilities at this time.

Users may file bugs using our bug report template: https://github.com/imageworks/OpenCue/issues/new?labels=bug&template=bug_report.md Or, general issue filing at https://github.com/imageworks/OpenCue/issues

The project uses the GitHub issue tracker: https://github.com/imageworks/OpenCue/issues

Bug issues are regularly triaged by project leads, and either fixed or added to a backlog as necessary.

Enhancement issues are regularly triaged by project leads, and either fixed or added to a backlog as necessary.

All past issues are available at https://github.com/imageworks/OpenCue/issues

The project security policy is published at https://github.com/AcademySoftwareFoundation/OpenCue/blob/master/SECURITY.md. This security policy appears when filing a new issue against the project.

This process is described in https://github.com/AcademySoftwareFoundation/OpenCue/blob/master/SECURITY.md.

No vulnerabilities have been reported yet, but regular issue triaging ensures they will be handled quickly.

Java components use Gradle to build binaries. Python components use pip and setuptools for building and packaging Python components. GitHub Actions is used to automate this process.

Java components use Gradle to build binaries. Python components use pip and setuptools for building and packaging Python components.

All tools in our build stack are OSS.

Java components use JUnit and Gradle for running tests. Python components use the unittest module setuptools for running tests. Test execution is automated via our CI system using GitHub Actions.

OpenCue uses the unittest Python library, and has the test structured as recommended ( example https://github.com/AcademySoftwareFoundation/OpenCue/blob/master/cueadmin/tests/common_tests.py )

Coverage for the project is >50%, and the TSC is working to increase this over time. https://sonarcloud.io/dashboard?id=AcademySoftwareFoundation_OpenCue

GitHub Actions is used to run our CI system. Automated tests are run for all Pull Requests and on our master branch.

Example: https://github.com/AcademySoftwareFoundation/OpenCue/pull/1337

Pull request templates document our policy of adding tests. Code reviewers are responsible for enforcing this policy. Sonar Quality Gate tracks our adherence to this policy.

Sonar Quality Gate tracks our adherence to this policy.

Pull request templates document this policy.

Java components use "-Xlint:all" and "-Werror" at build time. Python components use pylint, which is run as part of the testing suite. These tools must pass before pull requests can be merged. Sonar also identifies some additional warnings, these warnings have been addressed and our project has an "A" rating in Sonar.

All warnings originally identified by the above tools have addressed in the master branch. The CI pipeline which runs on all pull requests ensures new warnings will not be created.

Warning tools use maximally strict settings. The only pylint checks which have been disabled deal with superficial coding style rules.

Existing TSC members have this knowledge.

Existing TSC members have this knowledge.

None used

SonarCloud is used to analyze code. The project currently maintains an "A" rating there. Analysis is run on every commit to master, and our release policy is to address any identified issues before a release can be produced.

SonarCloud includes these rules.

All SonarCloud issues have been addressed, and our release policy ensures any new issues will be identified and quickly addressed.

Analysis occurs on every commit.

Python and Java code