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.
Difference between revisions of "Orion/Plan/3.0"
(New page: = Introduction = This document is a place to brainstorm about what we want to do in Release 3.0 The official plan document is [http://eclipse.org/projects/project-plan.php?planurl=http:/...) |
(→Git support) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 11: | Line 11: | ||
* Integration of Scripted content assist with Orion Node.js server (ongoing work from [http://camthemann.wordpress.com Cameron Mann] UCOSP Student) | * Integration of Scripted content assist with Orion Node.js server (ongoing work from [http://camthemann.wordpress.com Cameron Mann] UCOSP Student) | ||
| − | == | + | == Consumability and User Experience == |
* Further work on Projects support including RESTful APIs for consumers | * Further work on Projects support including RESTful APIs for consumers | ||
* Improved export from Orion including VMC support | * Improved export from Orion including VMC support | ||
| − | |||
| − | |||
== Infrastructure == | == Infrastructure == | ||
| Line 21: | Line 19: | ||
== Git support == | == Git support == | ||
| + | * Git support on Node.js server | ||
| + | |||
| + | The Orion Java server was always intended as a demo server and not something that scales up to very large scale demand. The current server is able to handle the load on orionhub where there are 5-10K accounts and no more than 100 concurrent users. We need to investigate and start working on what is required to make this a truly scalable server. For more details see [[Orion/Plan/3.0/Server scalability]]. | ||
== Others? == | == Others? == | ||
Latest revision as of 10:34, 4 April 2013
Contents
Introduction
This document is a place to brainstorm about what we want to do in Release 3.0
The official plan document is here.
Themes
Most of the work in Orion should fall under some agreed upon themes for the release. This is a working list of ideas. If some themes can be coalesced into others that is fine. To start this is a fairly large list which needs to be prioritized.
Language Tooling
- Integration of Scripted content assist with Orion Node.js server (ongoing work from Cameron Mann UCOSP Student)
Consumability and User Experience
- Further work on Projects support including RESTful APIs for consumers
- Improved export from Orion including VMC support
Infrastructure
- Node or NPM features from Orion Java server to facilitate Node.js app development
Git support
- Git support on Node.js server
The Orion Java server was always intended as a demo server and not something that scales up to very large scale demand. The current server is able to handle the load on orionhub where there are 5-10K accounts and no more than 100 concurrent users. We need to investigate and start working on what is required to make this a truly scalable server. For more details see Orion/Plan/3.0/Server scalability.