The Apache Software Foundation
The Apache Software Foundation Incubator

Cassandra Project Incubation Status

This page tracks the project's status in the incubator. For more general project status, please see the project website.

The Cassandra project graduated on 2010-02-17


The Cassandra Project is a massively scalable second generation distributed database.


  • 2009-12-31 0.5.0-rc1 released.
  • 2009-12-16 Jaakko Laine added as a new committer.
  • 2009-12-16 Gary Dusbabek added as a new committer.
  • 2009-12-09 0.5.0-beta2 released.
  • 2009-11-20 0.5.0-beta1 released.
  • 2009-11-19 Johan Oskarsson added as a new committer.
  • 2009-11-09 0.4.2 released.
  • 2009-10-16 0.4.1 released.
  • 2009-10-05 Chris Goffinet added as a new committer.
  • 2009-09-26 0.4.0 released.
  • 2009-09-16 0.4.0-rc2 released.
  • 2009-08-17 0.4.0-beta1 released.
  • 2009-07-20 0.3.0 released.
  • 2009-06-29 Jun Rao added as a new committer.
  • 2009-06-29 Eric Evans added as a new committer.
  • 2009-03-26 Jonathan Ellis added as a new committer.
  • 2009-01-02 Project enters incubation.

Project info

item type reference
Website www
Wiki www
Mailing list devel
Mailing list user
Mailing list commits
Bug tracking JIRA
Source code SVN incubator/cassandra
Mentor antelder Ant Elder
Mentor BrianM Brian McCallister
Mentor mriou Matthieu Riou
Committer/PMC alakshman Avinash Lakshman
Committer/PMC pmalik Prashant Malik
Committer/PMC jbellis Jonathan Ellis
Committer/PMC eevans Eric Evans
Committer/PMC junrao Jun Rao
Committer/PMC goffinet Chris Goffinet
Committer kannan Kannan Muthukkaruppan
Committer jhuang Jiansheng Huang
Committer Dan Dumitriu
Committer johan Johan Oskarsson
Committer gdusbabek Gary Dusbabek
Committer jaakko Jaakko Laine

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
2009-01-02 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.
2009-01-02 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.
2009-01-02 If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance.
2009-01-02 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
2009-01-02 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.
2009-01-02 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
2009-01-02 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.
2009-01-02 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
2009-01-02 Check that all active committers have submitted a contributors agreement.
2009-01-02 Add all active committers in the STATUS file.
2009-01-02 Ask root for the creation of committers' accounts on


date item
2009-01-02 Ask infrastructure to create source repository modules and grant the committers karma. (JIRA: INFRA-1840)
2009-01-02 Ask infrastructure to set up and archive Mailing lists. (JIRA: INFRA-1841)
2009-01-02 Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira). (JIRA: INFRA-1842)
2009-01-02 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?
  • 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 acknowledged by all committers?


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?