Scope gig worker use case and its first prototype

[junszhao]

Following our discussions on 24 May, we would like to identify what kind of features that are going to provide some new additions to systems like drivers’ seats.

• Can we have all the data from other related systems? If so, how?
• We should aim for something unique and different, such as normalising this data across different work sites, enabling the communication of workers across different sites. What should this unique feature be?

Suggested timeline:

• Mid June: identify all the datasets
• End June: identify prototype timeline for a 4-week cycle
• Mid July: have the project intern start

[junszhao]

Updates from Jake and Rui

• Try to find gig worker use cases for the MPC benchmarking, such as the kind of queries they would need
  @@action to Jake: follow up with Reuben Binns for dataset access
  @@action to Jake: whether there is a need for us to set up a gig worker user study
• Discussed the data provenance and data terms of use policy, which is kind of related to the MPC planning

[jakemlstein]

On it! :). I think next week's meeting with Joe might be helpful for getting in touch with groups for potential participant recruitment.

Would want to run this by you, but I think expanding beyond just gig drivers for a user study might be interesting too -- to demonstrate in particular the variety of requirements (both in-common and context-specific among different groups).

A couple other to-dos for me Rui and I chatted about in our 1-1:
1. Generate list of metadata needed for experimentation with synthetic data via existing benchmarking design
-What are the uses/computation necessary?
-Level of complexity of operations
-Volume and burstiness of traffic
-Number of parameters
2. Mine the Privacy Policies for business logics to define the delta between corporate use and minimum viable user- organized collective use.