Projects Lifecycle

Overview

The Consortium's activities for software development are organized into Projects. A Project regroups either development actions corresponding to one or more technical software components or the integration of different technical components in order to build a platform. Projects are the raison d'être of OW2, and without projects, OW2 just would not exist. Projects represent the fundamental activity. At OW2, everything starts with a Project.

Building on the legacy of ObjectWeb and OrientWare, OW2 is fully committed to managing open-source projects. They currently cover a broad scope of infrastructure software functionality including middleware and generic applications, application platforms, persistency/database solutions, workflow engines, software engineering, etc. OW2 provides a "home" as well as a showcase to open source software projects. Each project evolves through a lifecycle described below. OW2 already hosts some 80 projects.

The Technology Council is responsible for building the overall technical architecture, including defining technical guidelines, providing technology validation, making Project lifecycle decisions, and monitoring production and overall Projects consistency.

Projects Lifecycle

The project lifecycle is composed of three stages: Incubation, Mature and Archive

New projects start in the Incubation stage then may move to the Mature stage and, ultimately, might end up in Archive stage depending on periodic evaluation by the Technology Council.

The Technology Council has defined a set of criteria to evaluate migration from the Incubation to the Mature status. The Technology Council organizes regular reviews of projects to manage their lifecycle status. Deciding whether a project should move to the Archive status can be proposed by the Project Leader. Alternatively, upon observing the non-evolution of the project code base and activity over a period of time, OW2 can contact the Project Leader to propose moving to Archive. Note that an Archive project still benefits from the OW2 infrastructure services, and can come back to the Incubator or Mature status when activity resumes.

A fully executed Corporate or Strategic membership is required for a project to be moved from Incubation to Mature status. Community projects based on individual members will only be handled on a case-by-case basis. Competition will be re-assessed for moving to the Mature status.

Submitting a new project

New projects can be submitted from the project submission page.

The fully executed Individual membership of the project leader is the minimum membership requirement for a project to be accepted in incubation. The proposal is then debated on the Technology Council mailing list which evaluates its relevance for OW2 in terms of complementarities, synergies, licence, support, etc. The Technology Council must reach a consensus to adopt the project. Each project must also be presented and discussed at a Technology Council meeting. Once it is provisioned in the OW2 Forge, you can start working on it. 

Project selection criteria

Project submissions are evaluated by the Technology Council which decides by consensus whether or not to host the project on the OW2 infrastructure. The Technology Council will decide after evaluating and reaching consensus on the four principal following criteria:

  • Is it infrastructure software at large (middleware, libraries, tooling, application platform, etc.)?
  • Does the team show goodwill to synergize with other OW2 projects?
  • Is the license compatible with the IPR policy?
  • Is the Project able to release code and/or foster a community?

Competition between projects

OW2 recognizes that a dynamic code base must accept some level of competition between its projects. Moreover the OW2 project portfolio is already quite extensive and could not grow without some friction or overlap between projects. Projects with overlapping or 'competitive' features will be allowed on the OW2 Forge and in OW2 initiatives so long as they are:
 

  1. Provided by an OW2 Member. 
  2. Distributed under an OSI-approved license.
  3. Differentiated from existing projects.
  4. Accepted by the Technology Council.