Mozillians/Phonebook/Services: Difference between revisions

Jump to navigation Jump to search
 
(20 intermediate revisions by the same user not shown)
Line 5: Line 5:
* Single contributor profile across all of Mozilla.org
* Single contributor profile across all of Mozilla.org
* Standardize, Standardize, Standardize
* Standardize, Standardize, Standardize
* Simple and High Relevant First
* Simple Use Cases First


== Features ==
== Features ==
* [http://www.flickr.com/photos/aakashhdesai/8026977545 User Privacy Settings]
=== Mozillian Passport ===
=== Mozillian Passport ===
Users can opt-out to allow community sites to authorize and auto-populate their Mozilla Connect information and contributor level to that individual account. To make it easier on contributors, sites will need to allow contributors to opt-in to use Mozilla Connect profile information and authorization on registration and settings changes. Mozilla Connect will immediately authorize that contributor's profile on specified community sites (based on groups attached) and authorize the contributor for their respective level.
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]
 
Mozillians currently have a difficult time connecting and getting access to Projects and Products in our community. The Phonebook aims to fix this problem by offering an API that allows developers and apps across the project authorize users as Vouched Mozillians (using the "is_vouched" status within the Phonebook). This will be done in a two-pronged approach due to resourcing constraints:


* [http://farm8.staticflickr.com/7176/6894192756_accb611a3b_o.png Flow Diagram]
# An API key available on a per-user basis
# A token-based API key available to Applications via OAuth


=== Profile Sharing ===
=== Profile Sharing ===
* [http://farm8.staticflickr.com/7107/6894222294_9c85f7f6d4_o.png Flow Diagram]
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]


Users can opt-in to allow community sites and Mozilla community members to allow for contributor information to be shown to those who the user has allowed to be seen to. There are two major use cases attached to this approach:
Mozillian Phonebook users can opt-in to allow community sites to parse for their Mozillian Profile data. There are two use cases attached to this approach:


# When contributors go to a mozilla.org property with a profiling system, they should be offered a way to auto-populate the profiles fields with information already placed onto Mozillians.org. Contributors will need to opt-in to use the service during registration or as a logged-in user.  
# When contributors go to a mozilla.org property with a profiling system, they should be offered a way to auto-populate the profiles fields with information already placed onto Mozillians.org. Contributors will need to opt-in to use the service during registration or as a logged-in user.  
# For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis.
# For mozilla.org properties, they should be able to use to grab contributor information on a per user (i.e. e-mail address), per group or per location basis.
 
In order to keep the privacy of Mozillians safe, we'll use an oauth-based approach to allow applications to ask for access to the API as well as an individual user's data.
 
==Targeted Use Cases and Goals==
 
===Short-Term/K9O===
* Winston Bowden - ExactTarget - Sync up e-mail lists of Vouched Mozillians on Engagement's e-mail messaging tool. He wants to reduce the cost of asking IT to query the Phonebook database and upload those e-mails.
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.
* Yammer - Authorize contributors to have access within the "Mozillians" group.


=== <strike>Mozillian Resume</strike> '''<font color="red">[Later]</font>''' ===
===Long-Term===
Users can opt-in to allow Mozilla Connect to show contributions made across groups attached to the Mozillians' profile as well as allow people to make recommendations for work accomplished in the Mozilla Community.
* Gerv/Byron Jones - Bugzilla - Authorize contributors based on groups and status as those with greater privileges on Bugzilla. Also, they would like to auto-populate profile pics and fields of a Bugzilla user.
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.


== Non-Goals ==
== Non-Goals ==
* Make Mozillians.org the single sign-on solution for the Mozilla Project.
* Make Mozillians.org the single sign-on solution for the Mozilla Project.
== Implementation ==
'''Privacy Review'''
* {{done|}} - [[Privacy/Reviews/PhonebookAPI|Privacy Review]]
{| width="100%" cellpadding="3"
|-
| style="background-color: #efefef;"| '''Item'''
| style="background-color: #efefef; width: 100px;"| '''Status'''
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''
|-
| [https://bugzilla.mozilla.org/show_bug.cgi?id=775556 Land Per-User Vouched API] || {{done|}} || Q3 2012
|-
| [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{ok|}} || Q3 2012
|-
| [https://bugzilla.mozilla.org/show_bug.cgi?id=752997 Profile Data Proliferation (Oauth)] || {{ok|}} || Q3 2012
|}
Confirmed users
6,300

edits

Navigation menu