Difference between revisions of "TM Future Planning"

From Eclipsepedia

Jump to: navigation, search
(TM 2.0.x Planning)
 
(47 intermediate revisions by 4 users not shown)
Line 1: Line 1:
Collect input for the planning process for RSE 2.0. Goals of this page are
+
<font size="-2">&lt; [[DSDP]] | [[DSDP/TM|TM]]</font>
* Collect ideas and Requirements for RSE 2.0
+
 
 +
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 needs what features
 
* Find out who would be willing to work on what
 
* Find out who would be willing to work on what
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.  
+
'''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 [[RequirementsCouncil06TP#Embedded_Device_Software|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.
  
RSE 2.0 will be released with Eclipse 3.3 - presumably end of June 2007. See the [http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_3.html Eclipse 3.3 draft plan]. Rough timeline:
+
An initial plan was discussed in the [[DSDP/TM/Committer_Phone_Meeting_22-May-2007|Committer Phone Meeting on 22-May-2007]].
* Sept. 27, 2006 (RSE 1.0 Release Review) - Requirements Gathering complete
+
* Oct. 20, 2006 (RSE 1.0 release) - Draft plan with timeline available, 6-week milestones start
+
* March, 2007 - API Complete / API Freeze
+
* April, 2007 - Feature Complete / Testing begins
+
* June, 2007 - 2.0 release with Eclipse 3.3
+
  
== Planned Items ==
+
More discussions will be at the [[DSDP/TM/Face-to-face Meeting Toronto 17-Sep-2007]].
* (IBM) Add User Actions
+
* (IBM) Add Import/Export Facility
+
* (WR) Add Terminal View ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=152826 bug 152826])
+
* (Symbian) Add Discovery
+
  
== Themes and Priorities ==
+
== TM 2.0.x Planning ==
Our Themes and Priorities need to be aligned with the global and DSDP [[RequirementsCouncil06TP#Embedded_Device_Software|Requirements]]
+
  
* (Interest: WR) '''Adopt Platform Changes''' - RSE should adopt Eclipse Platform concepts wherever possible. For instance:
+
* TM 2.0.1 and 2.0.2 to be aligned with [[Europa Simultaneous Release]] Service Releases in autumn and spring 08 respectively
** Adopt '''ICU4J''' and '''Capabilities''' (needed for Europa)
+
** No major feature additions; focus on unit tests, ISV Docs
** Use '''Common Preferences for ssh and Proxy''' - Collaborate with Platform/Team on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=119278 bug 119278]
+
*** Probably adding RSE Terminal integration
** Use Common Navigator for the Remote Systems View - Platform/Team Remote Explorer [https://bugs.eclipse.org/bugs/show_bug.cgi?id=138583 bug 138583]
+
* Work on unittests, isv docs over the summer can also be done in HEAD, forking off the mainline in autumn
** Adoption of new Platform APIs from 3.2 -- these include the Commands framework, field assist, SWT column sort indicators,etc. In 2.0, we should step up to the latest APIs, e.g. support Content Assist for Remote Search / Regular Expression field
+
** 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
** Clarify Usage / Adoption of EFS
+
** Use existing Platform Extension Points for popup menus, property pages etc.
+
** Integrate Content Types / RSE File Types
+
  
* (Interest: WR) '''Optimize APIs - Remove obsolete API'''. RSE APIs should be made smaller (less API, more internal) in order to make them easier to understand and maintain. Eliminate dead code. Clarify threading model.
+
== TM 3.0 (Ganymede) Planning ==
** e.g. get rid of rseConfigDefaults extension point - use plugin_customization.ini
+
** e.g. get rid of dynamicPopupMenuExtensions, popupMenus extension points - use Platform commands, expression language
+
** e.g. passwordPersistence vs. keystoreProviders extension points
+
** e.g. propertyPages extension point - use Platform propertyPages?
+
** e.g. get rid of systemtype extension point -- use systemType instead
+
  
* (Interest: WR) '''Further UI/Non-UI Refactoring''' - RSE code should be further refactored to split UI from non-UI parts. A Headless Eclipse should be able to perform Launches through RSE-provided services / subsystems.
+
=== Bugzilla Plan Input ===
  
* (Interest: Symbian) Add '''Autodetect''' as defined by the [[DSDP/TM/Autodetect|Autodetect group]] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140320 bug 140320], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=142493 bug 142493]
+
* 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
 +
** 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] (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] (108 bugs on 10-Jul-2007)
  
* (Interest: WR) Add a '''Terminal View''' with Terminal Emulation (in addition to the current Commands view)
+
=== 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 ([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
  
* (Interest: WR) Integrate improved '''Launching''' as defined by the [[DSDP/TM/Launching|Launching group]]
+
=== Themes and Proposals ===
  
* (Interest: IBM) Add not-yet-ported features from RSE 7.0
+
* 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.
** User Actions
+
* Naturally those themes will be carried on first that have most interested parties, and where those interested parties actually contribute code, patches or committers.
** Compile Commands
+
* '''Community members can influence the planning process by declaring their interest, and/or especially declaring their willingness to contribute work on the themes.'''
** Import/Export
+
* <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.
  
* Support '''Shell Pattern Matching''' on the client
+
==== '''Theme: Scaling Down''' ====
** Support pattern matching, compiler error navigation and code completion in ssh shells and any other contributed shells, by moving corresponding code from the dstore remote side to the local client side
+
* <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
  
* (Interest: WR) Add '''Multicore / Multisystem capabilities''' to the RSE Tree
 
** Support target groups as defined by the [[DSDP/TM/Connection Groups|Connection Groups initiative]]
 
  
* (Interest: WR) Define a standard for remote system properties as defined by the [[DSDP/DD/Spirit|Spirit group]] - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=146090 bug 146090]
+
==== '''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'''
 +
** 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 ([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])
 +
* '''Better live with the Platform'''
 +
** Make use of the Platform Command/Handler framework, including parameterized handlers, to all user-defined keyboard shortcuts, extender modifiable UI and macro recording (eventually)
 +
** Contribute Welcome content, http://www.eclipse.org/eclipse/platform-ua/documents/intro_3_3_features.html
 +
** Get rid of Platform Discouraged access ("internal")
 +
* '''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 ([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
  
* (Interest: Symbian, WR) RSE should be more service-oriented - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150498 bug 150498]
+
==== '''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: Add unique new features''' ====
 +
* <font color="red">Interest: Broadcom, WR, IBM</font>
 +
* <font color="blue">Contribute: Broadcom (Contribute Launch), WR (Lab Manager), IBM (IBM Contributions)</font>
 +
* Contribute Broadcom '''Launch Actions''', improve Launching as defined by the [[DSDP/TM/Launching|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''' ====
 +
* <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
 +
 
 +
 
 +
=== Other ideas carried forward ===
 +
 
 +
* Improve '''Shell Pattern Matching''' on the client
 +
** <font color="red">Interest: WR, IBM</font>
 +
** <font color="blue">Contribute:</font>
 +
** Allow user-defined patterns ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153274 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'''
 +
** <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 ==
 +
=== TM 2.0 (Eclipse Europa, June 2007) ===
 +
 
 +
* See the [http://www.eclipse.org/dsdp/tm/development/tm_project_plan_2_0.html official TM 2.0 Project Plan] for details on target environment, plans and timing.
 +
* See bugzilla [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&keywords_type=allwords&keywords=plan&classification=DSDP&product=Target+Management&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit&order=Assignee plan items] for latest status of items.
 +
* See the [[Europa Simultaneous Release]] page for coordinated release issues.
  
* 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
 
  
* Improve the '''default Persistence Provider'''
+
=== TM 1.0 (Fall 2006) ===
** Associate connections, profiles, filter pools etc. with projects
+
** Store as normal XML files in the workspace, get rid of the RemoteSystemsConnections project (just like Launch Configs!)
+
** Use fewer files for storage (improved performance, easier handling for checkin/checkout of team-shared data) - e.g. collapsing Property files by putting the current "directory" path into the Properties Key
+
  
* Extension point / API to add systemTypes dynamically?
+
See the [http://www.eclipse.org/dsdp/tm/development/tm_project_plan_1_0.html official TM 1.0 Project Plan] for details on target environment, plans and timing.

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.

Contents

[edit] 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

[edit] TM 3.0 (Ganymede) Planning

[edit] 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

[edit] 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

[edit] 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.

[edit] 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


[edit] 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

[edit] 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)

[edit] 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

[edit] 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


[edit] 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.

[edit] Archive of previous plans

[edit] TM 2.0 (Eclipse Europa, June 2007)


[edit] TM 1.0 (Fall 2006)

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