Page History

...

The Apache Project Maturity Model assesses whether or not a project complies with each element in the following seven categories: code, licenses and copyright, releases, quality, community, consensus building, and independence. There are no intermediate levels: a project either complies with an element or it does not. The following sections address Taverna's status regarding each element of the model.

NOTE: Numbers in brackets ([ ]) refer to footnotes on the Apache Project Maturity page, and are reproduced at the bottom of this document.

Code

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

...

• 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

[1] "For distribution to the public at no charge" is straight from the from the ASF Bylaws at http://apache.org/foundation/bylaws.html.
[2] See also LC40.
[3] It's ok for platforms (like a runtime used to execute our code) to have different licenses as long as they don't impose reciprocal licensing on what we are distributing.
[4] http://apache.org/legal/resolved.html has information about acceptable licenses for third-party dependencies 
[5] In Apache projects, the ASF owns the copyright for the collective work, i.e. the project's releases. Contributors retain copyright on their contributions but grant the ASF a perpetual copyright license for them. 
[6] See http://www.apache.org/dev/release.html for more info on Apache releases 
[7] The required level of security depends on the software's intended uses, of course. Expectations should be clearly documented. 
[8] Apache projects can just point to http://www.apache.org/security/ or use their own security contacts page, which should also point to that.
[9] In Apache projects, "consensus" means widespread agreement among people who have decision power. It does not necessarily mean "unanimity".
[10] For Apache projects, http://www.apache.org/foundation/voting.html defines the voting rules.
[11] Apache projects have a private mailing list that their PMC is expected to use only when really needed. The private list is typically used for discussions about people, for example to discuss and to vote on PMC candidates privately.
[12] Independence can be understood as basing the project's decisions on the open discussions that happen on the project's main communications channel, with no hidden agendas.