Raindrop/Milestone Planning

From MozillaWiki
Jump to navigation Jump to search

Milestones

Planning area for different milestones. Milestones are a few weeks long and are named after trees. These milestones are for the "Hosted Goal" described more.

Hosted Goal

Our Q2 goal for Raindrop is having a hosted Raindrop that is in restricted Alpha. The goal of this hosted version is to get feedback on the design. It will be a very experimental alpha, users should expect volatile behavior.

User reqs

  • Only one gmail account and one twitter account allowed to be registered.
  • Firefox or Webkit desktop browser only.
  • English only.

Explicit non-goals

  • Contact/relationship design will likely not be included. We probably need feedback/metrics from initial alpha before doing this.
  • No tagging.
  • No full text search. Push off to google if possible.
  • If we have time, do reply/compose. If it has bugs or is not designed well then that is a problem. It will likely not be included. When the work is done, this is the order of importance:
    • Twitter stuff first.
    • Email, plain text
    • Email fancy style.
  • No mobile, strictly desktop browser.
  • Developer tools will not be improved, the goal is for design feedback. But we should invite developers so they can try it and get interested in the code.

High level pieces

  • Web site describing the hosted offering. Point users to the blog for news. It will not take requests for invites. Rafael?
    • See Weave project for possible templates on privacy/terms of use etc...
  • Invite system: Only do it by hand, we choose the people manually. Need to work with Gozer on how to tie invite links to people's accounts. Gozer?
  • Invite link goes to the Account page. Restrict account setup to the invite email name.
  • Account page. Needs the following: Bryan?
    • Security
      • Not for sensitive materials. We will do our best but this is an Alpha. Link to tech on a wiki page.
    • Explanation
      • What Raindrop can do (mostly read-only for now)
      • What is required of you
        • Participate, File Issues, Look for problems in layout and rendering
          • You can file new ideas but we're looking for what isn't working, not what isn't there
      • Last N days of email only (explain that in explanation).
    • Accounts
      • Enter Account here and here. You may delete them later
    • Only Gmail, twitter one account each.
    • "We'll email you when its ready" - no waiting UI is needed.
      • Check your email in a couple minutes when we are ready
  • Send email when the run-raindrop is done! Mark?
    • When run-raindrop runs, at the end of each run, check for a rd.last_sync schema.
    • If that schema does not exist, write it with the current time stamp and send email using the gmail credentials for the user. So the user ends up getting an email from themself.
    • If that schema already exists, update the timestamp and do not send email.
    • Ideally the email should look good in raindrop -- it is likely to be the first message they see when the come to raindrop. Maybe something that is a "Welcome to Raindrop" message with an embedded youtube/vimeo URL, and in Raindrop they see it as an inline video.
  • User comes back, sees metrics participation screen (disable checkbox for this alpha)
    • Add explanation that in the Alpha phase you are required to participate in the metrics or you should delete your account
  • Inflow experience (see below)
  • Ability to delete an account via Account page. James/Mark/?
    • Explain that will do our best to delete all traces of your data, however this is alpha software and there are no guarantees. Remember that from when you signed up?

Inflow

Move to bulk needs polish

  • Remove the ( Not Personal ) button
    • Create a new popup/dropdown menu and add a ( Move to Bulk ) action
  • We should animate the removal of a group of messages to bulk
    • Animate messages leaving Inflow
    • Ensure we don't have lots of empty white space
    • Animate a new bulk box appearing
  • Add a "[x] Deliver to Bulk" option to our People / Address view

Archive, Delete, and other actions

  • Archive & Delete
    • Needs testing that they actually still work
    • Buttons should move to the upper right corner of a listed conversation
    • Conversations should be removed quickly through a slideup animate and the next conversation should appear under the mouse
  • Open Button
    • Should be removed
    • Links inside the message should no longer be linkified
    • Clicking on the message text or subject should open the mail
  • An "other actions" menu button can be placed at the current bottom left hand corner for holding conversation actions like "Move to Bulk" or "Mute"

Attachments

  • Clean up what we have
    • Create the following attachment type handlers
      • Video Link Attachments
        • Examples: YouTube, Vimeo
        • Thumbnail, Title, ByUser
      • Image Link Attachments
        • Examples: Flickr
          • Thumbnail, Title, ByUser
        • Example: Twitpic
          • Thumbnail
      • Expanded Link Attachments
        • Example: Bit.ly
          • Title, LongURL, ByUser
      • Image File Attachments
      • Document File Attachments
  • It should be trivial for a developer to create a new backend data miner extension in a certain format so their attachments automatically show up in our default attachment type handlers
    • What needs to be done for this?
  • We should be able to focus on this item when talking to developers about getting new data miners created

Search / Find

much of this is following a ubiquity style design

  • More Polished Search Entry
    • Should look like a "Starting Point" and not just an input box for search
  • onFocus / onClick should open a larger popup for search,browse,and auto-complete

sketch of design

Security

Still mostly unknown, need to work out soon since it impacts design.

Since we need to store some passwords, then do not worry about using OAuth for twitter, just to cut down on the work, but favor OAuth in the future.

Still may use OAuth support in couch to secure the specific requests to the server. Maybe we can use the OAuth token for a "master password" for use in encryption?

Operations

What pieces of software/servers are needed? Gozer to flesh out.

Random Notes

  • Refresh / Send / Receive UI
  • Be clear about security
    • read / write access of messages
    • how we store passwords
  • Get Satisfaction Integration
    • How to Leave Feedback?
    • How to lookup a parson's CouchDB
      • Show unique ID on the GS view
  • What Metrics will we need?
    • Attachments
      • Types
      • Count
      • From (tweet, email)
    • Mailing Lists
    • types of list - list-unsubscribe, list-id
  • Message from a New Contact
Retrieved from "https://wiki.allizom.org/index.php?title=Raindrop/Milestone_Planning&oldid=196037"