1,007
edits
Labs/Ubiquity/Roadmap: Difference between revisions
→Ubiquity 0.7.1
| Line 105: | Line 105: | ||
A few features that didn't make it into 0.7, along with fixes for whatever the biggest bugs are that we discover after 0.7. | A few features that didn't make it into 0.7, along with fixes for whatever the biggest bugs are that we discover after 0.7. | ||
== Ubiquity 0.8: User-interface experimentation == | |||
Late Q4, 2009 | |||
This release will focus on opening up the Ubiquity user-interface to more experimentation. | |||
By rebuilding Ubiquity on top of Jetpack, so that Ubiquity and Jetpack share a common runtime, we will not only make debugging of Ubiquity much easier; we will also be able to expose the library of installed Ubiquity commands through a Jetpack API, so that others can write new interfaces to take advantage of these commands. | |||
* Ubiquity built to run on Jetpack | |||
* Commands exposed through Jetpack | |||
* Experimentation with different UI, such as always-on input field, or mouse-based UI. | |||
* Command chaining, AKA pipes between commands | |||
* Solve whatever are the most pressing usability problems discovered through Test Pilot data collection | |||
* More locales supported, more and better built-in commands | |||
== Ubiquity 1.0: A product ready for mainstream use == | |||
Early 2010 | |||
This release will focus on polish. It will not have any major new features beyond 0.8, but before a release is worthy of being called 1.0 it must be much more solid than any release we have made thus far. The built-in commands and nountypes, the security model, the user interface, and the parser must all be clean and reliable, and all remaining major bugs must be fixed. | |||
== Beyond 1.0: == | |||
Experiments in these areas can be done beyond 1.0 if there are sufficient developer resources, but they are outside the core project goals. | |||
* Weave integration | |||
* Thunderbird integration | |||
* Bespin integration | |||
== Ubiquity 1.0 == | == Ubiquity 1.0 == | ||
A Ubiquity worthy of being called 1.0 must have: | A Ubiquity worthy of being called 1.0 must have: | ||