Skip to main content
Jump to: navigation, search

DSDP/Restructuring Review

Revision as of 16:21, 17 August 2010 by (Talk | contribs) (Initial Contribution)

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


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.



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.

(Doug) Subproject of Sequoyah? Merge into Sequoyah?

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.


Move to Technology.


Move to Tools.

As Sequoyah is the successor to the Tools for Mobile Linux (TmL) project, TmL will cease to exist when DSDP is restructured. The code for TmL has already been moved to either Sequoyah or Linux Tools and archives are available for historical purposes.

Target Management (TM)

Target Communication Framework

Target Communication Framework (TCF) functionality from TM will be carved out and turned into a new project (tools.cdt.tcf).


TCF is a vendor-neutral, lightweight, extensible network protocol mainly for communicating with embedded systems (targets). Its most distinguishing feature is that TCF is designed to transparently plug in value-adding servers between the tool and the target. But even without value-add, the protocol has potential to unify lots of currently independent communication links, thus saving resources and making setup and configuration much easier than in current embedded development scenarios.


Initial Committers

The following individuals are current committers on the TM project. They will continue their responsibilities in the new project.

Doug, please edit

  • Xuan Chen
  • Anna Dushistova
  • David Dykstal
  • David McKnight
  • Martin Oberhuber
  • Uwe Stieber
  • Eugene Tarassov

Initial Contribution

The TCF functionality from TM will be moved into this project. Specifically, this is:

The Rest of TM

The rest of TM should remain and be moved under the Tools project.

Back to the top