Raindrop/Milestone Planning

Milestones

Planning area for different milestones. Milestones are a few weeks long and are named after trees.

• Yew
• Douglas Fir
• Wattle (Completed, but not yet tagged)
• Maple (Completed)

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 now that means getting Raindrop to run on a hosted service in the cloud.

Grouping milestone work into the following three goals will get us there:

• Emotional feeling of better organization: Make sure the experience gives the user a sense of relief via easy setup and automatic filtering/grouping done for the user.

• Dog Food: The inflow app should be usable by all the team members on a day-to-day basis.

• Cloud enabled: Raindrop is runnable in the cloud, with clear instructions on how to set it up to make it secure. The goal is not to host Raindrop on Mozilla Messaging services, but make it easy for users or ISPs to run Raindrop on their own servers.

The following section is where we can group tasks that follow under one of the three goals above. For each milestone, we should pick items from the current goal.

Codes:

• BE: Back End (platform)
• FE: Front End (platform)

Emotional feeling of better organization

• Design: Specific group widgets
• Good defaults for triaging
• Ability to do "Don't want this in my inflow".
• Tracking people and relationships.
• Complete the move to the server web API, remove old JS code.
• run-raindrop.py to go away, controlled by front end.

Dog Food

• reply
• archive/delete
• new message
• FE: Developer tools
  • Server API inspector
  • In-page code inspector: show widgets and their properties.
  • Improved extension editor that allows HTML/CSS/JS.
• FE: implement JSDoc comments to allow for API documentation.
• Implement twitter sending/more twitter APIs so people can make their own twitter web app?
• Stronger guarantees on message authenticity?

Cloud Enabled

• New web-based account setup based on the security model, ideally something suitable for a hosted environment, but not required.
• 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.
• Cloud images for Raindrop: Amazon image, others?
• Extension sharing model.
• More mobile work? A code prototype?