Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search

Orion/Milestone Plan/0.2

This page contains a detailed plan of what we worked on during the Orion 0.2 release.

Current Milestone

RC1: June 10

  • Minor page optimization work
  • Documentation
  • Git Reset to throw away local commit

Future Milestones

RC2: June 17

RC3: June 24

Unallocated Work

  • Enable the server to be split up across multiple processes (ex, separate search server)
  • WebDAV support to allow using existing desktop tools against files on
    • How will authentication work
  • 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

M8/RC0: June 3


  • Site configurations [blocked on absolute URL problem]
    • Enable self hosting
    • Proper handling of HTTP headers
  • Simplify server configuration (bug 336560)
  • example page for most common editor embed cases (consumability)
  • landing page and extension points for contributing tasks and primary navigation links (consumability)
  • Command framework improvements (performance and polish)
    • performance work around timing of menu population
    • ability to collect lightweight info without a dialog
  • visual styling updates and polish, icons, UI polish bugs, etc. (polish)
  • Dojo 1.6 [Simon]
    • Dojox migration
    • Doc mode changes to support IE9
  • Get documentation infrastructure in place
  • Migrate to RequireJS
  • Extension points
    • Content assist
    • Plugging in different editors
    • Keybindings
  • Git Multi-branch support


  • Concurrency work in server impl
  • Three way diff
  • Dojo theming
  • Plug-in authentication (Authorize access to plugin's services)
    • OAuth workflow
  • De-pluginify [John]
    • Merge git and file client plugins
  • User name in file URL
  • Performance
    • Convert to expire headers for static content
    • Look for other performance gains
  • Explore moving from OpenAJAX to bare PostMessage
  • Explore WebDAV
  • Investigate local storage events for notifying other pages of service changes
    • Validation/errors

M7 - April 29, 2011

  • Relicense source code
  • Git SSH authentication (using Orion with Github or
  • Git support:
    • Finish clone/config
    • Log page (show history for single file/folder)
    • Remote page: push, pull, tag, fetch
    • Support merge workflows
    • Ensure we work properly with GitHub
    • Fetching git log in pages to avoid timeout
  • Progress service
  • Project proposal
  • Dojo 1.6
    • Creating Dojo subset / CQ
  • Writable compare editor
  • Support Firebug integration
    • Reusable editor container (editor + trim + keybindings)
  • Organize/structure CSS
  • Import/Export from/to SFTP [John]
  • Extension points
    • Syntax high-lighting
    • Multiple file clients
  • Handling changed plugins
  • Timing problem between preference/service initialization (reload needed after login problem)

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