Services/Sync/Push to device: Difference between revisions

Jump to navigation Jump to search
m
move ops review to proper section
(add unknown ops lead)
m (move ops review to proper section)
Line 15: Line 15:
|Feature qa lead=Tracy Walker
|Feature qa lead=Tracy Walker
|Feature ux lead=Alex Faaborg
|Feature ux lead=Alex Faaborg
|Feature product marketing lead=Jaclyn Fu
|Feature operations lead=UNKNOWN
|Feature operations lead=UNKNOWN
|Feature product marketing lead=Jaclyn Fu
|Feature additional members=Ibai Garcia (SUMO)
|Feature additional members=Ibai Garcia (SUMO)
}}
}}
Line 67: Line 67:
Some questions may require separate answers for separate form factors.
Some questions may require separate answers for separate form factors.
|Feature privacy review=Since the feature is utilizing Sync, all data will be encrypted on the client side and stored on Mozilla's servers such that Mozilla cannot decrypt the data.
|Feature privacy review=Since the feature is utilizing Sync, all data will be encrypted on the client side and stored on Mozilla's servers such that Mozilla cannot decrypt the data.
|Feature operations review=A new server-side collection will be introduced, *sendtab*. Do we need to define collection in Sync Server/MySQL? How much storage are we expecting it to utilize? What should the record TTL be?
|Feature implementation notes=The feature can basically be boiled down to the following actions/functions:
|Feature implementation notes=The feature can basically be boiled down to the following actions/functions:


Line 93: Line 94:
|Feature engineering status=Blocked on UX implementation
|Feature engineering status=Blocked on UX implementation
}}
}}
*Need ops review
** will be introducing new collection on server for tab state
** do we define collection on server?
** how much storage do we expect?
canmove, Confirmed users
409

edits

Navigation menu