The Apache Software Foundation Apache Incubator

Apache Chemistry Incubation Status

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

Description

Apache Chemistry is a generic Java language implementation of the upcoming OASIS CMIS specification.

News

  • 2009-05-15 David Caruana added as a new committer
  • 2009-04-30 Project enters incubation.

Project info

item type reference
Website www http://incubator.apache.org/chemistry/
. wiki .
Mailing list dev chemistry-dev@incubator.apache.org
. commits chemistry-commits@incubator.apache.org
Bug tracking jira CMIS
Source code svn https://svn.apache.org/repos/asf/incubator/chemistry/
Mentors fmeschbe Felix Meschberger
. gianugo Gianugo Rabellino
. jukka Jukka Zitting
Committers bs Bogdan Stefanescu
. dcaruana David Caruana
. dpfister Dominique Pfister
. fguillaume Florent Guillaume
. gabriele Gabriele Columbro
. paolo Paolo Mottadelli
. sfermigier Stéfane Fermigier
. slacoin Stéphane Lacoin
. stan Sun Seng David Tan
. uncled David Nuescheler
Extra . .

Incubation status reports

July 2009

Apache Chemistry is an effort to provide a Java (and possibly others, like JavaScript) implementation of the upcoming CMIS specification. Chemistry entered incubation on April 30th, 2009.

There are currently no issues requiring board or Incubator PMC attention.

Community

  • David Caruana has been voted in as committer and member of the PPMC.

Software

  • David Caruana offered contribution of Client Test Harness

Licensing and other issues

  • None at the moment.

Issues before graduation:

  • Stabilize the general interest and energy into a sustainable development community
  • Make sure that all licensing details conform with Apache policies
  • Create an Apache release of the Chemistry codebase
June 2009

Apache Chemistry is an effort to provide a Java (and possibly others, like JavaScript) implementation of the upcoming CMIS specification. Chemistry entered incubation on April 30th, 2009.

The incubation process has started well. All the project infrastructure is in place and all initial committers have their Apache accounts. We even increased the headcount of the initial team as David Caruana joined the project as a new committer.

Development of the Chemistry codebase has moved to Apache svn and there's been a number or related discussions on the mailing list. Overall the project is still in a startup phase as people are getting oriented with the scope and structure of the project. A number of license headers were updated to match Apache policies.

Issues before graduation:

  • Stabilize the general interest and energy into a sustainable development community
  • Make sure that all licensing details conform with Apache policies
  • Create an Apache release of the Chemistry codebase
May 2009

Apache Chemistry is an effort to provide a Java (and possibly others, like JavaScript) implementation of the upcoming CMIS specification. Chemistry entered incubation on April 30th, 2009.

The Chemistry project has just entered incubation and we've been busy getting started with everything. Most of the project infrastructure is already in place, all the CLAs have been received, and the initial codebases are now in Apache svn.

Many Chemistry developers had a chance to meet in person in the CMIS PlugFest at the end of April, and the resulting energy has been visible also on the new Chemistry mailing lists. Among the results are updates to the core Chemistry codebase, a new JavaScript-based CMIS client codebase, and a proposal to contribute a Flex/Air -based CMIS explorer.

Issues before graduation:

  • Stabilize the general interest and energy into a sustainable development community
  • Make sure that license headers and other details conform with Apache policies
  • Create an Apache release of the Chemistry codebase

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-04-30 Make sure that the requested project name does not already exist and check www.nameprotect.com to be sure that the name is not already trademarked for an existing software product.
2009-04-30 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-04-30 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.

Interim responsibility

date item
2009-04-30 Identify all the Mentors for the incubation, by asking all that can be Mentors.
2009-04-30 Subscribe all Mentors on the pmc and general lists.
2009-04-30 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)
2009-04-30 Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html'

Copyright

date item
2009-04-30 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-08-16 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
....-..-.. 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.
....-..-.. 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-08-16 Check that all active committers have submitted a contributors agreement.
2009-08-16 Add all active committers in the STATUS file.
2009-08-16 Ask root for the creation of committers' accounts on people.apache.org.

Infrastructure

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

Project specific

Add project specific tasks here.

Incubation

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.

Exit

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?