Raindrop/Milestone/Sequoia: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(21 intermediate revisions by 3 users not shown)
Line 1: Line 1:
Milestone end date '''TBD'''?
Milestone end date '''March 11th 2010'''
 
Primary goals: reduce the big risks of hosting Raindrop:
* Platform Costs (performance/hosting costs)
* User Experience
 
How to get there for both items?
* Bootstrap hosted version for dogfooding by team
* Set performance goals
* Measure current version
* Build in feedback loop
* Use measured data to do changes


== Host Bootstrap for Dogfooding ==
== Host Bootstrap for Dogfooding ==


* Breaking out APIs '''Mark and Gozer'''
* Blocking
* Optimization build for browser code '''James'''
** <strike>Basic Auth protected access '''Gozer'''</strike>
* OpenID for front door auth '''Gozer
** Protection of backend credentials ''saved to a file at minimum'' '''Mark/James/Gozer'''
* OpenID-based auth UI '''Andy and James'''
*** Discussed API  '''Mark/James/Gozer'''
* Protection of backend credentials '''Gozer'''
*** Mark in progress of converting backend to not read accounts  '''Mark'''
* Compose capability, call out to GMail/Twitter? '''Bryan/Andy for buttons, James for behavior'''
**** Expected front end fallout  '''James'''
 
** <strike>Examine Account Info Page to ensure it is still correct '''Andy and James'''</strike>
== Performance Goals ==
** <strike>SSL '''Gozer'''</strike>
 
** Restore attachments in the inflow '''James'''
=== Platform ===
* Necessary
* Load initial UI under 2 seconds
** <strike>OpenID for front door auth '''Gozer'''</strike>
* Each API call under 2 seconds
** <strike>OpenID driven access-control '''Gozer'''</strike>
* Expand group widget, 1 second
** <strike>OpenID-based auth UI '''Andy and James'''</strike>
* View conversations for a group (like mailing lists) 2 seconds
** Breaking out APIs '''Mark and Gozer'''
* Time to process a message after fetching from message provider?
** Optimization build for browser code '''James'''
* Come up with a cost per user per month target. May need real data first.
* Wanted
 
** Compose capability '''Andy designs/James for behavior'''
=== User Experience ===
*** <strike>GMail</strike>
* Sense of relief?
**** <strike>Create a compose button in UI</strike>
* Be able to use on daily basis?
**** <strike>Open a new GMail Compose window</strike>
* Ease of processing new mail?
*** Twitter
 
**** Create our own compose entry in UI
== Measure Current Version ==
** Reply capability '''Andy designs/James for behavior'''
 
*** GMail
=== Platform ===
**** Simple inline reply text boxes working again
* Measure cost of running Jean's account '''Gozer'''
**** Possibly hand off other reply / forward functions
* Disable/enable some features/extensions to see the effect on cost '''Mark to expand?'''
*** Twitter
 
**** Simple inline reply text boxes working
=== User Experience ===
**** Retweets?
* List out the broken pieces, things that must be working to get outside people to try limited experience test. '''Bryan and Andy'''
**** Faves?
 
** Baseline benchmarks '''Gozer'''
== Feedback Loop ==
 
=== Platform ===
 
* As we do changes, how do we measure increase in performance/affect on per user cost? '''Mark/Gozer'''
 
=== User Experience ===
* Identify up to 10 people for initial feedback test?
* How to to set the tone for the feedback?
* How to collect the feedback?
* How to feed new "tests" to the initial users?


== Changes Based on Measurements ==
== Hosted Raindrops For Guinea Pigs  ==


This section is likely to be filled in later after we have more data, maybe as part of another milestone. Some initial thoughts from Bryan (but need real data to confirm effectiveness):
: ''This section is only notes for reference about the next milestone but does not indicate the actual milestone requirements''


* From Bryan: put summary docs in a different DB, and use custom views on it, to replace the API layer. Benefits, easier to play with for developer writing front end extensions, may help performance?
* Blocking
* Reduce the flexibility of the backend schemas.
** OAuth for Mail Accounts '''Mark/James'''

Latest revision as of 21:23, 12 March 2010

Milestone end date March 11th 2010

Host Bootstrap for Dogfooding

  • Blocking
    • Basic Auth protected access Gozer
    • Protection of backend credentials saved to a file at minimum Mark/James/Gozer
      • Discussed API Mark/James/Gozer
      • Mark in progress of converting backend to not read accounts Mark
        • Expected front end fallout James
    • Examine Account Info Page to ensure it is still correct Andy and James
    • SSL Gozer
    • Restore attachments in the inflow James
  • Necessary
    • OpenID for front door auth Gozer
    • OpenID driven access-control Gozer
    • OpenID-based auth UI Andy and James
    • Breaking out APIs Mark and Gozer
    • Optimization build for browser code James
  • Wanted
    • Compose capability Andy designs/James for behavior
      • GMail
        • Create a compose button in UI
        • Open a new GMail Compose window
      • Twitter
        • Create our own compose entry in UI
    • Reply capability Andy designs/James for behavior
      • GMail
        • Simple inline reply text boxes working again
        • Possibly hand off other reply / forward functions
      • Twitter
        • Simple inline reply text boxes working
        • Retweets?
        • Faves?
    • Baseline benchmarks Gozer

Hosted Raindrops For Guinea Pigs

This section is only notes for reference about the next milestone but does not indicate the actual milestone requirements
  • Blocking
    • OAuth for Mail Accounts Mark/James
Retrieved from "https://wiki.allizom.org/index.php?title=Raindrop/Milestone/Sequoia&oldid=208001"