All edits to this page are moderated by the DSDP PMC and EMO.
This page provides a working area for the creation of documentation for a combined Restructuring/Termination review for the DSDP project.
- 1 Overview
- 2 Projects
- 2.1 Blinki
- 2.2 Device Debugging (DD)
- 2.3 Mobile Tools for Java
- 2.4 Native Application Builder
- 2.5 Real-Time Software Components (RTSC)
- 2.6 Sequoyah
- 2.7 Target Management (TM)
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.
For each project, one or more responsible individuals are listed. These individuals will, upon success of the review, initiate the required actions (e.g. open a bug).
Responsible: Wayne Beaton
There is no code committed in any Eclipse source code repository for the Blinki project. The Website is out of date, and project metadata is not being maintained. All activity around the project appears stalled. The project is effectively dead.
As part of this Restructuring, the Blinki project will be terminated.
Device Debugging (DD)
Responsible: Wayne Beaton
The Device Debugging (DD) is inactive; there have been no commits since April 2009. The DD content has previously been moved to CDT.
As part of this Restructuring, the DD project will be terminated.
Mobile Tools for Java
Responsible: Gorkem Ercan, Eric Cloninger
The Mobile Tools for Java (MTJ) project will move to Subproject of Sequoyah.
Native Application Builder
Responsible: Doug Schaefer
The Native Application Builder (NAB) is inactive. No actual committers on the project (only a project lead). No commits since 2008. The source code from this project will be moved into CDT (no committers will be moved as part of this action). C/C++ GUI building is in CDT scope.
Real-Time Software Components (RTSC)
Responsible: Dave Russo, Technology PMC
Responsible: Eric Cloninger, Tools PMC
The Sequoyah Project will move to Tools.
Target Management (TM)
Target Communication Framework
Responsible: Martin Oberhuber
The TCF 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.
To provide a vendor-neutral, lightweight, extensible network protocol primarily intended for communicating with embedded systems (targets).
Relationship to Other Projects
Martin, can you please add a few words to describe the relationship with ECF? "This project competes with ECF" is valid here.
The following current TM committers have been active on TCF. They will continue their responsibilities in the new project.
- Felix Burton
- Anna Dushistova
- Martin Oberhuber
- Uwe Stieber
- Eugene Tarassov
TCF is a de-facto component of the TM project. The TCF functionality from TM will be moved into this project. Specifically, this is:
- The following SVN directories:
- The following CQs:
- CQ 1870 TCF initial contribution
- CQ 2519 TCF change to EPL/EDL dual-license
CQ 2553(rejected) dbghelp.dll
- The following Bugzilla components:
The Rest of TM
Responsible: Martin Oberhuber, Tools PMC
The rest of TM should remain and be moved under the Tools project.