Skip to main content
Jump to: navigation, search

Difference between revisions of "DSDP/Restructuring Review"

(Target Management)
(Native Application Builder)
Line 25: Line 25:
  
 
Project is inactive. No actual committers on the project (only a project lead). No commits since 2008. Terminate.
 
Project is inactive. No actual committers on the project (only a project lead). No commits since 2008. Terminate.
 +
 +
(Doug) Alternative, bring the source code sans committers into CDT (all committers are inactive anyway). C/C++ GUI building is in CDT scope.
  
 
==RTSC==
 
==RTSC==

Revision as of 12:19, 17 August 2010

This page provides a working area for the creation of documentation for a combined Restructuring/Termination review for the DSDP project.

Overview

The Device Software Development Platform raised the awareness of Eclipse to the embedded community. But given the ever decreasing participation in it, it probably is a good time to retire the project and send the pieces to more natural homes.

Projects

Blinki

Project metadata is out of date, so Dash statistics are not available. Project appears inactive. Terminate.

The current status of Blinki is unknown. The project is quite inactive at the moment. We have initiated a discussion with the project leadership to determine if Blinki can be re-energized as part of this effort, or if it should be terminated along with DSDP.

Device Debugging

Project is inactive. No commits since April 2009. The DD content has previously been moved to CDT. Terminate.

Mobile Tools for Java

Move to Tools.

Native Application Builder

Project is inactive. No actual committers on the project (only a project lead). No commits since 2008. Terminate.

(Doug) Alternative, bring the source code sans committers into CDT (all committers are inactive anyway). C/C++ GUI building is in CDT scope.

RTSC

Move to Technology.

Sequoyah

Move to Tools.

Target Management

Move content and committers into CDT and terminate. Or does it make more sense make this a Subproject of CDT?

(Doug) Separate out TCF from TM. TCF would be a subproject of CDT. It includes functionality that depends on CDT and visa versa.

(Doug) The rest of TM should remain and be a Tools subproject.

Back to the top