Jump to: navigation, search

Difference between revisions of "TM Future Planning"

(TM 2.0.x Planning)
 
(24 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
<font size="-2">&lt; [[DSDP]] | [[DSDP/TM|TM]]</font>
 +
 
Collect input for the planning process for next year's DSDP Target Management Release ('''Eclipse Ganymede train, tentatively TM 3.0, June 2008''') as well as the upcoming service releases (DSDP-TM 2.0.x). Goals of this page are
 
Collect input for the planning process for next year's DSDP Target Management Release ('''Eclipse Ganymede train, tentatively TM 3.0, June 2008''') as well as the upcoming service releases (DSDP-TM 2.0.x). Goals of this page are
 
* Collect ideas and Requirements for Target Management Ganymede and beyond
 
* Collect ideas and Requirements for Target Management Ganymede and beyond
Line 7: Line 9:
  
 
An initial plan was discussed in the [[DSDP/TM/Committer_Phone_Meeting_22-May-2007|Committer Phone Meeting on 22-May-2007]].
 
An initial plan was discussed in the [[DSDP/TM/Committer_Phone_Meeting_22-May-2007|Committer Phone Meeting on 22-May-2007]].
 +
 +
More discussions will be at the [[DSDP/TM/Face-to-face Meeting Toronto 17-Sep-2007]].
  
 
== TM 2.0.x Planning ==
 
== TM 2.0.x Planning ==
  
 
* TM 2.0.1 and 2.0.2 to be aligned with [[Europa Simultaneous Release]] Service Releases in autumn and spring 08 respectively
 
* TM 2.0.1 and 2.0.2 to be aligned with [[Europa Simultaneous Release]] Service Releases in autumn and spring 08 respectively
** TM 2.0.1 might be released 2 or 3 weeks before Europa SR1
 
 
** No major feature additions; focus on unit tests, ISV Docs
 
** No major feature additions; focus on unit tests, ISV Docs
 
*** Probably adding RSE Terminal integration
 
*** Probably adding RSE Terminal integration
Line 17: Line 20:
 
** if we have any large things for 3.0 and want to start before 2.0.1 might do that in a branch; but having the branch this or that way is not a big deal
 
** if we have any large things for 3.0 and want to start before 2.0.1 might do that in a branch; but having the branch this or that way is not a big deal
  
== TM Ganymede Planning (tentatively TM 3.0) ==
+
== TM 3.0 (Ganymede) Planning ==
  
 
=== Bugzilla Plan Input ===
 
=== Bugzilla Plan Input ===
Line 27: Line 30:
 
** Target milestone "---" is uesd for bugs not yet analyzed or discussed.
 
** Target milestone "---" is uesd for bugs not yet analyzed or discussed.
 
* Bugzilla Queries
 
* Bugzilla Queries
** TM [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bapi%5D&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Importance All Open API Bugs] (32 bugs on 23-May-2007)
+
** TM [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bapi%5D&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Importance All Open API Bugs] (25 bugs on 10-Jul-2007)
** TM [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=Future&keywords_type=nowords&keywords=api&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&cmdtype=doit&order=Importance Non-API Enhancement Requests deferred to the Future] (55 bugs on 23-May-2007)
+
** TM [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=Future&keywords_type=nowords&keywords=api&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=enhancement&cmdtype=doit&order=Importance Non-API Enhancement Requests deferred to the Future] (93 bugs on 10-Jul-2007)
** TM [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=Future&keywords_type=nowords&keywords=api&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&cmdtype=doit&order=Importance Bugs deferred to the Future] (66 bugs on 23-May-2007)
+
** TM [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=Future&keywords_type=nowords&keywords=api&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&cmdtype=doit&order=Importance Bugs deferred to the Future] (108 bugs on 10-Jul-2007)
  
=== Should it be TM 2.1 or TM 3.0? ===
+
=== Planning and Priorities ===
* Themes "scaling down" and "be a better framework" strongly encourage heading for TM 3.0 such that we are not burdoned by a promise to maintain old APIs
+
* We have consensus to work towards TM 3.0 for Ganymede (rather than 2.1) so we'll allow API changes but keep them as small as possible. However, "getting things right" is agreed to be more important than being backward compatible.
* Doing 2.1 might be possible but harder than going for 3.0 right away; Finishing the UI/Non-UI refactoring is essential to complete for the next release
+
* Discussion and finalization of priorities into plan items will be at the [[DSDP/TM/DSDP/TM/Face-to-face Meeting Toronto 17-Sep-2007]].
* As it stands now, we see no clear requirement to be backward compatible with next year's release. If community wants it please speak up on the newsgroup or mailing list. We think we'll better be '''going for TM 3.0''' since not entirely happy with APIs yet. Though we'd strive to keep API changes small.
+
* '''Top 10 Priorities:'''
 +
** 1 - (All) '''Quality''', Maintenance, Reduce bug backlog. Add unit tests. Clean up old implementations, get rid of obsolete code.
 +
*** 1a - (WR, IBM) '''Improve UI''', Adhere to Guidelines, Better Wizard UI, Componentize connection/subsystem/services
 +
** 2 - (IBM, WR) '''Componentize''': UI/Non-UI splitting, avoid unnecessary plugin activation, support RCP
 +
** 3 - (IBM) '''Team Support''': Provide Import/Export of RSE Profiles by XML, provide UI for working with Profiles
 +
** 4 - (IBM) Contribute IBM '''User Action''' Framework
 +
** 5 - (WR) Contribute '''Target Communication Framework (TCF)''' Agent
 +
** 6 - (WR) Improve Remote CDT Launch; integrate remote CDT build
 +
** 7 - (WR, IBM) Improve '''Platform Integration''': Drag&Drop ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=196176 SWT:196176]), Command/Handler, Avoid Platform "internal" access, keyboard shortcuts; Improve EFS; Contribute Welcome content; Credentials Management via upcoming Platform JAAS support ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=196445 196445])
 +
*** Especially driving EFS forward can be important wrt community building - discussing caching / rsync facilities for EFS
 +
** 8 - (WR, IBM) '''Finalize / Clean up APIs''', making them maintainable from 3.0 without API breakage
 +
** 9 - (Contributors) '''Integrating''' other remote access solutions - ECF, Platform/Team Synchronization API, WebDAV, Wicked Shell, TPTP, JArchive; important for community building
 +
** 10 - (WR) Features for '''Multi-Core / Multisystem'''; flexible grouping of connections / items; investigate collaboration with PTP
 +
* '''"Might Have" Themes and Proposals (Interesting but probably not enough time)'''
 +
** Finalize Terminal APIs
 +
** Generic Filtering Framework / Generic monitoring APIs (possibly related to TCF)
 +
** Launch Actions
 +
** Remote Lab Manager Integrations
 +
** Shell Pattern Matching
 +
 
 +
=== Themes and Proposals ===
  
=== Priorities ===
 
* We have not yet agreed on clear priorities, but naturally those themes will be carried on first that have most interested parties, and where those interested parties actually contribute code, patches or committers.
 
 
* In the list of themes below, typically those themes or work items that we feel to be more important appear first. Not all items of a theme may be addressed, especially those appearing further down in the list for a theme would typically receive less attention.
 
* In the list of themes below, typically those themes or work items that we feel to be more important appear first. Not all items of a theme may be addressed, especially those appearing further down in the list for a theme would typically receive less attention.
 +
* Naturally those themes will be carried on first that have most interested parties, and where those interested parties actually contribute code, patches or committers.
 
* '''Community members can influence the planning process by declaring their interest, and/or especially declaring their willingness to contribute work on the themes.'''
 
* '''Community members can influence the planning process by declaring their interest, and/or especially declaring their willingness to contribute work on the themes.'''
 
* <font color="green">Contribute:</font> items below do not yet indicate a committment to actually contribute but do declare willingess of the signed up parties.
 
* <font color="green">Contribute:</font> items below do not yet indicate a committment to actually contribute but do declare willingess of the signed up parties.
  
=== Themes by Priority ===
+
==== '''Theme: Scaling Down''' ====
 +
* <font color="red">Interest: IBM, WR</font>
 +
* <font color="blue">Contribute: IBM, WR (committers)</font>
 +
* Further improve UI/Non-UI splitting, supporting
 +
** (a) RSE as an EFS provider without having to start up
 +
** (b) Remote file export in headless applications
 +
* Improve usage of the extension registry:
 +
** (a) Avoid plugin startup where not necessary - improve initial startup performance
 +
** (b) Make plugin registration dynamic, allowing dynamic reconfiguration (registry trackers etc: might be a requirement for the future provisioning story)
 +
* Improve Componentization:
 +
** (a) Support RCP, allowing the use of RSE even if Resources do not exist
 +
** (b) Provide a shortcut to RSE Services layer without Subsystems - probably via OSGi Services; might help EFS provider
 +
* Potentially move to Platform + 0 level --> move CDT Launcher to CDT Project
  
* See bugzilla [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Assignee TM Enhancement Requests Assigned to Future] for the full list of known bugzilla enhancement requests.
 
  
* '''Theme: Scaling Down'''
+
==== '''Theme: Be a Better Framework''' ====
** <font color="red">Interest: IBM, WR</font>
+
* <font color="red">Interest: WR, IBM, Symbian</font>
** <font color="blue">Contribute: IBM, WR (committers)</font>
+
* <font color="blue">Contribute: WR, IBM, Symbian (committers)</font>
** Further improve UI/Non-UI splitting, supporting
+
* '''Improve Quality, Maintainability, strive for small and efficient implementations'''
*** (a) RSE as an EFS provider without having to start up
+
** Most important point for IBM and WR
*** (b) Remote file export in headless applications
+
** Increase Unit Test Coverage
** Improve usage of the extension registry:
+
** Do unit tests with a GUI Recorder e.g. TPTP AGR
*** (a) Avoid plugin startup where not necessary - improve initial startup performance
+
** Reduce the Bug backlog
*** (b) Make plugin registration dynamic, allowing dynamic reconfiguration (registry trackers etc: might be a requirement for the future provisioning story)
+
** Collaborate with DSDP-DD and Platform/Debug for a cleaned-up SystemView solution
** Improve Componentization:
+
* Increase the flexibility of the host/subsystem/service combination after connection creation
*** (a) Support RCP, allowing the use of RSE even if Resources do not exist
+
** Improved more flexible wizards; allow adding and removing services as needed; Inheritable Properties for configuring subsystems
*** (b) Provide a shortcut to RSE Services layer without Subsystems - probably via OSGi Services; might help EFS provider
+
** Improved Wizard UI ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=176490 176490], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=142493 142493], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=192758 192758])
** Potentially move to Platform + 0 level --> move CDT Launcher to CDT Project
+
* '''Better live with the Platform'''
 
+
 
+
* '''Theme: Be a Better Framework'''
+
** <font color="red">Interest: WR, IBM, Symbian</font>
+
** <font color="blue">Contribute: WR, IBM, Symbian (committers)</font>
+
** Improve Quality, Maintainability, strive for small and efficient implementations
+
*** Collaborate with DSDP-DD and Platform/Debug for a cleaned-up SystemView soltuion
+
** Increase the flexibility of the host/subsystem/service combination after connection creation
+
*** Improved more flexible wizards; allow adding and removing services as needed; Inheritable Properties for configuring subsystems
+
 
** Make use of the Platform Command/Handler framework, including parameterized handlers, to all user-defined keyboard shortcuts, extender modifiable UI and macro recording (eventually)
 
** Make use of the Platform Command/Handler framework, including parameterized handlers, to all user-defined keyboard shortcuts, extender modifiable UI and macro recording (eventually)
** Finalize Terminal APIs
+
** Contribute Welcome content, http://www.eclipse.org/eclipse/platform-ua/documents/intro_3_3_features.html
** Provide a generic filtering framework (through OQL)
+
** Get rid of Platform Discouraged access ("internal")
** Re-think RSE SystemMessages: Do we need XML when we have Eclipse NLS / Java MessageFormat?
+
* '''Connection Sharing and Team Support'''
*** E.g. DStore_Service_Percent_Complete_Message -- multiple transformations for substitution
+
** Import/Export RSE Profiles; A must-have for IBM
 +
* '''Finalize Terminal APIs'''
 +
** Contribute Terminal Userdocs and API Docs
 +
* Fix and Improve '''Drag and Drop'''
 +
** Collaborate with Platform/Common Navigator to fix PluginTransfer into the Project Explorer
 +
** Collaborate with Platform/SWT to fix deferred drag&drop of remote files to copy into Windows Explorer ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=196176 bug 196176])
 +
** Improve the RSE DnD Framework to support extenders plug-in transfer types for specific objects in their own remote systems (Newsgroup: [http://dev.eclipse.org/newslists/news.eclipse.dsdp.tm/msg00173.html Uday Kabe, Lotus Notes]
 +
* Provide a generic filtering framework (through OQL)
 +
* Improve the '''connection data model''', being a store for IP-Xact data about hardware
 +
** remote system properties as defined by the [[DSDP/DD/Spirit|Spirit group]]
 +
* Re-think RSE SystemMessages: Do we need XML when we have Eclipse NLS / Java MessageFormat?
 +
** E.g. DStore_Service_Percent_Complete_Message -- multiple transformations for substitution
  
 +
==== '''Theme: Integrate other remote access solutions''' (strong should have) ====
 +
* <font color="red">Interest: Community, projects mentioned below</font>
 +
* <font color="blue">Contribute:</font>
 +
* '''Integrate Platform/Team WebDAV''' provider, and/or Google SoC WebDAV provider (through Apache)
 +
* '''Integrate Platform/Team synchronization framework''' (for minimal data transfer on sync or import/export)
 +
* Integrate TPTP agent controller (file services, launch services) as subsystems
 +
* Bridge to any registered EFS provider, making RSE an EFS Browser (Note: Can be done transparently through ECF filetransfer API. ECF filetransfer is extremely lightweight and there is an existing bridge from ECF filetransfer to EFS. ECF is graduating to 1.0 with Europa.).
 +
* Use ECF filetransfer API.  Expose/Implement RSE as new ECF filetransfer provider.
 +
* Use ECF discovery API.  Expose current zeroconf implementation as new ECF discovery provider.
 +
* Collaborate with Wicked Shell, integrating features from it
 +
* Collaborate with JArchive, providing support for more archive formats (through RSE extension point)
  
* '''Theme: Integrate other remote access solutions''' (strong should have):
+
==== '''Theme: Add unique new features''' ====
** <font color="red">Interest: Community, projects mentioned below</font>
+
* <font color="red">Interest: Broadcom, WR, IBM</font>
** <font color="blue">Contribute:</font>  
+
* <font color="blue">Contribute: Broadcom (Contribute Launch), WR (Lab Manager), IBM (IBM Contributions)</font>
** Integrate Platform/Team WebDAV provider, and/or Google SoC WebDAV provider (through Apache)
+
* Contribute Broadcom '''Launch Actions''', improve Launching as defined by the [[DSDP/TM/Launching|Launching group]]
** Integrate Platform/Team synchronization framework (for minimal data transfer on sync or import/export)
+
** Currently being discussed with Robert Norton on the dsd-tm-dev list
** Integrate TPTP agent controller (file services, launch services) as subsystems
+
** ILaunchAction may also be used for board lab hooks
** Bridge to any registered EFS provider, making RSE an EFS Browser
+
* Add hooks for '''Remote Lab Manager''' support
** Bridge to ECF fileshare providers and probably other services exposed through ECF
+
** reserve / unreserve target boards, discover target boards, vague target descriptions
** Collaborate with Wicked Shell, integrating features from it
+
** Implementation might be facilitated by ILaunchAction hooks
** Collaborate with JArchive, providing support for more archive formats (through RSE extension point)
+
* Contribute features from '''existing IBM implementations''' (need legal review):
 +
** '''User actions''' (probably replace by Command framework) - a must-have for IBM
 +
** "External Tools" remote implementation (very interesting!) - potentially consolidate into single User Actions framework
 +
** Remote Java Debug
 +
** Remote Jar Export
 +
** Export to multiple targets;
 +
* '''Wind River Target Communication Framework (TCF)'''
 +
** A lightweight plain-C portable agent
  
 
+
==== '''Theme: Multicore / Multisystem support''' ====
* '''Theme: Add unique new features'''
+
* <font color="red">Interest: WR</font>
** <font color="red">Interest: Broadcom, WR, IBM</font>
+
* <font color="blue">Contribute:</font>  
** <font color="blue">Contribute: Broadcom (Contribute Launch), WR (Lab Manager), IBM (IBM Contributions)</font>
+
* Support target groups as defined by the [[DSDP/TM/Connection Groups|Connection Groups initiative]]
** Contribute Broadcom '''Launch Actions''', improve Launching as defined by the [[DSDP/TM/Launching|Launching group]]
+
* Filters on 1st level of System View ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164807 164807])
*** Currently being discussed with Robert Norton on the dsd-tm-dev list
+
* View for working with multiple shells concurrently exists
*** ILaunchAction may also be used for board lab hooks
+
* Right now we have grouping by profiles
** Add hooks for '''Remote Lab Manager''' support
+
* Cluster definitions should be something different (being stored inside a profile)
*** reserve / unreserve target boards, discover target boards, vague target descriptions
+
* Requirements currently unclear; instead of hacking up something wrong, better have no solution
*** Implementation might be facilitated by ILaunchAction hooks
+
* PTP might come up with requirements
** Improve the '''connection data model''', being a store for IP-Xact data about hardware
+
*** remote system properties as defined by the [[DSDP/DD/Spirit|Spirit group]]
+
** Contribute features from '''existing IBM implementations''' (need legal review):
+
*** User actions (probably replace by Command framework)
+
*** "External Tools" remote implementation (very interesting!) - potentially consolidate into single User Actions framework
+
*** Remote Java Debug
+
*** Remote Jar Export
+
*** Export to multiple targets;
+
 
+
 
+
* '''Theme: Multicore / Multisystem support'''
+
** <font color="red">Interest: WR</font>
+
** <font color="blue">Contribute:</font>  
+
** Support target groups as defined by the [[DSDP/TM/Connection Groups|Connection Groups initiative]]
+
** Filters on 1st level of System View ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164807 164807])
+
** View for working with multiple shells concurrently exists
+
** Right now we have grouping by profiles
+
** Cluster definitions should be something different (being stored inside a profile)
+
** Requirements currently unclear; instead of hacking up something wrong, better have no solution
+
** PTP might come up with requirements
+
  
  
Line 129: Line 162:
 
*** Client-side patterns buried inside the jarfile --> copy it out of JAR into preferences on first start, allow users to modify through Preferences
 
*** Client-side patterns buried inside the jarfile --> copy it out of JAR into preferences on first start, allow users to modify through Preferences
  
 +
* Improve RSE '''Credentials Management'''
 +
** <font color="red">Interest:</font>
 +
** <font color="blue">Contribute:</font>
 +
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=196445 196445] The RSE Credentials Management currently uses the Eclipse Keyring, which just provides weak encryption. It should provide a credentials store similar to Firefox, which is passphrase protected and stores credentials well encrypted. It might be possible to use the Jsch mechanism for accessing stored SSH private keys, since getting strong encryption through Eclipse Legal might be problematic. Another option is using the upcoming Platform / Equinox JAAS framework.
  
 
== Archive of previous plans ==
 
== Archive of previous plans ==

Latest revision as of 23:03, 14 August 2007

< DSDP | TM

Collect input for the planning process for next year's DSDP Target Management Release (Eclipse Ganymede train, tentatively TM 3.0, June 2008) as well as the upcoming service releases (DSDP-TM 2.0.x). Goals of this page are

  • Collect ideas and Requirements for Target Management Ganymede and beyond
  • Find out who needs what features
  • Find out who would be willing to work on what

This is a collaborative Wiki, so everyone in the community is welcome to contribute to the discussion by simply modifying the page. Please sign up by declaring your interest or willingess to contribute on the individual items below. Our Themes and Priorities need to be aligned with the global and DSDP Requirements. As soon as a feature description is sufficiently clear and there is some group supporting a feature, Bugzilla entries should be used for tracking requests. When finalizing the plan, bugzilla plan items will be created for grouping related work items together in order to track them.

An initial plan was discussed in the Committer Phone Meeting on 22-May-2007.

More discussions will be at the DSDP/TM/Face-to-face Meeting Toronto 17-Sep-2007.

TM 2.0.x Planning

  • TM 2.0.1 and 2.0.2 to be aligned with Europa Simultaneous Release Service Releases in autumn and spring 08 respectively
    • No major feature additions; focus on unit tests, ISV Docs
      • Probably adding RSE Terminal integration
  • Work on unittests, isv docs over the summer can also be done in HEAD, forking off the mainline in autumn
    • if we have any large things for 3.0 and want to start before 2.0.1 might do that in a branch; but having the branch this or that way is not a big deal

TM 3.0 (Ganymede) Planning

Bugzilla Plan Input

  • Query Information
    • The following bugzilla queries cover non-overlapping distinct requests that we currently have in the queue.
    • Bugs lists are sorted by importance, with the more important ones (i.e. higher priority or severity) first.
    • Target milestone "Future" is used for bugs that have been discussed and deferred.
    • Target milestone "---" is uesd for bugs not yet analyzed or discussed.
  • Bugzilla Queries

Planning and Priorities

  • We have consensus to work towards TM 3.0 for Ganymede (rather than 2.1) so we'll allow API changes but keep them as small as possible. However, "getting things right" is agreed to be more important than being backward compatible.
  • Discussion and finalization of priorities into plan items will be at the DSDP/TM/DSDP/TM/Face-to-face Meeting Toronto 17-Sep-2007.
  • Top 10 Priorities:
    • 1 - (All) Quality, Maintenance, Reduce bug backlog. Add unit tests. Clean up old implementations, get rid of obsolete code.
      • 1a - (WR, IBM) Improve UI, Adhere to Guidelines, Better Wizard UI, Componentize connection/subsystem/services
    • 2 - (IBM, WR) Componentize: UI/Non-UI splitting, avoid unnecessary plugin activation, support RCP
    • 3 - (IBM) Team Support: Provide Import/Export of RSE Profiles by XML, provide UI for working with Profiles
    • 4 - (IBM) Contribute IBM User Action Framework
    • 5 - (WR) Contribute Target Communication Framework (TCF) Agent
    • 6 - (WR) Improve Remote CDT Launch; integrate remote CDT build
    • 7 - (WR, IBM) Improve Platform Integration: Drag&Drop (SWT:196176), Command/Handler, Avoid Platform "internal" access, keyboard shortcuts; Improve EFS; Contribute Welcome content; Credentials Management via upcoming Platform JAAS support (196445)
      • Especially driving EFS forward can be important wrt community building - discussing caching / rsync facilities for EFS
    • 8 - (WR, IBM) Finalize / Clean up APIs, making them maintainable from 3.0 without API breakage
    • 9 - (Contributors) Integrating other remote access solutions - ECF, Platform/Team Synchronization API, WebDAV, Wicked Shell, TPTP, JArchive; important for community building
    • 10 - (WR) Features for Multi-Core / Multisystem; flexible grouping of connections / items; investigate collaboration with PTP
  • "Might Have" Themes and Proposals (Interesting but probably not enough time)
    • Finalize Terminal APIs
    • Generic Filtering Framework / Generic monitoring APIs (possibly related to TCF)
    • Launch Actions
    • Remote Lab Manager Integrations
    • Shell Pattern Matching

Themes and Proposals

  • In the list of themes below, typically those themes or work items that we feel to be more important appear first. Not all items of a theme may be addressed, especially those appearing further down in the list for a theme would typically receive less attention.
  • Naturally those themes will be carried on first that have most interested parties, and where those interested parties actually contribute code, patches or committers.
  • Community members can influence the planning process by declaring their interest, and/or especially declaring their willingness to contribute work on the themes.
  • Contribute: items below do not yet indicate a committment to actually contribute but do declare willingess of the signed up parties.

Theme: Scaling Down

  • Interest: IBM, WR
  • Contribute: IBM, WR (committers)
  • Further improve UI/Non-UI splitting, supporting
    • (a) RSE as an EFS provider without having to start up
    • (b) Remote file export in headless applications
  • Improve usage of the extension registry:
    • (a) Avoid plugin startup where not necessary - improve initial startup performance
    • (b) Make plugin registration dynamic, allowing dynamic reconfiguration (registry trackers etc: might be a requirement for the future provisioning story)
  • Improve Componentization:
    • (a) Support RCP, allowing the use of RSE even if Resources do not exist
    • (b) Provide a shortcut to RSE Services layer without Subsystems - probably via OSGi Services; might help EFS provider
  • Potentially move to Platform + 0 level --> move CDT Launcher to CDT Project


Theme: Be a Better Framework

  • Interest: WR, IBM, Symbian
  • Contribute: WR, IBM, Symbian (committers)
  • Improve Quality, Maintainability, strive for small and efficient implementations
    • Most important point for IBM and WR
    • Increase Unit Test Coverage
    • Do unit tests with a GUI Recorder e.g. TPTP AGR
    • Reduce the Bug backlog
    • Collaborate with DSDP-DD and Platform/Debug for a cleaned-up SystemView solution
  • Increase the flexibility of the host/subsystem/service combination after connection creation
    • Improved more flexible wizards; allow adding and removing services as needed; Inheritable Properties for configuring subsystems
    • Improved Wizard UI (176490, 142493, 192758)
  • Better live with the Platform
  • Connection Sharing and Team Support
    • Import/Export RSE Profiles; A must-have for IBM
  • Finalize Terminal APIs
    • Contribute Terminal Userdocs and API Docs
  • Fix and Improve Drag and Drop
    • Collaborate with Platform/Common Navigator to fix PluginTransfer into the Project Explorer
    • Collaborate with Platform/SWT to fix deferred drag&drop of remote files to copy into Windows Explorer (bug 196176)
    • Improve the RSE DnD Framework to support extenders plug-in transfer types for specific objects in their own remote systems (Newsgroup: Uday Kabe, Lotus Notes
  • Provide a generic filtering framework (through OQL)
  • Improve the connection data model, being a store for IP-Xact data about hardware
  • Re-think RSE SystemMessages: Do we need XML when we have Eclipse NLS / Java MessageFormat?
    • E.g. DStore_Service_Percent_Complete_Message -- multiple transformations for substitution

Theme: Integrate other remote access solutions (strong should have)

  • Interest: Community, projects mentioned below
  • Contribute:
  • Integrate Platform/Team WebDAV provider, and/or Google SoC WebDAV provider (through Apache)
  • Integrate Platform/Team synchronization framework (for minimal data transfer on sync or import/export)
  • Integrate TPTP agent controller (file services, launch services) as subsystems
  • Bridge to any registered EFS provider, making RSE an EFS Browser (Note: Can be done transparently through ECF filetransfer API. ECF filetransfer is extremely lightweight and there is an existing bridge from ECF filetransfer to EFS. ECF is graduating to 1.0 with Europa.).
  • Use ECF filetransfer API. Expose/Implement RSE as new ECF filetransfer provider.
  • Use ECF discovery API. Expose current zeroconf implementation as new ECF discovery provider.
  • Collaborate with Wicked Shell, integrating features from it
  • Collaborate with JArchive, providing support for more archive formats (through RSE extension point)

Theme: Add unique new features

  • Interest: Broadcom, WR, IBM
  • Contribute: Broadcom (Contribute Launch), WR (Lab Manager), IBM (IBM Contributions)
  • Contribute Broadcom Launch Actions, improve Launching as defined by the Launching group
    • Currently being discussed with Robert Norton on the dsd-tm-dev list
    • ILaunchAction may also be used for board lab hooks
  • Add hooks for Remote Lab Manager support
    • reserve / unreserve target boards, discover target boards, vague target descriptions
    • Implementation might be facilitated by ILaunchAction hooks
  • Contribute features from existing IBM implementations (need legal review):
    • User actions (probably replace by Command framework) - a must-have for IBM
    • "External Tools" remote implementation (very interesting!) - potentially consolidate into single User Actions framework
    • Remote Java Debug
    • Remote Jar Export
    • Export to multiple targets;
  • Wind River Target Communication Framework (TCF)
    • A lightweight plain-C portable agent

Theme: Multicore / Multisystem support

  • Interest: WR
  • Contribute:
  • Support target groups as defined by the Connection Groups initiative
  • Filters on 1st level of System View (164807)
  • View for working with multiple shells concurrently exists
  • Right now we have grouping by profiles
  • Cluster definitions should be something different (being stored inside a profile)
  • Requirements currently unclear; instead of hacking up something wrong, better have no solution
  • PTP might come up with requirements


Other ideas carried forward

  • Improve Shell Pattern Matching on the client
    • Interest: WR, IBM
    • Contribute:
    • Allow user-defined patterns (153274)
    • Provide an extension point for patterns but not let the user edit them
    • Server-side patterns vs. client-side patterns, want to have them consistent
      • Server-side file can be modified by the users, located in dstore daemon
      • Client-side patterns buried inside the jarfile --> copy it out of JAR into preferences on first start, allow users to modify through Preferences
  • Improve RSE Credentials Management
    • Interest:
    • Contribute:
    • 196445 The RSE Credentials Management currently uses the Eclipse Keyring, which just provides weak encryption. It should provide a credentials store similar to Firefox, which is passphrase protected and stores credentials well encrypted. It might be possible to use the Jsch mechanism for accessing stored SSH private keys, since getting strong encryption through Eclipse Legal might be problematic. Another option is using the upcoming Platform / Equinox JAAS framework.

Archive of previous plans

TM 2.0 (Eclipse Europa, June 2007)


TM 1.0 (Fall 2006)

See the official TM 1.0 Project Plan for details on target environment, plans and timing.