The Apache Software Foundation
The Apache Software Foundation Incubator

Airavata Project Incubation Status

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

The Airavata project graduated on 2012-09-19


Apache Airavata, a software framework to compose, manage, execute, and monitor distributed applications and workflows on computational resources ranging from local resources to computational grids and clouds. Airavata can be used as individual components or as an integrated solution to build science gateways or general-purpose distributed application and workflow management systems. Users can use Airavata back end services and build gadgets to deploy in open social containers such as Apache Rave and modify them to suit their needs. Airavata builds on general concepts of service oriented computing, distributed messaging, and workflow composition and orchestration.


  • 2012-09-19 Apache Airavata TLP is created
  • 2012-09-19 ASF Board passed a resolution to create Apache Airavata TLP
  • 2012-09-10 The Incubator PMC voted and accepted a proposal to recomment Airavta TLP creation resolution to the board
  • 2012-09-06 Airavata community uninamously voted Suresh Marru as rge woodbe PMC chair
  • 2012-08-30 Airavata community voted to approve the community is ready to graduate out of the incubator
  • 2012-08-01 Airavata 0.4-INCUBATING is released
  • 2012-07-19 Shahani Weerawarana is voted and added as a new committer
  • 2012-06-21 Airavata 0.3-INCUBATING is released
  • 2012-05-05 Airavata 0.2-INCUBATING is released
  • 2011-11-29 Saminda Wijeratne is voted and added as a new committer
  • 2011-10-31 Heshan Suriyaarachchi is voted and added as a new committer
  • 2011-08-19 Patanachai Tangchaisin is voted and added as a new committer
  • 2011-07-30 Lahiru Gunathilake is voted and added as a new committer
  • 2011-07-20 Barbara Hallock is voted and added as a new committer
  • 2011-06-26 The website is live
  • 2011-05-14 Donated code is imported and the project is active
  • 2011-05-07 Project enters incubation

Project info

item type reference
Website www
Mailing list developer
Private (PPMC)
Bug tracking
Source code SVN
Champion Ross Gardler
Mentors Alek Slominski
Ate Douma
Sanjiva Weerawarna
Paul Fremantle
Chris A. Mattmann
Committers Suresh Marru
Marlon Pierce
Srinath Perera
Aleksander Slominski
Raminderjeet Singh
Archit Kulshrestha
Chathura Herath
Eran Chinthaka
Thilina Gunaratne
Wathsala Vithanage
Barbara Hallock
Lahiru Gunathilake
Patanachai Tangchaisin
Heshan Suriyaarachchi
Saminda Wijeratne
Shahani Markus Weerawarana

Incubation status reports

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
2011-05-05 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. Note: Since is no longer offering free trademark searches, the US Patent Office was searched for Airavata with no results. Google searches for Apache Airavata only resturned results relavent to incubator proposal. No other the Apache Airavata project is returned. The team bought the airavata .com and .org domains.
2011-05-05 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.

Interim responsibility

date item
2011-05-05 Identify all the Mentors for the incubation, by asking all that can be Mentors.
2011-05-05 Subscribe all Mentors on the pmc and general lists.
2011-05-05 Give all Mentors access to the incubator SVN repository. (to be done by the Incubator PMC chair or an Incubator PMC Member wih karma for the authorizations file)
2011-05-05 Tell Mentors to track progress in the file 'incubator/projects/{}.html'
date item
Done 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.
Done 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
Done Check and make sure that for all code included with the distribution that is not under the Apache license, e have the right to combine with Apache-licensed code and redistribute.
Done 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
2011-05-05 Check that all active committers have submitted a contributors agreement.
2005-06-22 Add all active committers in the STATUS file.
2011-05-05 Ask root for the creation of committers' accounts on


date item
2011-05-05 Ask infrastructure to create source repository modules and grant the committers karma.
2011-05-05 Ask infrastructure to set up and archive Mailing lists.
2011-05-05 Decide about and then ask infrastructure to setup an issuetracking system (Jira).
2011-05-05 Migrate the project to our infrastructure.


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? YES, the initial committers have been identified and accepted committership and working together on development. - DONE -
  • 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.) YES, Airavata has demonstrated the diversity and welcoming committers from diverse organizations. The committers are affiliated to more than three organizations. - DONE -
  • Are project decisions being made in public by the committers? YES, the commiters actively use the dev mailing lists and jira for all decisions. - DONE -
  • Are the decision-making guidelines published and agreed to by all of the committers? YES, the guideles have been agreed by the committers and published on the airavata website. - DONE -

Licensing awareness

  • Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers? Yes, all trademark and licensing issues have been taken care and approved by all committers, mentors and trademarks at a.o. - DONE -

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 a new PMC, has the board voted to accept it? YES, on September 19th 2012, the board has uninamously passed a resolution to accept Airavata as a Top Level Project. - DONE -

Incubator sign-off

  • Has the Incubator decided that the project has accomplished all of the above tasks? Yes, on Sept 10th 2012, the IPMC has the voted the project has accomplished all the tasks passed the proposal to recommend resolution to create Aira vata TLP to the ASF Board. - DONE -