[Design] summary of workflow for sharing data for instrumentation

[Ashkan Soltani]

Hey guys

After a few discussions on the best way to implement the  
instrumentation piece, Mimi and I have come up with the following  
workflow for sharing user-behavior data:

1) The user will download the app as normal.

2) Chandler will automatically begin logging specific user actions  
such as 'switching collections' or 'changing application areas' to a  
logfile (currently /var/tmp/chandler-instrumentation.log) using the  
built-in python system logger.

3) After a specified amount of time (TBD, but lets say 1 week), a  
Calendar event will display a notification dialogue saying:
+ We would like to collect some data
+ Who we are and why we want the data (i.e to help design the  
direction that the product will take)
+ A summary of the data that we're collecting with some examples
+ A 'See more' option to allow the user to see their activity log on  
the local system

4) User will then have the option to 'Share this data' with us (OSAF).
4a) No.  Deletes existing logfile, turns off logging (with a possible  
test-menu option to turn it back on in the future?)
4b) Yes.  Displays the EULA, schedules a recurring automatic  
background http upload to the osaf webservers.

Notes:
+ Upload mechanism will be HTTPS upload if supported, otherwise we  
will figure out a way to encrypt/obfuscate the data
+ The files will be received on the OSAF webservers via some a cgi  
script (TBD)
+ HTTP upload will fail quietly if HTTP access/network access is not  
available

Thats the quick outline.  Let me know if there are any thoughts/ 
questions
-a


On Jul 5, 2006, at 3:03 PM, Mimi Yin wrote:

> 1. Download the app
> 2. Logging stuff to some file
> 3. Calendar: we want to know more about you, is it okay to share  
> this information? EULA.
> + Who we are and why we want you data.
> + Summary of data that we're collecting: insert some examples.
> + See more option to view actual log.
> 4. Yes or No to share.
> 4a. No. Deletes log file. Turns off logging.
> 4b. Yes. Schedules automatic background upload. (Warn them that  
> it's automatic.)
>
> Points of failure:
> + No HTTP access
> + Never logs onto internet
> + SMTP? is an option.
>
> ===
>
> Aggregates made available publicly.
> Graph the aggregates.
>
>