The Apache Software Foundation
The Apache Software Foundation Incubator

Sling Project Incubation Status

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

The Sling project graduated on 2009-06-17


Sling is a framework to develop content centric web applications based on the idea of modularizing the rendering of HTTP resources.


  • 2009-06-17: Board passed resolution to establish Apache Sling as a TLP
  • 2009-05-18: Release of Apache Sling Commons MIME support 2.1.0-incubator
  • 2009-05-13: Second Release of Apache Sling
  • 2009-03-30: New committer: Vidar Ramdal
  • 2008-06-26: First Release of Apache Sling
  • 2008-04-07: Sling present at ApacheCon EU 08: Fast Feather Track and BOF
  • 2008-01-16: New committer: Padraic Hannon
  • 2007-11-06: Sling present at ApacheCon US 07: Fast Feather Track and BOF
  • 2007-11-06: Sling API replaces Component API
  • 2007-09-10: Source code is now available in the Apache SVN repository

Project info

If the project website and code repository are not yet setup, use the following table:

item type reference
Website www
Mailing list dev
private (PPMC)
Bug tracking jira
Source code SVN
Sponsor Jackrabbit PMC
Mentors jukka Jukka Zitting
gianugo Gianugo Rabellino
farra J Aaron Farr
Committers   See up to date list on the Sling website

Incubation status reports

  • May 2009: New Committer Vidar S. Ramdal; Second Sling release
  • February 2009: OpenID contribution, preparing next release.
  • November 2008: Sling presented at and ApacheCon US.
  • August 2008: First Sling release
  • May 2008: Sling won the 5th prize at the JAX Innovation Award
  • February 2008: New Committer Padraic Hannon; Sling API finalized
  • November 2007: Migration of Component API to Sling API
  • October 2007: Site is up; Discussion on replacing Component API by Sling API
  • September 2007: Project started and setting up infrastructure

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
2007-06 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.
2007-09-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.
2007-09 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
2007-08-07 Identify all the Mentors for the incubation, by asking all that can be Mentors.
2007-08 Subscribe all Mentors on the pmc and general lists.
2007-08 Give all Mentors access to the incubator SVN repository. (to be done by PMC chair)
2007-08 Tell Mentors to track progress in the file 'incubator/projects/{}.html'
date item
2007-08-31 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.
2007-08-31 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
2008-06 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.
2008-06 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
2007-09-09 Check that all active committers have submitted a contributors agreement.
2007-09-10 Add all active committers in the STATUS file.
2007-09-09 Ask root for the creation of committers' accounts on


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

Project specific

date item
2007-09-11 Setup basic site.
2008-01 Care for nightly builds.
2007-09-10 Ask infrastrucure for SLING space on Confluence.
2007-11 Migrate existing documentation from Jackrabbit Wiki to own space.
2008-02-11 Move Site Source to new Confluence Space and create open Confluence Wiki Space


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?