Raindrop/Milestone Planning: Difference between revisions
< Raindrop
Jump to navigation
Jump to search
(Created page with 'Planning area for different milestones. Milestones are a few weeks long and are named after trees. * Maple') |
No edit summary |
||
| Line 1: | Line 1: | ||
Planning area for different milestones. Milestones are a few weeks long and are named after trees. | == Milestones == | ||
Planning area for different milestones. Milestones are a few weeks long and are | |||
named after trees. | |||
* [[Raindrop/Milestone/Maple|Maple]] | * [[Raindrop/Milestone/Maple|Maple]] | ||
== Backlog == | |||
This is a sketchpad area where we can list out things we want to do that have not been slotted into a milestone yet. | |||
'''Do not''' assume anything listed here will actually be done. It is more of a planning area, and the list will change drastically over time. | |||
When choosing items for the next milestone, focus on items that will help Raindrop develop a significant market presence. Right that means getting Raindrop to run on a hosted service in the cloud. | |||
Codes: | |||
* BE: Back End (platform) | |||
* FE: Front End (platform) | |||
=== Backlog === | |||
* Security: investigate CouchDB OAuth to restrict access to the couch to only authorized users. | |||
* Security: set up secure storage and use of credentials to message service providers. | |||
* BE: Implement confidences to allow multiple extensions to override/cooperate on a specific schema. | |||
* BE: Provide a way to roll back extension changes that affect a common schema. For instance, if two schemas modify rd.msg.body, then have a way to roll back one of them and the subsequent schemas generated from rd.msg.body and re-run the dependent extensions based on the new version of rd.msg.body. | |||
* New web-based account setup based on the security model, something suitable for a hosted environment. | |||
* Cloud images for Raindrop: Amazon image, others? | |||
* FE: Developer tools | |||
** Server API inspector | |||
** In-page code inspector: show widgets and their properties. | |||
** Improved extension editor that allows HTML/CSS/JS. | |||
* Extension sharing model. | |||
* FE: implement JSDoc comments to allow for API documentation. | |||
Revision as of 21:31, 9 November 2009
Milestones
Planning area for different milestones. Milestones are a few weeks long and are named after trees.
Backlog
This is a sketchpad area where we can list out things we want to do that have not been slotted into a milestone yet.
Do not assume anything listed here will actually be done. It is more of a planning area, and the list will change drastically over time.
When choosing items for the next milestone, focus on items that will help Raindrop develop a significant market presence. Right that means getting Raindrop to run on a hosted service in the cloud.
Codes:
- BE: Back End (platform)
- FE: Front End (platform)
Backlog
- Security: investigate CouchDB OAuth to restrict access to the couch to only authorized users.
- Security: set up secure storage and use of credentials to message service providers.
- BE: Implement confidences to allow multiple extensions to override/cooperate on a specific schema.
- BE: Provide a way to roll back extension changes that affect a common schema. For instance, if two schemas modify rd.msg.body, then have a way to roll back one of them and the subsequent schemas generated from rd.msg.body and re-run the dependent extensions based on the new version of rd.msg.body.
- New web-based account setup based on the security model, something suitable for a hosted environment.
- Cloud images for Raindrop: Amazon image, others?
- FE: Developer tools
- Server API inspector
- In-page code inspector: show widgets and their properties.
- Improved extension editor that allows HTML/CSS/JS.
- Extension sharing model.
- FE: implement JSDoc comments to allow for API documentation.