Page History

...

• CD10: The project produces Open Source software, for distribution to the public at no charge. [1]

• • Apache Taverna ..'s source code is fully licensed as Apache License 2.0 for no charge.

• CD20: The project's code is easily discoverable and publicly accessible.

• • Apache Taverna's source repositories (git) are available from https://taverna.incubator.apache.org/download/code/ and mirrored to GitHub. Source code archives are available for each released component, e.g. https://taverna.incubator.apache.org/download/engine/#source-code (see also https://archive.apache.org/dist/incubator/taverna/source/ )

• CD30: The code can be built in a reproducible way using widely available standard tools.

• • Apache Tavera ...Apache Taverna's source code can be built using Apache Maven, Gradle (taverna-mobile) and Rake (taverna-databundle-viewer). Each repository has a README, e.g. https://github.com/apache/incubator-taverna-engine#building - build verified by Jenkins https://builds.apache.org/user/stain/my-views/view/taverna/.  (But note that the *-workbench repositories are ) 

• 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.

• • Apache Taverna's source code is hosted on http://git.apache.org/ in multiple git repositories, see https://git-wip-us.apache.org/repos/asf?a=project_list&s=taverna&btnS=Search and https://taverna.incubator.apache.org/download/code/.  Each release has a tag (based on release candidate VOTE), e.g. https://github.com/apache/incubator-taverna-engine/releases/tag/3.1.0-incubating - pre-Apache releases are tagged as old/*

• 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. [2]

...