Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Website Backlog

Revision as of 10:31, 5 March 2009 by Ptrevithick.gmail.com (Talk | contribs) (Misc)

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}} This page is a catchall bin of ideas of what we COULD or MIGHT to do improve http://project-higgins.org.

What we ACTUALLY plan to do is listed here Higgins 1.1 Plan



New Downloads Organization

  • Create new download approach
    • Design new download approach to meet the needs of different "users"
      • Use the Components page as a "download index"?
      • Call out "Selected Downloads" (a few easy-to-consume solutions) vs. All downloads?
      • Take out a layer. For example, combine the page that lists all the available builds Example 1 with the page that you get when you click a build, that lists the available parts Example 2. This could be done by adding 3 additional links to each row on the first page, and eliminating the 2nd.
    • Vet download design with the dev list.
    • Develop new content required by download approach
    • Implemement new download approach - bugzilla: 218923

Misc

  • Combine volunteer and getting started material
  • Clean up website directories when are done experimenting.
  • Make the POI and other Higgins papers more visible in own section under news. Don't just bury in press releases.
  • Break Higgins based Solutions at the bottom of Solutions page into open source and commercial offerings.
  • Revise Charter and update old long description

Eclipse i-cards

  • Creation and use of "Eclipse" i-cards to build community and drive usage experience
    • Follow-up with webmaster on specifics of relationship between bugzilla and mediawiki
    • Work with ICF and community on error handling for existing MediaWiki ((*Heads up to Charles)
    • Work with ICF and community on workflow for RP's
    • Propose details of Selectors offered initially and subsequently (Hosted (FireFox or AIR), Digital Me or Higgins hosted??)
    • Also create bugzilla RP and distribute widely
    • Draft phased proposal for Eclipse (types of cards, systems)

Solutions organization

  • Higgins Client
    • Selector
      • for Andorid
      • for iPhone (experimental)
      • for Mac
        • AIR
        • Cocoa
      • for Windows
        • AIR
        • GTK
      • for Linux
        • RPM
        • Debian
    • Higgins Selector Selector (HSS)
    • Higgins Browser Extension (new multi-protocol integrated version)
      • For FF
      • For IE
      • For Safari
      • For Chrome
  • Identity Web Services
    • IdP
    • RP
    • Web Selector
  • IdAS
  • Misc
    • XDI4J

Flash

  • Create flash video(s) and make available from a link on the home page.
  • Could be several short 60-90 second ones. See two Data Portability videos, one in flash and the other in Blair Witch project style http://www.youtube.com/watch?v=TupCZY09Kwc
  • Also show at workshops, etc.
  • When the site looks good and navigates well and we have a more polished end user experience post to YouTube and blog about it.
  • Can we get Derick Ashong to star in a brief video?

Tutorials

(This is much lower priority, requires more maturity)

  • Create hands on developer tutorials (i.e. how to add Higgins to my blog, How to hook a silo site up to CloudTripper or whatever...etc.)

Bounties

  • Jazz up the request for volunteers with requests for specific bounties (when funding permits)


Done

Back to the top