The Eclipse Data Tools Platform Incubator hosts new development in areas that are relevant to the other Eclipse Data Tools Platform projects, which because of their nature would not be appropriate for direct inclusion in the effected sub-project. This could be because the work is still experimental, will have a longer timeline than can be contained within a single release, has dependencies on external IP that has not yet cleared the Eclipse Foundation IP process, or is simply potentially too destabilizing in nature.

+

+

==Out of Scope==

+

Work in the Eclipse Data Tools Platform Incubator will be constrained to only those efforts that we expect to graduate (i.e. the code will eventually become part of one of the other Eclipse Data Tools Platform sub-projects). It is not a playground for arbitrary development efforts. In addition, we should ensure that investment in the incubator never leaves the community with the perception that it is coming at the cost of important work on the other Eclipse Data Tools Platform sub-projects.

+

==Incubation Process==

==Incubation Process==

−

(Coming soon...)

+

Components in the DTP incubator follow a similar path to incubating projects at Eclipse:

+

+

'''1.''' Using a DTP community forum (such as the newsgroup or a mailing list), indicate interest in creating an incubation component.

+

+

'''2.''' The DTP PMC will review the request to determine if the component is in [http://www.eclipse.org/datatools/charter.php scope for DTP] and to help those proposing the component understand the commitment required.

'''4.''' Working with the DTP PMC, the component team will notify the Eclipse community at large about the pending creation.

+

+

'''5.''' Once (3) and (4) are complete, the component will be created in the Incubator project.

+

+

'''6.''' The component team works on developing the community and building an ecosystem around it. The idea is to get into working the [http://www.eclipse.org/projects/dev_process/incubation-phase.php Eclipse Way].

+

+

'''7.''' At some point the component will reach a level of development where it is ready to [http://www.eclipse.org/projects/dev_process/graduation-review.php graduate] to the appropriate mature project in DTP. The PMC will work with the component team to complete this graduation process, which will normally take place as part of a larger DTP release cycle. For details about the promotion process, see [[DTP Incubator Promotion Policy | DTP Incubator Promotion Policy]].

+

==Incubating Components==

==Incubating Components==

−

(None at the moment.)

+

+

* [[Ecore_ODA_Driver|Ecore ODA Driver]]

+

+

==Inquiries==

+

For questions about the DTP Incubator project, please email the [mailto:dtp-pmc@eclipse.org DTP PMC].

+

+

[[Category:Data Tools Platform]]

Latest revision as of 21:33, 8 October 2010

Contents

Incubating DTP...

About the DTP Incubator

The Eclipse Data Tools Platform Incubator hosts new development in areas that are relevant to the other Eclipse Data Tools Platform projects, which because of their nature would not be appropriate for direct inclusion in the effected sub-project. This could be because the work is still experimental, will have a longer timeline than can be contained within a single release, has dependencies on external IP that has not yet cleared the Eclipse Foundation IP process, or is simply potentially too destabilizing in nature.

Out of Scope

Work in the Eclipse Data Tools Platform Incubator will be constrained to only those efforts that we expect to graduate (i.e. the code will eventually become part of one of the other Eclipse Data Tools Platform sub-projects). It is not a playground for arbitrary development efforts. In addition, we should ensure that investment in the incubator never leaves the community with the perception that it is coming at the cost of important work on the other Eclipse Data Tools Platform sub-projects.

Incubation Process

Components in the DTP incubator follow a similar path to incubating projects at Eclipse:

1. Using a DTP community forum (such as the newsgroup or a mailing list), indicate interest in creating an incubation component.

2. The DTP PMC will review the request to determine if the component is in scope for DTP and to help those proposing the component understand the commitment required.

3. Any initial code is subject to parallel IP review by Eclipse legal.

4. Working with the DTP PMC, the component team will notify the Eclipse community at large about the pending creation.

5. Once (3) and (4) are complete, the component will be created in the Incubator project.

6. The component team works on developing the community and building an ecosystem around it. The idea is to get into working the Eclipse Way.

7. At some point the component will reach a level of development where it is ready to graduate to the appropriate mature project in DTP. The PMC will work with the component team to complete this graduation process, which will normally take place as part of a larger DTP release cycle. For details about the promotion process, see DTP Incubator Promotion Policy.