Versions Compared

Old Version 10

changes.mady.by.user Gale Naylor

Saved on

compared with

New Version Current

changes.mady.by.user Ian Dunlop

Saved on

Key

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

Working draft ... in progressOutline completed 4/4/2016. Ready for content.

...

Goal: Make self-evaluation comments objective and demonstrable.

...

The purpose of this plan is to document the Apache Taverna podling's progress toward graduation from the Apache incubator. Initially, it is a roadmap for the Taverna PMC, showing completed items as well as those that have yet to be accomplished, and will help us focus our efforts to achieve project maturity. As graduation nears, the plan will be a measurable means for mentors, community members, the Incubator PMC, and the ASF Board of directors to assess Taverna's readiness to graduate. 

This Maturity Assessment Plan is based on the Apache Project Maturity Model and benefits from the experience of the Groovy Podling.

Status

 This is an initial outline of the Taverna Podling maturity plan and content needs to be added for each of the plan elementsWe are adding content to the plan.

Assessment Summary

 When completed, this section will summarize the readiness of the Taverna podling to graduate.

...

  • 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 and available with no charge..
  • CD20: The project's code is easily discoverable and publicly accessible.
  • CD30: The code can be built in a reproducible way using widely available standard tools.
  • 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.
  • 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]
    • Apache Taverna uses Git for version control. Every commit has a unique id. Commits are only allowed using ssh keys. All third part commits are checked for compliance with the Apache way before being merged.

Licenses and Copyright

  • LC10: The code is released under the Apache License, version 2.0.
    • Apache Taverna ...code is released under the Apache License, version 2.0
    • See also License review
  • 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 software.
  • 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 committers are bound by an ICLA. .. (Committers are listed on the Apache Taverna home page.)
  • 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.
  • 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]
    • Apache Taverna ...
  • 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.

...