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

Orion/Milestone Plan

< Orion
Revision as of 11:48, 27 April 2011 by Susan franklin.us.ibm.com (Talk | contribs) (Structural Changes)

This page contains a detailed plan of what we intend to work on in the coming milestones.

Current Milestone

M7 - April 29, 2011

Planned

Self Hosting
  • Git support: [Szymon,Tomasz,Gosia]
    • Remote page: push, pull, tag, fetch [in progress]
      • fetch/merge/push server side api done, fetch/merge client done
    • Support merge workflows [in progress]
  • Site configurations [Mark] [blocked on absolute URL problem]
    • Enable self hosting
    • Proper handling of HTTP headers
  • Some issues with fetch from github
  • Timeout issues on log page - fetching entire log rather than pages
High Value Integrations
  • Import/Export from/to SFTP [John] [in progress]
  • Extension points (in order of importance) [Mark]
    • Syntax high-lighting [in progress]
  • Multiple file clients [in progress]
Structural Changes
  • Plug-in authentication (Authorize access to plugin's services) [Simon, Boris] [in progress]
    • OAuth workflow
  • Relicense source code [Boris] [in progress]
  • Eliminate unnecessary dialogs and move to more "webby" UI [Susan] [in progress, more general solution planned for M8]
  • De-pluginify [John]
    • Merge git and file client plugins
  • User name in file URL [John]
  • Migrate to RequireJS [Simon, Susan]
  • Performance [Andrew]
    • Convert to expire headers for static content
    • Look for other performance gains
  • Handling changed plugins
  • Timing problem between preference/service initialization

Committed

  • Git SSH authentication (using Orion with Github or git.eclipse.org)
  • Git support:
    • Finish clone/config
    • Log page (show history for single file/folder)
  • Progress service
  • Project proposal
  • Dojo 1.6 [Simon]
    • Creating Dojo subset / CQ
  • Writable compare editor
  • Support Firebug integration
    • Reusable editor container (editor + trim + keybindings)
  • Organize/structure CSS

Deferred

  • Concurrency work in server impl [John]
  • Three way diff
  • Extension points
    • Content assist
    • Validation/errors
    • Plugging in different editors
    • Keybindings
  • Dojo 1.6 [Simon]
    • Dojox migration
    • Doc mode changes to support IE9
  • Dojo theming

Future Milestones

M8/RC0: June 3

  • Explore moving from OpenAJAX to bare PostMessage
  • Explore WebDAV
  • Investigate local storage events for notifying other pages of service changes
  • Landing page (multiple workspaces? feeds? dashboard?)

RC1: June 10

RC2: June 17

RC3: June 24

Unallocated Work

  • Enable the server to be split up across multiple processes (ex, separate search server)
  • Navigator decorations (potentially computed server side)
  • WebDAV support to allow using existing desktop tools against files on orion.eclipse.org
    • How will authentication work
  • FTP support bug 336127
  • Gerrit integration
  • User configuration of page (ability to "show view")
  • Help/Documentation
    • Help server
    • Story for context-sensitive help
  • NLS
    • Client side
    • Server side: multi-locale
  • Firebug breakpoint integration
  • Editor theming
  • Embed Open Social gadgets?
  • Plug-in configuration
  • Project/file sharing between users

Past Milestones

M6 - March 11, 2011

  • Finish command registry [Susan]
    • "Real" story for editor actions/command contributions from another site
    • Reduce duplication in page headers, etc.
  • Cleanup basic UI layout and styling
    • Polish pass on pages, consistency, primary nav and task discovery
  • Validation of user input / prevent cross-site scripting attacks
  • Basic compare UI
  • Finish plug-in registry
  • Git Server API: clone, status, diff, index, commit, reset (unstage), add (stage)
    • Rest and Commit only operate on all staged files (JGit limitation)
  • Profile page each user can view and change their password
  • Minify Dojo
  • Extension point to enable different file systems to be used on the client
  • Site/launching support
  • Copy/move UI
  • Be able to make projects world readable (global server setting)
  • Plugins stored on server

Post 0.2

  • Roles (at least "admin" vs "user")
  • Allow admin to change authorization settings (currently vi users.xml)
  • Ability to assign specific access rights for anonymous user
  • Keybindings in pages other than the editor

Back to the top