Versions Compared

Old Version 13

changes.mady.by.user Stian Soiland-Reyes

Saved on

compared with

New Version 14

changes.mady.by.user Ian Dunlop

Saved on

Key

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

...

  • LC10: The code is released under the Apache License, version 2.0.
  • LC20: Libraries that are mandatory dependencies of the project's code do not create more restrictions than the Apache License does. [3, 4]
    • Apache Taverna ...does not contain any restrictive dependencies.
  • LC30: The libraries mentioned in LC20 are available as Open Source software.
    • All the Apache Taverna ...dependencies are available as open source.
  • 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.
    • All Apache Taverna ...commiters are bound by an ICLA (do we need to reference a commiter list?)
  • LC50: The copyright ownership of everything that the project produces is clearly defined and documented. [5]
    • All Apache Taverna ...source code contains the appropriate Apache copyright text.

Releases

  • RE10: Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term. [6]
    • Apache Taverna ...is based on open source, community maintained languages (list needed - Java, Android).
  • RE20: Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation.
    • Apache Taverna ...releases are voted for by the project PMC following the appropriate Apache release procedures (reference needed)
  • RE30: Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.
    • Apache Taverna ...releases are distributed along with SHA1 and MD5 digests to allow validation of downloads.
  • RE40: Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee.
    • Apache Taverna ...???

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.
    • Apache Taverna ..uses the Apache JIRA bug tracker system to list current issues.
  • QU20: The project puts a very high priority on producing secure software. [7]

...

  • QU30: The project provides a well-documented channel to report security issues, along with a documented way of responding to them. [8]
    • Apache Taverna ...uses mailing lists as well as IRC channels to communicate all of which are documented 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.
    • Apache Taverna ...backwards compatibility of what?
  • QU50: The project strives to respond to documented bug reports in a timely manner.
    • Apache Taverna ..strives to respond to bug reports as quick as is practicable. Most are responded to within 48 hours.

Community

  • CO10: The project has a well-known homepage that points to all the information required to operate according to this maturity model.

...