Collect input for the planning process for Target Management 2.0 and beyond. Goals of this page are

+

<font size="-2">&lt; [[DSDP]] | [[DSDP/TM|TM]]</font>

−

* Collect ideas and Requirements for Target Management 2.0 and beyond

+

+

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

Our Themes and Priorities need to be aligned with the global and DSDP [[RequirementsCouncil06TP#Embedded_Device_Software|Requirements]].

+

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

+

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.

−

Target Management 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 plan] and the [[Europa_Simultaneous_Release#Milestones_and_Release_Candidates]].

+

An initial plan was discussed in the [[DSDP/TM/Committer_Phone_Meeting_22-May-2007|Committer Phone Meeting on 22-May-2007]].

−

== Planned Items for TM 2.0 ==

+

More discussions will be at the [[DSDP/TM/Face-to-face Meeting Toronto 17-Sep-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 and timing.

+

== TM 2.0.x Planning ==

−

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.

+

* 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

* 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]].

* 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.'''

+

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

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

** Support target groups as defined by the [[DSDP/TM/Connection Groups|Connection Groups initiative]]

+

** <font color="red">Interest:</font>

−

** Filters on 1st level of System View ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164807 164807])

+

** <font color="blue">Contribute:</font>

−

** View for working with multiple shells concurrently exists

+

** [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.

−

** Right now we have grouping by profiles

+

−

** Cluster definitions should be something different (being stored inside a profile)

+

== Archive of previous plans ==

−

** Requirements currently unclear; instead of hacking up something wrong, better have no solution

+

=== TM 2.0 (Eclipse Europa, June 2007) ===

−

** PTP might come up with requirements

+

+

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

Latest revision as of 23:03, 14 August 2007

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.

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.

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.

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

Other ideas carried forward

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.