This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Skip to end of metadata
Go to start of metadata


Podling maturity evaluation of Apache Airflow based on the Apache project maturity model.


iddescription (from maturity model)evaluationcommitters agreeing with evaluation
  • CD10
The project produces Open Source software, for distribution to the public at no charge.The project has always been open source and distributed for free at no charge.bolke
  • CD20
The project's code is easily discoverable and publicly accessible.A Google search easily finds the project home page and source on the GitHub mirror.bolke
  • CD30
The code can be built in a reproducible way using widely available standard tools.The code is built using Python. Instructions for building the code are documented:
  • 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.The full history of the project is available in git. Each release is tagged in git in a consistent way (e.g. v1.10.1rc2). Each major release has a stable branch (e.g. v1-10-stable) and development branch (e.g. v1-10-test). This makes it possible to reconstruct the release from source history. Instructions for releasing are clearly documented in Releasing Airflow.bolke
  • 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. This is established by the git commit history:

Licenses and Copyright

iddescription (from maturity model)evaluationcommitters agreeing with evaluation
  • 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.

All dependencies are Apache 2.0 compatible(

  • LC30
The libraries mentioned in LC20 are available as Open Source software.All dependences mentioned in LC20 are open source.bolke
  • 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 committers have completed the ICLA.bolke
  • LC50
The copyright ownership of everything that the project produces is clearly defined and documented.All necessary files have a header covering license ownership. This can be verified with the rat task in the build system. Any other copyright information is available in the LICENSE files.bolke



iddescription (from maturity model)evaluationcommitters agreeing with evaluation
  • RE10
Releases consist of source code, distributed using standard and open archive formats that are expected to stay readable in the long term.
  • 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.
  • RE40
Convenience binaries can be distributed alongside source code but they are not Apache Releases -- they are just a convenience provided with no guarantee.

Binary releases are available here: and

  • RE50
The release process is documented and repeatable to the extent that someone new to the project is able to independently generate the complete set of artifacts required for a release.Releasing Airflowbolke



iddescription (from maturity model)evaluationcommitters agreeing with evaluation
  • 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.

Yes. For example, there are unit tests and integration tests covering the code. We report on the coverage. Coveralls shows at time of writing Coverage Status 


  • QU20
The project puts a very high priority on producing secure software. 



  • QU30
The project provides a well-documented channel to report security issues, along with a documented way of responding to them.

We follow the generic Apache way of handling security issues. Per and


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

Yes, through Jira and


  • QU50
The project strives to respond to documented bug reports in a timely manner.

Yes, through Jira and release notes.




iddescription (from maturity model)evaluationcommitters agreeing with evaluation
  • CO10
The project has a well-known homepage that points to all the information required to operate according to this maturity model.
  • CO20
The community welcomes contributions from anyone who acts in good faith and in a respectful manner and adds value to the project.No examples of unkind or rejecting behavior could be found in a search through the e-mail list.bolke
  • CO30
Contributions include not only source code, but also documentation, constructive bug reports, constructive discussions, marketing and generally anything that adds value to the project.Committers are evaluated on all these categories of contribution.bolke
  • CO40
The community is meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project.
New committers include:
  • ashb
  • fokkodriesprong
  • kaxil
  • CO50
The way in which contributors can be granted more rights such as commit access or decision power is clearly documented and is the same for all contributors.

  • CO60
The community operates based on consensus of its members (see CS10) who have decision power. Dictators, benevolent or not, are not welcome in Apache projects.Yes.bolke
  • CO70
The project strives to answer user questions in a timely manner.

One example occurred in email list:



Consensus Building

iddescription (from maturity model)evaluationcommitters agreeing with evaluation
  • 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.Public list of contributors with decision power are available here:
  • CS20
Decisions are made by consensus among PMC members 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.

Decisions are documented in the dev mailing list, in JIRAs tracked in the Bugs link and on PRs on Github.

  • CS30
Documented voting rules are used to build consensus when discussion is not sufficient.The Apache Airflow community fully accepts standard ASF voting
rules as detailed here:
  • 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.Vetoes are only valid for code commits and are justified by a technical explanationbolke
  • 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.All important discussions happen in the documented communication channels, which is either the dev mailing list or in JIRAs. Any offline communication that happens is documented in those channels.bolke



iddescription (from maturity model)evaluationcommitters agreeing with evaluation
  • IN10
The project is independent from any corporate or organizational influence. 

PMC members/committers come from the following organization:

* Dan Davydov (aoen)
* Arthur Wiedmer (artwr)
* Maxime Beauchemin (mistercrunch)
* Alex Guziel (..)
* Bolke de Bruin (bolke)
* Fokko Driesprong (fokko) GoDataDriven
* Tao Feng (...)
* Joy Gao (jgao)
* Kaxil Naik (kaxil) independent
* Sid Anand (r...)

* Chris Riccomini (ccriccomini)
* Sid Anand (r...)

Having committers from a diverse set of companies means independence from the influence of any one company. Committers are sometimes  paid by their organizations to work on Airflow specifically.

  • IN20
Contributors act as themselves as opposed to representatives of a corporation or organization.None of the contributors act as representatives of a corporation or organization and only act for themselves.bolke




  • No labels