Difference between revisions of "DSDP/Restructuring Review"

From Eclipsepedia

Jump to: navigation, search
(Native Application Builder)
Line 7: Line 7:
 
The Device Software Development Platform raised the awareness of Eclipse to the embedded community. But given the ever decreasing
 
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.  
 
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).
  
 
=Projects=
 
=Projects=
Line 12: Line 14:
 
==Blinki==
 
==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.
+
Responsible: Wayne Beaton
 +
 
 +
There is no code committed in any Eclipse source code repository for the [http://www.eclipse.org/dsdp/blinki 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.
 
As part of this Restructuring, the Blinki project will be terminated.
 +
  
 
==Device Debugging (DD) ==
 
==Device Debugging (DD) ==
  
Project is inactive; there have been no commits since April 2009. The DD content has previously been moved to CDT.
+
Responsible: Wayne Beaton
 +
 
 +
The [http://www.eclipse.org/dsdp/dd 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.
 
As part of this Restructuring, the DD project will be terminated.
Line 24: Line 31:
 
==Mobile Tools for Java==
 
==Mobile Tools for Java==
  
Move to Subproject of Sequoyah.
+
Responsible: Gorkem Ercan, Eric Cloninger
 +
 
 +
The [http://www.eclipse.org/dsdp/mtj Mobile Tools for Java] (MTJ) project will move to Subproject of Sequoyah.
  
 
==Native Application Builder==
 
==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.
+
Responsible: Doug Schaefer
 +
 
 +
The [http://www.eclipse.org/dsdp/nab/ 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)==
  
==RTSC==
+
Responsible: Dave Russo, Technology PMC
  
Move to Technology.
+
The [http://www.eclipse.org/dsdp/rtsc Real-Time Software Components] (RTSC) project will move to [http://www.eclipse.org/technolog Technology].
 
 
 
==Sequoyah==
 
==Sequoyah==
  
Move to Tools
+
Responsible: Eric Cloninger, Tools PMC
  
<strike>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.</strike> ''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.''
+
The [http://www.eclipse.org/dsdp/sequoyah Sequoyah] Project will move to Tools.
  
 
==Target Management (TM)==
 
==Target Management (TM)==
  
 
===Target Communication Framework===
 
===Target Communication Framework===
[http://wiki.eclipse.org/TCF Target Communication Framework] (TCF) functionality from TM will be carved out and turned into a new project (tools.cdt.tcf).
+
 
 +
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).
  
 
====Description====
 
====Description====
Line 49: Line 65:
  
 
====Scope====
 
====Scope====
 +
 +
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.''
 +
 +
ECF
  
 
====Initial Committers====
 
====Initial Committers====
Line 58: Line 82:
 
*Uwe Stieber
 
*Uwe Stieber
 
*Eugene Tarassov
 
*Eugene Tarassov
 
<strike>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</strike> ''wtb: we don't need to mention those who will not be part of the project.''
 
  
 
====Initial Contribution====
 
====Initial Contribution====
Line 82: Line 97:
  
 
===The Rest of TM===
 
===The Rest of TM===
 +
 +
Responsible: Martin Oberhuber, Tools PMC
 +
 
The rest of TM should remain and be moved under the Tools project.
 
The rest of TM should remain and be moved under the Tools project.
  
 
[[Category:DSDP]]
 
[[Category:DSDP]]

Revision as of 10:32, 2 September 2010

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.

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

Projects

Blinki

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

The Real-Time Software Components (RTSC) project will move to Technology.

Sequoyah

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

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

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.

ECF

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

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

Responsible: Martin Oberhuber, Tools PMC

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