Labs/PAC/Psync
Status
| Profile Mediator | |
| Stage | Draft |
| Status | In progress |
| Release target | ` |
| Health | OK |
| Status note | ` |
Team
| Product manager | ` |
| Directly Responsible Individual | ` |
| Lead engineer | ` |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | ` |
Open issues/risks
- Do we provide our own profile server?
- How is caching handled?
Stage 1: Definition
1. Feature overview
It's helpful to be able to control your online identity from a central, secure location. By offering Mozilla users a Profile Mediator, they can take control of their online presence, licensing different aspects of their identity to different sites as they see fit through a single UI.
This feature will provide such an access point, allowing sites to request basic profile information such as name, picture, bio, online accounts, and more.
We will likely want to provide our own example Profile Server, which in addition to the core aspects of their profile will also house pointers to a user's various activity streams, contacts, sync data, installed apps, installed add ons, and other firefox preferences.
2. Users & use cases
- Provide a centralized personal identity access point for users and apps
- Empower users to define personal information sharing relationships with various sites
- Provide a secure, non-spoofable way to set these access preferences
- Assure users of the security of their personal data
3. Dependencies
- Extend Sync for our own implementation?
- Build off of Site-based data mangement
4. Requirements
- Refine a good set of profile data to store
- Figure out a licensing structure
Non-goals
`
Stage 2: Design
5. Functional specification
- profile.get(field[, onsuccess, onfailure])
- profile.set(field, value[, onsuccess, onfailure])
6. User experience design
- coming soon
The site-based prefs will be implemented in content at an about page (about:profile). It will be in-content (much like [about:addons]), and is intended to build off of the mechanisms of the Site-based data management UI as appropriate.
Stage 3: Planning
7. Implementation plan
- Refine the API
- Build the mediator
- Build our server/service provider
8. Reviews
Security review
`
Privacy review
`
Localization review
`
Accessibility
`
Quality Assurance review
`
Operations review
`
Stage 4: Development
9. Implementation
`
Stage 5: Release
10. Landing criteria
`
Feature details
| Priority | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| Privacy | ` | ` |
| Localization | ` | ` |
| Accessibility | ` | ` |
| Quality assurance | ` | ` |
| User experience | ` | ` |
| Product marketing | ` | ` |
| Operations | ` | ` |
