DSDP/Restructuring Review

From Eclipsepedia

< DSDP
Revision as of 10:17, 2 September 2010 by Wayne.eclipse.org (Talk | contribs)

Jump to: navigation, search

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.

Contents

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

There is no code committed in any Eclipse source code repository. 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)

Project 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

Move to Subproject of Sequoyah.

Native Application Builder

Project 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.

RTSC

Move to Technology.

Sequoyah

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. wtb: TmL is already marked as archived in the Foundation DB. If we've missed archiving something, please advise the EMO. But I don't think we need to include discussion of TmL in this document.

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).

Description

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.

Scope

Initial Committers

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

The following TM committers have never been active on TCF and should not be provisioned initially for TCF:

  • Xuan Chen
  • Kevin Doyle
  • David Dykstal
  • Radoslav Gerganov
  • David McKnight
  • Michael Scharf wtb: we don't need to mention those who will not be part of the project.

Initial Contribution

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 Rest of TM

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