Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Higgins 1.1 Wishlist"

(Higgins Selector Switch Component)
Line 4: Line 4:
 
This page is tentative. It needs to be rationalized with the existing plan here: [[Backlog]]. If we decide to make this page authoritative, then the [[Backlog]] pages should be deleted or linked to.
 
This page is tentative. It needs to be rationalized with the existing plan here: [[Backlog]]. If we decide to make this page authoritative, then the [[Backlog]] pages should be deleted or linked to.
  
===Tentative Plan===
+
==Tentative Plan==
 
* June date - Shadow Eclipse Release train if possible
 
* June date - Shadow Eclipse Release train if possible
 
* Items are logged as  
 
* Items are logged as  
Line 10: Line 10:
 
** '''DONE''' are already or nearly completed.  
 
** '''DONE''' are already or nearly completed.  
 
** '''priority''' are high value elements, but do not necessarily have resources devoted to developing them at this time.
 
** '''priority''' are high value elements, but do not necessarily have resources devoted to developing them at this time.
 +
== Solutions ==
 +
===Client===
 +
* Getting all selector solutions to use the same [[Higgins Browser Extension]] and the [[Higgins Selector Switch]] as shown here: http://www.eclipse.org/higgins/Client-Overview-1.1.php
  
 +
===Selector Solutions===
 +
* [[AIR Client and Server 1.1]] - get all the code checked in using new AIR ICM UI in black & white
 +
* RCP - drop this for Higgins 1.1?
 +
* [[GTK and Cocoa Selector 1.0]] - need to create a 1.1 page and update architecture diagrams with new HSS, new Synchronizing Card Store, etc.
 +
* Naming of the above with common branding:  Higgins Selector for AIR, Higgins Selector for GTK - HIGH
 +
* Merging of selectors (part of Architecture Harmonization) - start moving to a common service, especially AIR and DigitalMe  - '''HIGH'''
 +
* Positioning
 +
** Higgins Selector for MacOSX (AIR or Cocoa variant) - '''HIGH'''
 +
** Higgins Selector for Windows (AIR)
 +
** Higgins Selector for Linux (GTK) - already part of SUSE
 +
== Components ==
 
===IdAS-related components===
 
===IdAS-related components===
 
* Google Contacts CP - '''HIGH'''
 
* Google Contacts CP - '''HIGH'''
Line 28: Line 42:
 
* WS-Trust 1.3 - '''HIGH'''
 
* WS-Trust 1.3 - '''HIGH'''
 
* PPID algorithm support for v1.5 - '''DONE'''
 
* PPID algorithm support for v1.5 - '''DONE'''
 
===Client===
 
* Getting all selector solutions to use the same [[Higgins Browser Extension]] and the [[Higgins Selector Switch]] as shown here: http://www.eclipse.org/higgins/Client-Overview-1.1.php
 
 
===Selector Solutions===
 
* [[AIR Client and Server 1.1]] - get all the code checked in using new AIR ICM UI in black & white
 
* RCP - drop this for Higgins 1.1?
 
* [[GTK and Cocoa Selector 1.0]] - need to create a 1.1 page and update architecture diagrams with new HSS, new Synchronizing Card Store, etc.
 
* Naming of the above with common branding:  Higgins Selector for AIR, Higgins Selector for GTK - HIGH
 
* Merging of selectors (part of Architecture Harmonization) - start moving to a common service, especially AIR and DigitalMe  - '''HIGH'''
 
* Positioning
 
** Higgins Selector for MacOSX (AIR or Cocoa variant) - '''HIGH'''
 
** Higgins Selector for Windows (AIR)
 
** Higgins Selector for Linux (GTK) - already part of SUSE
 
  
 
=== [[Higgins Selector Switch]] Component ===
 
=== [[Higgins Selector Switch]] Component ===
Line 52: Line 52:
 
* DigitalMe selector connectors (need MacOSX, Windows and Linux) - '''HIGH''' [Andy]
 
* DigitalMe selector connectors (need MacOSX, Windows and Linux) - '''HIGH''' [Andy]
  
=== New Card Types ===
+
== New Card Types ==
 
* UN/PW - '''HIGH'''
 
* UN/PW - '''HIGH'''
 
* OpenID - would be nice
 
* OpenID - would be nice
 
* R - would be nice
 
* R - would be nice
  
===Infrastructure===
+
==Infrastructure==
* Change Java version from 1.4.2 to 1.5? -Discussion followed by Doodle vote of committers - SELECTIVE
+
* Comb through [[Components]] page and correct all missing wiki pages, etc.
* Breaking every jar into its own Eclipse project (relationship to Orbit) (Mary to ask for volunteer on the list.)** Internationalization of certain CPs - done
+
** Improve [[Components]] page by showing
 +
*** Make it easy to see which component is used in 1.0, 1.1 or both
 +
*** Make it easy to see which components are building properly in the nightly build
 +
* Breaking every jar into its own Eclipse project (relationship to Orbit) (Mary to ask for volunteer on the list.)
 +
* Internationalization of certain CPs - done
 
* Evaluate how could internationalization the clients so that can outsource creating localized versions.
 
* Evaluate how could internationalization the clients so that can outsource creating localized versions.
 
* Automated testing based on buckminster builds
 
* Automated testing based on buckminster builds
 
* Paper on card-based authentication (Define card-based auth mechanism)??? where should this live, OASIS Security Services TC?
 
* Paper on card-based authentication (Define card-based auth mechanism)??? where should this live, OASIS Security Services TC?

Revision as of 21:35, 31 January 2009

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

This page is tentative. It needs to be rationalized with the existing plan here: Backlog. If we decide to make this page authoritative, then the Backlog pages should be deleted or linked to.

Tentative Plan

  • June date - Shadow Eclipse Release train if possible
  • Items are logged as
    • HIGH have high probability of being completed in upcoming sprints by June 09.
    • DONE are already or nearly completed.
    • priority are high value elements, but do not necessarily have resources devoted to developing them at this time.

Solutions

Client

Selector Solutions

  • AIR Client and Server 1.1 - get all the code checked in using new AIR ICM UI in black & white
  • RCP - drop this for Higgins 1.1?
  • GTK and Cocoa Selector 1.0 - need to create a 1.1 page and update architecture diagrams with new HSS, new Synchronizing Card Store, etc.
  • Naming of the above with common branding: Higgins Selector for AIR, Higgins Selector for GTK - HIGH
  • Merging of selectors (part of Architecture Harmonization) - start moving to a common service, especially AIR and DigitalMe - HIGH
  • Positioning
    • Higgins Selector for MacOSX (AIR or Cocoa variant) - HIGH
    • Higgins Selector for Windows (AIR)
    • Higgins Selector for Linux (GTK) - already part of SUSE

Components

IdAS-related components

  • Google Contacts CP - HIGH
  • CDM 1.1 - HIGH - Paul will do this
  • CDM Access control - priority
  • Restful Binding - priority
  • IdAS support for new CDM and initial access control - priority
  • Models as entities, especially data types - priority
  • RDF CP
  • JNDI/LDAP CP
  • Access Control CP?
  • Open Social CP
  • JDBC CP

STS-related components

  • SOAP1.2 - HIGH
  • WS-Trust 1.3 - HIGH
  • PPID algorithm support for v1.5 - DONE

Higgins Selector Switch Component

  • Versions for
    • Windows
    • Linux
    • MacOSX - HIGH
  • Merge connectors into the HSS - HIGH - [Jeesmon]
  • Windows selector connector for CardSpace and AIR - DONE
  • DigitalMe selector connectors (need MacOSX, Windows and Linux) - HIGH [Andy]

New Card Types

  • UN/PW - HIGH
  • OpenID - would be nice
  • R - would be nice

Infrastructure

  • Comb through Components page and correct all missing wiki pages, etc.
    • Improve Components page by showing
      • Make it easy to see which component is used in 1.0, 1.1 or both
      • Make it easy to see which components are building properly in the nightly build
  • Breaking every jar into its own Eclipse project (relationship to Orbit) (Mary to ask for volunteer on the list.)
  • Internationalization of certain CPs - done
  • Evaluate how could internationalization the clients so that can outsource creating localized versions.
  • Automated testing based on buckminster builds
  • Paper on card-based authentication (Define card-based auth mechanism)??? where should this live, OASIS Security Services TC?

Back to the top