Brainstorming ideas about how to go about launching Tomboy Online. These phases probably have some correspondence to Snowy releases.

Definitions:

• Data Consistency: Will you lose notes?

• Security: Will other users see your notes?

• Reliability: Will you be able to sync when you want, access your notes online when you want?

• Privacy: Will server admins see/use your notes?

Issues:

• Can't afford to make any guarantees, not a big company
• Can't make any promises about quality of service, no idea what server resources are required to run this
• Encrypting notes puts more strain on our limited server resources. Not encrypting them means that anyone on the sysadmin team potentially has access, and we are not a big company that screens people or has any influence over them

As the super-private alpha is already there, this an attempt at summarizing the tasks that need to be done in the near future:

Interface

• Better page to show when user can't view a note
• Notebooks UI
  • Maybe add a "notebook:" keyword to the search function?
  • Show which notebook a note is part of
  • Assign a note to a new notebook
• Consistent, awesome-looking design throughout the application

  • The ../DesignerPlayground contains some great mockups

• Design for _list pages
  • Taken from the old roadmap - is this still needed?
• Snowy Logo
• Better preferences
  • Associate multiple OpenIDs with one account
• Make as many strings as possible localizible

Under the Hood

• Fix all OpenID related bugs

• Robust HTML -> XML converter

  • U1 is using lxml to parse dirty HTML - maybe we should too?

• Markdown -> XML converter for mobile clients

  • Figure out a good way to integrate this into the API
  • Add Markdown editing capability to clients

Deployment

• Backup/Restore plans
  • Make sure data on the (semi-) public instance never gets lost - how to back up the cloud?
• Privacy Policy

Bigger Tasks (Hackfest?)

• Read/Write Sharing
  • UI - Ability to add collaborators
  • Core - Add fine-grained permission control per note
  • Automatic merging?
• Note Editor
  • Choose a good rich-text editor to costumize

  • Decide whether to do the HTML -> XML conversion on the server or on the client

Future

• Implement versioning of notes
• Be more social - multiuser collaboration
  • Editing Requests
• Sharing integration with Tomboy
  • Some kind of bar at the top of the document saying "This note is shared with..."?