The Apache Software Foundation
Apache Incubator

Beam Project Incubation Status

This page tracks the project status, incubator-wise. For more general project status, look on the project website.


Apache Beam is an open source, unified model and set of language-specific SDKs for defining and executing data processing workflows, and also data ingestion and integration flows, supporting Enterprise Integration Patterns (EIPs) and Domain Specific Languages (DSLs). Dataflow pipelines simplify the mechanics of large-scale batch and streaming data processing and can run on a number of runtimes like Apache Flink, Apache Spark, and Google Cloud Dataflow (a cloud service). Beam also brings DSL in different languages, allowing users to easily implement their data integration processes.


  • 2016-02-01 Project enters incubation.
  • 2016-02-02 JIRA, mailing lists, git, website space created.
  • 2016-06-15 Apache Beam 0.1.0-incubating released
  • 2016-08-09 Apache Beam 0.2.0-incubating released

Project info

item type reference
Website www
Mailing list dev
. commits
. user
Bug tracking JIRA
Source code GIT
Champion jbonofre Jean-Baptiste Onofré
Mentor venkatesh Venkatesh Seetharam
. tdunning Ted Dunning
. jbonofre Jean-Baptiste Onofré
Committers aljoscha Aljoscha Krettek
. amitsela Amit Sela
. bchambers Ben Chambers
. Craig Chambers
. dhalperi Dan Halperin
. davor Davor Bonaci
. frances Frances Perry
. jamesmalone James Malone
. jbonofre Jean-Baptiste Onofré
. jwills Josh Wills
. ktzoumas Kostas Tzoumas
. kenn Kenneth Knowles
. lcwik Luke Cwik
. mxm Maximilian Michels
. sewen Stephan Ewen
. tomwhite Tom White
. takidau Tyler Akidau
. robertwb Robert Bradshaw

Incubation work items

Project Setup

This is the first phase on incubation, needed to start the project at Apache.

Item assignment is shown by the Apache id. Completed tasks are shown by the completion date (YYYY-MM-dd).

Identify the project to be incubated

date item
2016-02-01 Make sure that the requested project name does not already exist and check to be sure that the name is not already trademarked for an existing software product.
2016-02-01 If request from an existing Apache project to adopt an external package, then ask the Apache project for the SVN module and mail address names.
2016-02-01 If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
If request from anywhere to become a stand-alone PMC, then assess the fit with the ASF, and create the lists and modules under the incubator address/module names if accepted.


date item
2016-02-01 Ask infrastructure to create source repository modules and grant the committers karma.
2016-02-01 Ask infrastructure to set up and archive mailing lists.
2016-02-01 Ask infrastructure to set up issue tracker (JIRA, Bugzilla).
2016-02-20 Migrate the project to our infrastructure.

Mentor-related responsibility/oversight

date item
2016-02-01 Identify all the Mentors for the incubation, by asking all that can be Mentors.
2016-02-01 Subscribe all Mentors on the pmc and general lists.
2016-02-01 Give all Mentors access to the incubator git repository. (to be done by the Incubator PMC chair or an Incubator PMC Member wih karma for the authorizations file)
date item
2016-02-01 Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project.
2016-02-10 Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright.

Verify distribution rights

date item
2016-02-15 Check and make sure that for all code included with the distribution that is not under the Apache license, we have the right to combine with Apache-licensed code and redistribute.
2016-02-15 Check and make sure that all source code distributed by the project is covered by one or more of the following approved licenses: Apache, BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same terms.

Establish a list of active committers

date item
2016-02-01 Check that all active committers have submitted a contributors agreement.
2016-02-01 Add all active committers in the STATUS file.
2016-02-01 Ask root for the creation of committers' accounts on

Project specific

Add project specific tasks here.


These action items have to be checked for during the whole incubation process.

These items are not to be signed as done during incubation, as they may change during incubation. They are to be looked into and described in the status reports and completed in the request for incubation signoff.

Collaborative Development

  • Have all of the active long-term volunteers been identified and acknowledged as committers on the project?
  • Are there three or more independent committers? (The legal definition of independent is long and boring, but basically it means that there is no binding relationship between the individuals, such as a shared employer, that is capable of overriding their free will as individuals, directly or indirectly.)
  • Are project decisions being made in public by the committers?
  • Are the decision-making guidelines published and agreed to by all of the committers?

Licensing awareness

  • Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?

Project Specific

Add project specific tasks here.


Things to check for before voting the project out.

Organizational acceptance of responsibility for the project

  • If graduating to an existing PMC, has the PMC voted to accept it?
  • If graduating to a new PMC, has the board voted to accept it?

Incubator sign-off

  • Has the Incubator decided that the project has accomplished all of the above tasks?