Page History

...

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

Licenses and Copyright

LC10: The code is released under the Apache License, version 2.0.
Apache Taverna ...
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 ...
LC30: The libraries mentioned in LC20 are available as Open Source software.
Apache Taverna ...
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.
Apache Taverna ...
LC50: The copyright ownership of everything that the project produces is clearly defined and documented. [5]
Apache Taverna ...

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 ...
RE20: Releases are approved by the project's PMC (see CS10), in order to make them an act of the Foundation.
Apache Taverna ...
RE30: Releases are signed and/or distributed along with digests that can be reliably used to validate the downloaded archives.
Apache Taverna ...
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 ...
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 ...
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 ...
QU50: The project strives to respond to documented bug reports in a timely manner.
Apache Taverna ...

Community

CO10: The project has a well-known homepage that ponts to all the nformaton requred to operate accordng to ths maturty model.
Apache Taverna ...
CO20: The communty welcomes contrbutons from anyone who acts n good fath and n a respectful manner and adds value to the project.
Apache Taverna ...
CO30: Contrbutons nclude not only source code, but also documentaton, constructve bug reports, constructve dscussons, marketng and generally anythng that adds value to the project.
Apache Taverna ...
CO40: The communty s mertocratc and over tme ams to gve more rghts and responsbltes to contrbutors who add value to the project.
Apache Taverna ...
CO50: The way n whch contrbutors can be granted more rghts such as commt access or decson power s clearly documented and s the same for all contrbutors.
Apache Taverna ...
CO60: The communty operates based on consensus of ts members (see CS10) who have decson power. Dctators, benevolent or not, are not welcome n Apache projects.
Apache Taverna ...
CO70: The project strves to answer user questons n a tmely manner.
Apache Taverna ...

Consensus Building

CS10: The project maintains a public list of its contributors who have decision power -- the project's PMC (Project Management Committee) consists of those contributors.
Apache Taverna ...
CS20: Decisions are made by consensus among PMC members [9] and are documented on the project's main communications channel. Community opinions are taken into account but the PMC has the final word if needed.
Apache Taverna ...
CS30: Documented voting rules are used to build consensus when discussion is not sufficient. [10]
Apache Taverna ...
CS40: In Apache projects, vetoes are only valid for code commits and are justified by a technical explanation, as per the Apache voting rules defined in CS30.
Apache Taverna ...
CS50: All "important" discussions happen asynchronously in written form on the project's main communications channel. Offline, face-to-face or private discussions [11] that affect the project are also documented on that channel.
Apache Taverna ...

Independence

IN10: The project is independent from any corporate or organizational influence. [12]
Apache Taverna ...
IN20: Contributors act as themselves as opposed to representatives of a corporation or organization.
Apache Taverna ...

Footnotes from Apache Project Maturity Model

...