Technology/Restructure 2016
This is just some random musing about how we might restructure the Technology TLP.
This page captures some thoughts regarding the future of the Technology Top Level Project (TLP).
Don't panic. These are just some random thoughts and ideas. Nothing has been decided.
Contents
Remain in the Technology TLP
- APP4MC
- Babel
- Common Build Infrastructure
- Dash
- Dynamic Languages Toolkit
- e(fx)clipse
- Eclipse Advanced Scripting Environment (EASE)
- Eclipse Collections
- Eclipse Packaging Project
- Eclipse Process Framework Project
- Eclipse Scout
- Eclipse UOMo
- Golo
- Graphical Editing Framework 3D
- Handly
- Higgins
- Mbeddr
- MDM@WEB
- MDM|BL
- Nebula - Supplemental Widgets for SWT/Nebula Incubator/Nebula NatTable
- Jubula Functional Testing Tool
- Ogee
- Open System Engineering Environment
- openK platform
- Package Drone
- RCP Testing Tool
- RDF4J
- Sapphire
- Sisu
- Skalli
- Spatio-Temporal Epidemiological Modeler
- SWTBot
- Tycho
- XWT
Move to the Science TLP
We're not sure exactly which projects the Science TLP will take. The EAVP and ERB projects may continue to make sense as Technology subprojects.
- ChemClipse
- DAWNSci
- Eclipse Advanced Visualization Project
- Eclipse Rich Beans
- The Eclipse Integrated Computational Environment
- Triquetrum
Move to the Tools TLP
- Accessibility Tools Framework
- Code Recommenders/Code Recommenders Incubator
- Marketplace Client
- Lyo
- Maven Integration/Maven Integration for Web Tools Platform
Move to the Lifecycle TLP
- Eclipse Git Team Provider (already discussed with Matthias a while ago)
- EGerrit
- Subversive - SVN Team Provider
- Java implementation of Git
- Hudson
- M2E?
Terminate/Archive
- Aether (Termination review scheduled for Feb 17/2016)
- Commits Dashboard
- Eclipse Runtime Packaging Project
- Remus
- Real-Time Software Components
- Voice Tools Project
Don't know
- Cloud Application Management Framework (ECD?)
- Tigerstripe (IoT, Modeling?)