Data Safety/Data Safety Consultation Meeting Notes/2012-02-14/2012-02-23

Data Safety Follow-up Meeting Details

Agenda

Items below are tracked with all Action Items related to the February Data Safety Consultation.

Not enough people on this call for a quorum. Schedule another meeting for all DS Team members.
Issue 1: Email addresses - Every badge will contain an issuee's email address as part of the data structure. BrowserID isn't the problem. Rather, there is a need for a distributed architecture for OB that has a unique identifier. We need Open Badges to think about different ways of binding a badge to the person.
- Can we do this in a way that doesn't have email addresses flying around?
- Is it possible to have badges include a hashup of email addresses instead of real email addresses? (This is the recommended approach).
Issue 2: Backpack - Mozilla will be the authoritative holder of these and we haven't done this for past projects. This may not be appropriate as a long-term plan (e.g., if there's an earthquake in the wrong place, we lose all badges). By storing the backpacks, we are making a brand promise and we need to be sure about that promise.
- Are we going to hold badges in perpetuity?
- How important is a "backpack"?
- What is the brand promise around the durability of the backpack? (Need to speak with Mark Mayo or have OB team talk with him.)
- Who is running the backpack service? (Mozilla Ops?)
- What is the current state of reviews for Security and Privacy?

David Ascher, Jishnu Menon, Alina Hua, Ben Adida

Declined
Sid Stamm, Chris Beard, Mitchell Baker, Brendan Eich, Jay Sullivan, Johnathan Nightingale, Alex Fowler