1,007
edits
Labs/Ubiquity/Roadmap: Difference between revisions
Jump to navigation
Jump to search
→Ubiquity 0.6
No edit summary |
|||
| Line 61: | Line 61: | ||
== Ubiquity 0.6 == | == Ubiquity 0.6 == | ||
After the deep infrastructure work of 0.5, we need to focus on turning the new power of the platform into tangible benefits for the end-user. That means improving the implementation of the standard feed commands for better stability and functionality, plus expanding the range of commands available, and attempting to expand the size of our user base. | |||
Around this time, the Test Pilot project will have produced a usable set of policy guidelines for collecting data without compromising user privacy. These guidelines will be implemented in 0.6 so that we can start collecting usage data that we can use to scientifically improve the usability of Ubiquity from here on. | Around this time, the Test Pilot project will have produced a usable set of policy guidelines for collecting data without compromising user privacy. These guidelines will be implemented in 0.6 so that we can start collecting usage data that we can use to scientifically improve the usability of Ubiquity from here on. | ||
* Instrument Ubiquity for data collection according to Test Pilot standards. | * Instrument Ubiquity for data collection according to Test Pilot standards. | ||
* Improvements to standard feed commands and their documentation | * Improvements to standard feed commands and their documentation; more new commands. | ||
* New and better default skin; Better graphics for user interface. | * New and better default skin; Better graphics for user interface. | ||
* Localization gets wider and deeper: More locales supported; make nountypes localizable; look into distributing localization so that a command feed can be localized independently from its creator. | * Localization gets wider and deeper: More locales supported; make nountypes localizable; look into distributing localization so that a command feed can be localized independently from its creator. | ||
| Line 73: | Line 73: | ||
=== Community Building after 0.6 === | === Community Building after 0.6 === | ||
We should have a contest to write the best Ubiquity command -- the most useful, most innovative, and best implemented commands that conform to our human interface guidelines will be rewarded with publicity, swag, and possible uplift into standard feeds to be included by default with future versions. | We should come up with metrics to estimate the size of our user base, and set targets for the number of users we would like to have. With the higher quality of the standard commands that will be emphasized in 0.6, it will be easier to reach new users. | ||
Increasing our user base will increase our command developer base as well as our command subscriber base, and allow us to make more realistic explorations of the scaling effects that start to affect security and trust when the network grows past critical mass. For instance, I am not aware of anyone having yet attempted to write a malicious Ubiquity command. I'm sure this is mostly because the user base is too small to be worth targeting. As the user base grows, it becomes inevitable that someone will attempt to attack our users using a malicious command. Thus, growing the community is an opportunity to test out the web-of-trust security model. | |||
We should take a hint from the "Extend Firefox" contests and run a contest to write the best Ubiquity command -- the most useful, most innovative, and best implemented commands that conform to our human interface guidelines will be rewarded with publicity, swag, and possible uplift into standard feeds to be included by default with future versions. | |||
== Ubiquity 0.6.1 == | == Ubiquity 0.6.1 == | ||