CloudServices/Chronicle: Difference between revisions

mNo edit summary
(Add testing stuff.)
 
(20 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Administrivia =
* IRC channel: #chronicle
* Mailing list: [https://mail.mozilla.org/listinfo/chronicle-dev chronicle-dev]
* Source [https://github.com/mozilla/chronicle Github]
= Overview =
= Overview =
Please see [https://docs.google.com/a/mozilla.com/document/d/18DF5B-lDUnMZwjn7DNZINWQtBdVuyqS4sxGyaIY-8Vk/edit#heading=h.rgj00ytmv9g8 this GDoc] for the in-progress/working draft project summary
''Separating out Chronicle and Reading List stuff...Reading List project will live here: [[CloudServices/Reading List]]''
 
= What is it? =
Making it easier to find a site, recipe, or article that you saw before. "Never lose site again". What if we pulled together Reading List + History + Bookmarks + Social Links and presented them in a powerful way accessible from any screen?
 
= Vision =
 
= Problem we're solving =
(DRAFT - edwong wrote these)


= Current Status =
1.0
* v1 project definition and requirements underway
 
* M1: History is a long list of duplicate urls that are hard to search. Let's make this better and accessible on all my devices.
* M2: I have a bookmark or article I want to read later but I'm on an iPhone.
* M3: I want read popular articles from multiple social streams in one place (possibly seamlessly inline[task continuity]).
2.0
* M1: I'd like to share links with my contacts, possibly in real time.
* M2: I want my awesome bar to be smarter about sites I might like, look pretty, and possibly suggest things.


= Roadmap =
= Roadmap =
== Chronicle v1 (Spring 2015) ==
TBD


== Chronicle v2 (Fall 2015) ==
== Chronicle (Target Fall 2015) ==
''TBD - after v1 is defined and underway''
1.0
* M1: Make history more awesome (look and feel, search)
* M2: Integrate Reading List, History, Bookmarks
* M3: Integrate Social


= Source =
2.0 Take chronicle learnings and put them in the awesome bar.
TBD


= Project Owners =
= Project Domains =
* Cloud Services Product Manager: Bill Maggs
* Cloud Services Product Manager: Bill Maggs
* Desktop Product Manager: Bryan Clark
* Desktop Product Manager: Bryan Clark
* Mobile Product Manager: Deb Richardson
* Mobile Product Manager: Deb Richardson
* Engineering Manager:
* Tech Lead/Product Owner: Nick Chapman
* Desktop Tech Lead:
* Technical Project Manager: Edwin Wong
* Technical Project Manager:
* UX/Research Lead: John Gruen
* UX Lead:
* Dev: Jared Hirsch, Sean MacArthur
* QA/Infrastructure Lead: Peter DeHaan
 
= Product Definition =


= Product Definition =  
= Test Plans and Testing Notes =
* TODO: Nail down v1 requirements for a Spring 2015 release ([https://docs.google.com/a/mozilla.com/document/d/18DF5B-lDUnMZwjn7DNZINWQtBdVuyqS4sxGyaIY-8Vk/edit#heading=h.lgac12h0uqpw GDoc in progress])
* [[/Test Plan|Test Plan]]
* TODO: Consolidate all existing documentation, user studies & other references here.
* [[/Summary of Tests|Summary of Tests]]
* [[/Testing Notes|Testing Notes]]

Latest revision as of 21:01, 11 March 2015

Administrivia

Overview

Separating out Chronicle and Reading List stuff...Reading List project will live here: CloudServices/Reading List

What is it?

Making it easier to find a site, recipe, or article that you saw before. "Never lose site again". What if we pulled together Reading List + History + Bookmarks + Social Links and presented them in a powerful way accessible from any screen?

Vision

Problem we're solving

(DRAFT - edwong wrote these)

1.0

  • M1: History is a long list of duplicate urls that are hard to search. Let's make this better and accessible on all my devices.
  • M2: I have a bookmark or article I want to read later but I'm on an iPhone.
  • M3: I want read popular articles from multiple social streams in one place (possibly seamlessly inline[task continuity]).

2.0

  • M1: I'd like to share links with my contacts, possibly in real time.
  • M2: I want my awesome bar to be smarter about sites I might like, look pretty, and possibly suggest things.

Roadmap

Chronicle (Target Fall 2015)

1.0

  • M1: Make history more awesome (look and feel, search)
  • M2: Integrate Reading List, History, Bookmarks
  • M3: Integrate Social

2.0 Take chronicle learnings and put them in the awesome bar.

Project Domains

  • Cloud Services Product Manager: Bill Maggs
  • Desktop Product Manager: Bryan Clark
  • Mobile Product Manager: Deb Richardson
  • Tech Lead/Product Owner: Nick Chapman
  • Technical Project Manager: Edwin Wong
  • UX/Research Lead: John Gruen
  • Dev: Jared Hirsch, Sean MacArthur
  • QA/Infrastructure Lead: Peter DeHaan

Product Definition

Test Plans and Testing Notes