https://wiki.mozilla.org/api.php?action=feedcontributions&user=Adesai&feedformat=atomMozillaWiki - User contributions [en]2024-03-29T07:51:25ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=Mozillians&diff=484439Mozillians2012-11-01T18:16:18Z<p>Adesai: /* Documentation */</p>
<hr />
<div>This page contains all of the important details for Mozillians<br />
<br />
= Elevator Pitch =<br />
Tools and platforms that augment our current community platforms, programs and product pages to support Mozilla’s ability to on-ramp, retain and easily organize contributors in the Mozilla Project. <br />
<br />
= Info & Specs =<br />
<br />
== URLS ==<br />
* Dev - https://mozillians-dev.allizom.org/<br />
* Stage - https://mozillians.allizom.org/<br />
* Prod - https://mozillians.org/<br />
* Code: http://www.github.com/mozilla/mozillians<br />
* IRC: #commtools<br />
<br />
== Documentation ==<br />
* [[Mozillians/Mission | Mission]]<br />
* [[Mozillians/RoadMap | RoadMap]]<br />
* [[Mozillians/Releases/Process | Release Process]]<br />
* [[Mozillians/Contribute | How To Contribute Code]]<br />
* [http://mozillians.rtfd.org Read The Docs Install Guide]<br />
* [[Mozillians/L10N | Help With Translations]]<br />
* [[Mozillians/Test-Plan | Test Plan]]<br />
* [[Mozillians/Phonebook/Administration | Administration FAQ]]<br />
<br />
== Components ==<br />
* [[Mozillians/Phonebook|Phonebook]] <br />
* [[Mozillians/TaskBoard|TaskBoard]] <br />
* [[Mozillians/Events_Manager|Events Manager]]<br />
<br />
== Specs ==<br />
* [[Mozillians/Privacy-Specification | Privacy Controls]]<br />
* [[Mozillians/API-Specification | API Specification]]<br />
* [https://mozillians.etherpad.mozilla.org/api-copy-deck API Copy Deck]<br />
<br />
== Team ==<br />
The primary and secondary contacts for each role of this project:<br />
<br />
* Product Owner - Aakash Desai<br />
* Developers - Giorgos Logiotatidis / Andrei Hajdukewycz<br />
* TPM - Benjamin Sternthal<br />
* IT - Norman Maul<br />
* QA - Stephen Donner<br />
* Security - Yvan Boily<br />
* Privacy - Stacy Martin<br />
* L10N - Milos<br />
<br />
= Project Management =<br />
<br />
== Schedule ==<br />
* [http://publish.smartsheet.com/0dd40b53c2064a6ba07cafea6658a45b Smartsheet Schedule]<br />
<br />
== Meetings ==<br />
* [https://mozillians.etherpad.mozilla.org/status-2012-11-01 2012-11-01 Weekly]<br />
* [https://mozillians.etherpad.mozilla.org/qa-planning-2012-10-30 2012-10-30 QA Planning]<br />
* [https://mozillians.etherpad.mozilla.org/status-2012-10-25 2012-10-25 Weekly]<br />
* [https://mozillians.etherpad.mozilla.org/l10n-API-2012-10-24 2012-10-24 L10N API]<br />
* [[Mozillians/Meetings/Archive| Archive]]<br />
<br />
== Development ==<br />
* [https://mozilla.kanbanery.com/projects/23282/board/?key=5663800855a446460b4d4f9bc4287a3951a89823 Kanban Board]<br />
* [[Mozillians/Open-Bugs|Current Development Bugs ]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Administration&diff=484438Mozillians/Phonebook/Administration2012-11-01T18:15:28Z<p>Adesai: /* User Profiles */</p>
<hr />
<div>What can you do with the Mozillian Phonebook Administration Panel?<br />
<br />
First off, head over to http://www.mozillians.org/admin/ to access the panel. If you can't, e-mail adesai@mozilla.com <br />
<br />
== Users ==<br />
<br />
=== Change a user's First Name, Last Name, username, E-mail Address and password ===<br />
# Click on "Users" within the Auth section<br />
# Search for the user by the first/last name, userid or e-mail address<br />
# Click on the user you wish to select.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Make a user an Administrator ===<br />
# Click on "Users" within the Auth section<br />
# Search for the user by the first/last name, userid or e-mail address<br />
# Click on the user you wish to select.<br />
# Under "Permissions" check the "Staff status" and "Superuser status" checkbox.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Delete a user ===<br />
'''(WARNING: REMEMBER, YOU CANNOT UNDO THIS)'''<br />
# Click on "Users" within the Auth section<br />
# Search for the user by the first/last name, userid or e-mail address<br />
# Check the checkbox on the left of the user row entry<br />
# In the "Actions" drop down select box, choose "Delete selected users".<br />
# Click on "Go".<br />
<br />
=== Edit the Groups or Skills section for a user ===<br />
# Click on "Users" within the "Auth" section.<br />
# Click on the user who's profile you would like to edit.<br />
# Under Groups and Skills, highlight or un-highlight the Groups & Skills you would like to add or remove (respectively) from the user's profile.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Change/Delete the Profile Picture for a user ===<br />
# Click on "Users" within the "Auth" section.<br />
# Click on the user who's profile you would like to edit.<br />
# Under "Photo", you can do two things:<br />
#* Change the profile picture by clicking on "Browse" and selecting th image from your filesystem.<br />
#* Delete the profile picture by click on the "Clear" checkbox<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Add/Edit/Remove Website, Display name, Bio or IRC Nickname of the user ===<br />
# Click on "Users" within the "Auth" section.<br />
# Click on the user who's profile you would like to edit.<br />
# Under "Website", "Bio" or "IRC Nickname" text fields, you can do three things:<br />
#* Add appropriate text into the fields<br />
#* Edit the text in those fields<br />
#* Remove the text in those fields<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Vouch or Un-Vouch a User ===<br />
# Click on "Users" within the "Auth" section.<br />
# Click on the user who's profile you would like to edit. <br />
# You have two options:<br />
#* Check the "is vouched" checkbox, to vouch the user. This will make them a Vouched Mozillian.<br />
#* Uncheck the "is vouched checkbox to un-vouch the user. <br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Change who Vouched a specific Mozillian ===<br />
(WARNING: Make sure to check the "is vouched" checkbox)<br />
# Click on "Users" within the "Auth" section.<br />
# Click on the user who's profile you would like to edit. <br />
# Under the "Vouched By" select box, choose a Phonebook user.<br />
# Click on "Save" at the bottom of the page.<br />
<br />
== Groups ==<br />
<br />
=== Add a group ===<br />
# Click on "Groups" within the Groups section.<br />
# On the top right, click on "Add a Group"<br />
# Fill out the required name and url fields and any other optional fields you would like to choose. (NOTE: description, IRC channel, website, and wiki will not show on its Phonebook group page unless a Steward is selected for the group).<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Make a Curated Group ===<br />
# Click on "Groups" within the Groups section.<br />
# Find the group you want to edit and click on it.<br />
# In the "Steward" row entry, select a person from the list. <br />
# Add in content into the Description, IRC Channel(s), Website and Wiki fields.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Edit a Group ===<br />
# Click on "Groups" within the Groups section.<br />
# Find the group you want to edit and click on it.<br />
# Change any field on the page. <br />
# In the "Steward" row entry, select a person from the list. <br />
# Add in content into the Description, IRC Channel(s), Website and Wiki fields (NOTE: description, IRC channel, website, and wiki will not show on its Phonebook group page unless a Steward is selected for the group).<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Delete a Group ===<br />
# Click on "Groups" within the Groups section.<br />
# Find the group you want to delete and select the checkbox on its row entry<br />
# In the "Actions" drop down select box, choose "Delete selected groups".<br />
# Click on "Go".<br />
<br />
== API & Apps ==<br />
<br />
=== Adding an App via Admin Panel ===<br />
* Go to mozillians.org/admin<br />
* Click on "add" on the "Api apps" row<br />
* Fill in the Name, Description, URL and Owner fields based on information detailed in the approved Data Safety bug.<br />
* Leave "Key" empty<br />
* Check the "Is Mozilla App" box the app lives on mozilla.org<br />
* Check the "Is Active"<br />
* Click on "Save"<br />
* Comment in the approved Data Safety bug and close it as "Resolved FIXED"</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Administration&diff=484437Mozillians/Phonebook/Administration2012-11-01T18:14:24Z<p>Adesai: /* Groups */</p>
<hr />
<div>What can you do with the Mozillian Phonebook Administration Panel?<br />
<br />
First off, head over to http://www.mozillians.org/admin/ to access the panel. If you can't, e-mail adesai@mozilla.com <br />
<br />
== Users ==<br />
<br />
=== Change a user's First Name, Last Name, username, E-mail Address and password ===<br />
# Click on "Users" within the Auth section<br />
# Search for the user by the first/last name, userid or e-mail address<br />
# Click on the user you wish to select.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Make a user an Administrator ===<br />
# Click on "Users" within the Auth section<br />
# Search for the user by the first/last name, userid or e-mail address<br />
# Click on the user you wish to select.<br />
# Under "Permissions" check the "Staff status" and "Superuser status" checkbox.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Delete a user ===<br />
'''(WARNING: REMEMBER, YOU CANNOT UNDO THIS)'''<br />
# Click on "Users" within the Auth section<br />
# Search for the user by the first/last name, userid or e-mail address<br />
# Check the checkbox on the left of the user row entry<br />
# In the "Actions" drop down select box, choose "Delete selected users".<br />
# Click on "Go".<br />
<br />
== User Profiles ==<br />
<br />
=== Edit the Groups or Skills section for a user ===<br />
# Click on "User Profiles" within the "Users" section.<br />
# Click on the user who's profile you would like to edit.<br />
# Under Groups and Skills, highlight or un-highlight the Groups & Skills you would like to add or remove (respectively) from the user's profile.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Change/Delete the Profile Picture for a user ===<br />
# Click on "User Profiles" within the "Users" section.<br />
# Click on the user who's profile you would like to edit.<br />
# Under "Photo", you can do two things:<br />
#* Change the profile picture by clicking on "Browse" and selecting th image from your filesystem.<br />
#* Delete the profile picture by click on the "Clear" checkbox<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Add/Edit/Remove Website, Display name, Bio or IRC Nickname of the user ===<br />
# Click on "User Profiles" within the "Users" section.<br />
# Click on the user who's profile you would like to edit.<br />
# Under "Website", "Bio" or "IRC Nickname" text fields, you can do three things:<br />
#* Add appropriate text into the fields<br />
#* Edit the text in those fields<br />
#* Remove the text in those fields<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Vouch or Un-Vouch a User ===<br />
# Click on "User Profiles" within the "Users" section.<br />
# Click on the user who's profile you would like to edit. <br />
# You have two options:<br />
#* Check the "is vouched" checkbox, to vouch the user. This will make them a Vouched Mozillian.<br />
#* Uncheck the "is vouched checkbox to un-vouch the user. <br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Change who Vouched a specific Mozillian ===<br />
(WARNING: Make sure to check the "is vouched" checkbox)<br />
# Click on "User Profiles" within the "Users" section.<br />
# Click on the user who's profile you would like to edit. <br />
# Under the "Vouched By" select box, choose a Phonebook user.<br />
# Click on "Save" at the bottom of the page.<br />
<br />
== Groups ==<br />
<br />
=== Add a group ===<br />
# Click on "Groups" within the Groups section.<br />
# On the top right, click on "Add a Group"<br />
# Fill out the required name and url fields and any other optional fields you would like to choose. (NOTE: description, IRC channel, website, and wiki will not show on its Phonebook group page unless a Steward is selected for the group).<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Make a Curated Group ===<br />
# Click on "Groups" within the Groups section.<br />
# Find the group you want to edit and click on it.<br />
# In the "Steward" row entry, select a person from the list. <br />
# Add in content into the Description, IRC Channel(s), Website and Wiki fields.<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Edit a Group ===<br />
# Click on "Groups" within the Groups section.<br />
# Find the group you want to edit and click on it.<br />
# Change any field on the page. <br />
# In the "Steward" row entry, select a person from the list. <br />
# Add in content into the Description, IRC Channel(s), Website and Wiki fields (NOTE: description, IRC channel, website, and wiki will not show on its Phonebook group page unless a Steward is selected for the group).<br />
# Click on "Save" at the bottom right of the page.<br />
<br />
=== Delete a Group ===<br />
# Click on "Groups" within the Groups section.<br />
# Find the group you want to delete and select the checkbox on its row entry<br />
# In the "Actions" drop down select box, choose "Delete selected groups".<br />
# Click on "Go".<br />
<br />
== API & Apps ==<br />
<br />
=== Adding an App via Admin Panel ===<br />
* Go to mozillians.org/admin<br />
* Click on "add" on the "Api apps" row<br />
* Fill in the Name, Description, URL and Owner fields based on information detailed in the approved Data Safety bug.<br />
* Leave "Key" empty<br />
* Check the "Is Mozilla App" box the app lives on mozilla.org<br />
* Check the "Is Active"<br />
* Click on "Save"<br />
* Comment in the approved Data Safety bug and close it as "Resolved FIXED"</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Privacy-Specification&diff=484399Mozillians/Privacy-Specification2012-11-01T16:45:43Z<p>Adesai: /* API: Mozilla */</p>
<hr />
<div>= Privacy Settings =<br />
<br />
== API: Mozilla ==<br />
* Can have access to profile data<br />
* User can choose to allow or forbid<br />
* Allow -> gets profile data<br />
* Forbid -> gets no profile data<br />
* Queries can be<br />
** email<br />
** group<br />
** location<br />
** skill<br />
** language<br />
<br />
== API: Community ==<br />
* Can have access to is_vouched<br />
* User can globally choose to allow or forbid<br />
* Allow -> gets is_vouched<br />
* Forbid -> gets no data<br />
* Queries can be<br />
** email<br />
<br />
== Default Settings ==<br />
* API: Mozilla -> Allow<br />
* API: Community -> Allow<br />
<br />
== Interface Mockups ==<br />
* [https://dl.dropbox.com/u/59169312/Mozillians/mocks/privacy.png Settings Screen]<br />
<br />
== Privacy Review Guidelines ==<br />
The below is for reference, the above follows these guidelines<br />
<br />
* [https://wiki.mozilla.org/Privacy/Reviews/PhonebookAPI Privacy Review]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Test-Plan&diff=477442Mozillians/Test-Plan2012-10-08T21:59:59Z<p>Adesai: /* Risk areas */</p>
<hr />
<div>=Test Plan=<br />
<!--<br />
==Analysis==<br />
<br />
===Currently in use===<br />
(as of 2012-10-08)<br />
<br />
====dev====<br />
?<br />
====qa====<br />
?<br />
<br />
==Changes==<br />
<br />
===1. Manual testing:===<br />
<br />
===2. Automated testing:===<br />
<br />
===3. Releases:===<br />
<br />
*Will go out as many times as there are fixes ready to go. They will be released by developers, without IT or QA. The developers will be in charge of monitoring services after the release to watch for changes in behavior. <br />
<br />
===4. Bug fixes:===<br />
*Do not need verification prior to releases. They may be verified by a developer, or by QA in production. <br />
--><br />
<br />
==Risk areas==<br />
<br />
The lower the number the higher the risk.<br />
<br />
1. API - returns correct vouched status & information <br/><br />
1. Existing User Login/Logout<br/><br />
1. New User registration<br/><br />
1. User editing/saving account information<br/><br />
1. Mozillians Search (web ui)<br/><br />
<br />
2. User vouching<br/><br />
2. View Profile<br/><br />
2. View Groups<br/><br />
2. Invite New User<br/><br />
2. API - new account request<br/><br />
<br />
<br />
====Legend====<br />
[1] must have good enough coverage that we feel comfortable a regression will be caught quickly be pushed out to production if broken<br><br />
[2] can fail for up to an hour<br><br />
<br />
<!--<br />
==Risk plan and tools==<br />
====1. Risk: Less critical tests will not be covered with automation.====<br />
*If the feature breaks it won't cause as much of a problem. It is deemed acceptable to to wait an hour for a fix.<br />
<br />
====2. Risk: More bugs with less automation, why not automate more rather than less?====<br />
*Time. Creating more tests in Selenium is guaranteeing with unit tests have already verified, and it slows the process down. Right now there is a lot of duplicate effort. The team will discuss what is not currently covered by unit cases.<br />
<br />
====3. Risk: Releases may have hidden bugs or regressions which affect users.====<br />
*Using Graphite as a tool. This tool will monitor usage of many common mozillians functions. Any significant data spikes or dips after a release will quickly indicate if there is an issue.<br />
*Using StatsD as a tool. Another tool to monitor site usage by users, which may indicate issues if they exist.<br />
<br />
====4. Risk: Quality is going down, how do we change direction?====<br />
*We are already releasing very quickly, which allows for fixes to go out faster. If we get to a point where we are not satisfied with the quality we will weigh that against the benefits of the speed of fixes. <br />
<br />
====5. Risk: Quality will go down over time as QA is less involved with the release process.====<br />
*There is no endpoint for looking at quality, goal is to give the best product as fast as possible. Monitoring releases will provide quality data statistics to refer to.<br />
<br />
====6. Risk: We don't have a current baseline for quality.====<br />
*We are gathering data all the time with new services. It is really difficult to measure the current level of regression and new bugs which are sent out in releases. The entire team is keeping an eye on quality in order to keep the levels up. In order to maintain current levels of quality we will keep an eye on regressions and feedback.<br />
--></div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/API-Specification&diff=474776Mozillians/API-Specification2012-09-28T16:47:49Z<p>Adesai: /* Registration Of New Application */</p>
<hr />
<div>= API Specification =<br />
<br />
== Registration Of New Application ==<br />
# User requests new application under "Edit Profile -> Developer"<br />
## User enters URL <br />
## User is directed to fill out [https://bugzilla.mozilla.org/enter_bug.cgi?product=Data%20Safety bug] with app information and usage case(s)<br />
### Items necessary in filed bug comment: Description of app, expected API usage, URL of app<br />
# User is then approved or denied in admin, manually, interface by those with administrator privileges (product lead or tech. pm)<br />
# User received email notification of approval and directed to mozillians for api key<br />
<br />
== API Keys ==<br />
* API keys are per application not per user<br />
* API keys are restricted to Vouched Users<br />
<br />
== Application Attributes ==<br />
{| class="wikitable"<br />
|-<br />
! Key <br />
! Required<br />
! Type<br />
! Length <br />
! Example<br />
|-<br />
| '''key'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''name'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''description'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''url'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''owner'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''creation_date'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''tracker_id'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''is_mozilla_app'''<br />
| <br />
| boolean<br />
| <br />
|<br />
|}<br />
<br />
== API Methods ==<br />
'''Giorgos To Fill Out we can do sep wiki page for each like http://www.flickr.com/services/api/flickr.activity.userComments.html'''<br />
<br />
<br />
== API Filters ==<br />
Results may be filtered by<br />
<br />
{| class="wikitable"<br />
|-<br />
! Value <br />
! Type<br />
! Length <br />
! Example<br />
|-<br />
| '''email'''<br />
| <br />
| <br />
| <br />
|-<br />
| '''location'''<br />
| <br />
| <br />
| <br />
|-<br />
| '''groups'''<br />
| <br />
| <br />
| <br />
|-<br />
| '''language'''<br />
| <br />
| <br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/API-Specification&diff=474388Mozillians/API-Specification2012-09-27T15:10:10Z<p>Adesai: /* Registration Of New Application */</p>
<hr />
<div>= API Specification =<br />
<br />
== Registration Of New Application ==<br />
# User requests new application under "Edit Profile -> Developer"<br />
## User enters URL <br />
## User is directed to fill out [https://bugzilla.mozilla.org/enter_bug.cgi?product=Data%20Safety bug] with app information and usage case(s)<br />
# User is then approved or denied in admin interface by those with administrator privileges (product lead or tech. pm)<br />
# User received email notification of approval and directed to mozillians for api key<br />
<br />
== API Keys ==<br />
* API keys are per application not per user<br />
* API keys are restricted to Vouched Users<br />
<br />
== Application Attributes ==<br />
{| class="wikitable"<br />
|-<br />
! Key <br />
! Required<br />
! Type<br />
! Length <br />
! Example<br />
|-<br />
| '''key'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''name'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''description'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''url'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''owner'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''creation_date'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''tracker_id'''<br />
| <br />
| <br />
| <br />
|<br />
|-<br />
| '''is_mozilla_app'''<br />
| <br />
| boolean<br />
| <br />
|<br />
|}<br />
<br />
== API Methods ==<br />
'''Giorgos To Fill Out we can do sep wiki page for each like http://www.flickr.com/services/api/flickr.activity.userComments.html'''<br />
<br />
<br />
== API Filters ==<br />
Results may be filtered by<br />
<br />
{| class="wikitable"<br />
|-<br />
! Value <br />
! Type<br />
! Length <br />
! Example<br />
|-<br />
| '''email'''<br />
| <br />
| <br />
| <br />
|-<br />
| '''location'''<br />
| <br />
| <br />
| <br />
|-<br />
| '''groups'''<br />
| <br />
| <br />
| <br />
|-<br />
| '''language'''<br />
| <br />
| <br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=474035Mozillians/Phonebook/Services2012-09-26T16:20:39Z<p>Adesai: /* Features */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
* [http://www.flickr.com/photos/aakashhdesai/8026977545 User Privacy Settings]<br />
<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
* Yammer - Authorize contributors to have access within the "Mozillians" group.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.<br />
<br />
== Implementation ==<br />
<br />
'''Privacy Review'''<br />
* {{done|}} - [[Privacy/Reviews/PhonebookAPI|Privacy Review]]<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=775556 Land Per-User Vouched API] || {{done|}} || Q3 2012<br />
|-<br />
| [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{ok|}} || Q3 2012<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=752997 Profile Data Proliferation (Oauth)] || {{ok|}} || Q3 2012<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Meetings/2012&diff=472077Mozillians/Meetings/20122012-09-19T20:04:03Z<p>Adesai: </p>
<hr />
<div>* [https://mozillians.etherpad.mozilla.org/status-09-19-2012 2012-09-19]<br />
* [https://mozillians.etherpad.mozilla.org/status-09-12-2012 2012-09-12]<br />
* [https://mozillians.etherpad.mozilla.org/status-09-05-2012 2012-09-05]<br />
* [https://mozillians.etherpad.mozilla.org/status-08-28-2012 2012-08-28]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Milestones/Phase2&diff=470720Mozillians/Milestones/Phase22012-09-14T22:58:36Z<p>Adesai: /* P1: Phonebook */</p>
<hr />
<div>It’s difficult to build any plan without a basic set of metrics to guide decision-making. The purpose of this <br />
milestone is to deliver a solution that will consolidate contributor information into a centralized <br />
area. The outcomes are to garner better geographical/demographic, contributors-participation metrics and help guide the prioritization of needs for the development of tools for them.<br />
<br />
== Build tools to help retention and build involvement of our ''current'' contributors ==<br />
<br />
=== P1: [[Mozillians/Phonebook|Phonebook]] ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=657069 Land "Groups"] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=665373 Login with Browserid] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=706626 Design Overhaul] || {{done|}} || Q1 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.2/Location|Location & Timezones in Profiles]] || {{done|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Services|Phonebook API (and primary integration touch points)]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Search|Search Results]] Improvements || {{risk|}} || Q3 2012<br />
|-<br />
| P1 || Simpler [[Mozillians/Phonebook/Registration|Registration Flow]] || {{done|}} || Q3 2012<br />
|-<br />
| P1 || [[Mozillians/One_Phonebook_to_Rule_Them_All|Only One Mozillian Phonebook]] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
=== P2: [[Mozillians/TaskBoard|TaskBoard]] '''<font color="red">[On Hold]</font>''' ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || Release an initial task discovery tool for Mozilla || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=701899 Add in "goodfirstbug" into tasks] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
== Community Data and Visualization ==<br />
<br />
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Goal'''<br />
| style="background-color: #efefef;"| '''Metrics Sources'''<br />
| style="background-color: #efefef; width: 150px;"| '''Status'''<br />
|-<br />
| Determine the number of contributors in our community<br />
|<br />
* Mozillians' accounts<br />
|<br />
* {{done|}}<br />
|-<br />
| Determine contributor characteristics per community<br />
|<br />
* volume of contributors across groups<br />
* percentage of contributors across group tags against aggregate<br />
* volume of contributors per geographic location<br />
* percentages of contributors per geographic location against aggregate<br />
|<br />
* {{done|}}<br />
|}<br />
<br />
== Promotions ==<br />
<br />
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community and align our contributor base with their phonebook profiles. Phase 2 will be heavily promoted to our existing channels within sub-community sites such as AMO, QMO, SUMO, etc.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Channel'''<br />
| style="background-color: #efefef;"| '''Messaging'''<br />
| style="background-color: #efefef;"| '''Audience'''<br />
|-<br />
| Contributor Services w/ user accounts<br />
|<br />
* Promotions of the show vouched mozillians will have greater privileges, where possible, across the Mozilla universe.<br />
|<br />
* contributors with user accounts on our various web services such as AMO, QMO, SUMO, etc.<br />
|-<br />
| Community/Get Involved Site and Events<br />
|<br />
* Implant snippets on /contribute to contact phonebook users in "steward" group and other associations.<br />
* Add link and description to event get involved fliers to get to the snippets and contact someone<br />
* Integrate Taskboard entries specific to the host<br />
|<br />
* New/Potential contributors<br />
|-<br />
| Personal Signatures (twitter, facebook, e-mail signatures)<br />
|<br />
* Promote links to Mozillian Phonebook profiles as signatures to who they are as Mozillian contributors<br />
|<br />
* Core/Active contributors<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/RACI&diff=469500Mozillians/RACI2012-09-11T17:49:41Z<p>Adesai: /* Responsible */</p>
<hr />
<div>== Responsible ==<br />
* UX - <br />
* Dev Lead<br />
** Phonebook - Giorgos<br />
* Devs - Giorgos, Aakash<br />
* QA - mbrandt, rbillings<br />
* Communications<br />
** Reps - Pierros/William Q<br />
** Stewards - David Boswell<br />
<br />
== Accountable ==<br />
* Aakash Desai<br />
* Mary Colvig<br />
<br />
== Consulted ==<br />
* Stewards (David and Stewards Group with CAPs)<br />
* Reps Council<br />
* Chris Beard<br />
<br />
== Informed ==<br />
* Mozillians (Paid Staff and Volunteers)</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Meetings/2012&diff=467826Mozillians/Meetings/20122012-09-05T15:02:33Z<p>Adesai: </p>
<hr />
<div>* [https://mozillians.etherpad.mozilla.org/status-09-05-2012 2012-09-05]<br />
* [https://mozillians.etherpad.mozilla.org/status-08-28-2012 2012-08-28]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/RACI&diff=465821Mozillians/RACI2012-08-30T15:57:22Z<p>Adesai: /* Responsible */</p>
<hr />
<div>== Responsible ==<br />
* UX - <br />
* Dev Lead<br />
** Phonebook - Giorgos<br />
* Devs - Giorgogs, Aakash<br />
* QA - Matt Brandt<br />
* Communications<br />
** Reps - Pierros/William Q<br />
** Stewards - David Boswell<br />
<br />
== Accountable ==<br />
* Aakash Desai<br />
* Mary Colvig<br />
<br />
== Consulted ==<br />
* Stewards (David and Stewards Group with CAPs)<br />
* Reps Council<br />
* Chris Beard<br />
<br />
== Informed ==<br />
* Mozillians (Paid Staff and Volunteers)</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Milestones/Phase2&diff=465811Mozillians/Milestones/Phase22012-08-30T15:32:58Z<p>Adesai: /* P1: Phonebook */</p>
<hr />
<div>It’s difficult to build any plan without a basic set of metrics to guide decision-making. The purpose of this <br />
milestone is to deliver a solution that will consolidate contributor information into a centralized <br />
area. The outcomes are to garner better geographical/demographic, contributors-participation metrics and help guide the prioritization of needs for the development of tools for them.<br />
<br />
== Build tools to help retention and build involvement of our ''current'' contributors ==<br />
<br />
=== P1: [[Mozillians/Phonebook|Phonebook]] ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=657069 Land "Groups"] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=665373 Login with Browserid] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=706626 Design Overhaul] || {{done|}} || Q1 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.2/Location|Location & Timezones in Profiles]] || {{done|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Services|Phonebook API (and primary integration touch points)]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Search|Search Results]] Improvements || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || Simpler [[Mozillians/Phonebook/Registration|Registration Flow]] || {{done|}} || Q3 2012<br />
|-<br />
| P1 || [[Mozillians/One_Phonebook_to_Rule_Them_All|Only One Mozillian Phonebook]] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
=== P2: [[Mozillians/TaskBoard|TaskBoard]] '''<font color="red">[On Hold]</font>''' ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || Release an initial task discovery tool for Mozilla || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=701899 Add in "goodfirstbug" into tasks] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
== Community Data and Visualization ==<br />
<br />
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Goal'''<br />
| style="background-color: #efefef;"| '''Metrics Sources'''<br />
| style="background-color: #efefef; width: 150px;"| '''Status'''<br />
|-<br />
| Determine the number of contributors in our community<br />
|<br />
* Mozillians' accounts<br />
|<br />
* {{done|}}<br />
|-<br />
| Determine contributor characteristics per community<br />
|<br />
* volume of contributors across groups<br />
* percentage of contributors across group tags against aggregate<br />
* volume of contributors per geographic location<br />
* percentages of contributors per geographic location against aggregate<br />
|<br />
* {{done|}}<br />
|}<br />
<br />
== Promotions ==<br />
<br />
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community and align our contributor base with their phonebook profiles. Phase 2 will be heavily promoted to our existing channels within sub-community sites such as AMO, QMO, SUMO, etc.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Channel'''<br />
| style="background-color: #efefef;"| '''Messaging'''<br />
| style="background-color: #efefef;"| '''Audience'''<br />
|-<br />
| Contributor Services w/ user accounts<br />
|<br />
* Promotions of the show vouched mozillians will have greater privileges, where possible, across the Mozilla universe.<br />
|<br />
* contributors with user accounts on our various web services such as AMO, QMO, SUMO, etc.<br />
|-<br />
| Community/Get Involved Site and Events<br />
|<br />
* Implant snippets on /contribute to contact phonebook users in "steward" group and other associations.<br />
* Add link and description to event get involved fliers to get to the snippets and contact someone<br />
* Integrate Taskboard entries specific to the host<br />
|<br />
* New/Potential contributors<br />
|-<br />
| Personal Signatures (twitter, facebook, e-mail signatures)<br />
|<br />
* Promote links to Mozillian Phonebook profiles as signatures to who they are as Mozillian contributors<br />
|<br />
* Core/Active contributors<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2012-08-20&diff=462373WeeklyUpdates/2012-08-202012-08-20T16:33:23Z<p>Adesai: /* Grow Mozilla */</p>
<hr />
<div><br />
<small>[[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} -1 week}}|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} +1 week}}|next week »]]</small><br />
<br />
{{conf|8600}}<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Product Status Updates (voice updates) ==<br />
<br />
=== Firefox Desktop ===<br />
''Speaker Location: johnath (Toronto)''<br />
* Next week is merge/release week!<br />
<br />
=== Firefox Mobile ===<br />
''Speaker Location: blassey (Boston)'' <br />
<br />
=== Thunderbird ===<br />
''Speaker Location:'' <br />
<br />
=== Older Branch Work ===<br />
''Speaker Location:'' <br />
<br />
=== Webmaker ===<br />
''Speaker Location:''<br />
<br />
=== Identity ===<br />
''Speaker Location:''<br />
<br />
=== Services ===<br />
''Speaker Location:''<br />
<br />
=== Firefox OS ===<br />
''Speaker Location:''<br />
<br />
=== Grow Mozilla ===<br />
''Speaker Location: San Francisco''<br />
<br />
* This week will be the last [[Grow/Meeting_08_09_12|Grow Mozilla discussion]] before MozCamp in Warsaw, so this is a good opportunity to come by and ask any questions you have about hosting a session or how to get the most of attending.<br />
<br />
* [https://reps.mozilla.org/events/ Mozilla Reps Event Manager] is live and includes a calendar, an interactive map and an awesome event creation tool. Check it out and post to [https://groups.google.com/forum/?fromgroups#!forum/mozilla.reps.general mozilla.reps.general] with any questions or comments.<br />
<br />
* The [http://www.mozillians.org Mozillians Phonebook] now [https://blog.mozilla.org/community/2012/08/09/a-layer-of-trust-for-the-mozilla-community/ offers an API to authorize Mozillians across your favorite sites/apps] vouch api.<br />
<br />
== Speakers ==<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Your Title Here<br />
| Your Name Here<br />
| What are you going to talk about?<br />
| Links to slides or images you want displayed on screen<br />
| Link to where audience can find out more information<br />
|-<br />
| Recruiting<br />
| Michelle Marovich<br />
| We are hiring in Product Management!<br />
| [http://tinyurl.com/8mtwnda/ Link to Job Listing]<br />
| [https://intranet.mozilla.org/Recruiting#Highlighted_Recruiting_Priorities_and_Contact_Information/ More Info]<br />
|-<br />
| Games - BananaBread Demo<br />
| Martin Best<br />
| Demo of what is now possible with the release of Firefox 15!<br />
| [https://docs.google.com/present/edit?id=0AUSKWkSn0nFDZGZkNWR4M2NfMTE2bWhuOTN6Y2o Presentation]<br />
| <br />
|}<br />
<br />
== Introducing New Hires ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Hire<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new hire?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
| ''Didem Ersoz''<br />
| ''Pascal Finette''<br />
| ''Mountain View,CA''<br />
| ''WebFWD''<br />
|-<br />
| ''Mathew Caldwell''<br />
| ''Debbie Cohen''<br />
| ''Mountain View, CA''<br />
| ''Director of Staffing''<br />
|-<br />
| ''Angela King''<br />
| ''Mihca Degele''<br />
| ''Mountain View, CA''<br />
| ''HR Coordinator''<br />
|-<br />
|}<br />
<br />
== Introducing New Interns ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Intern<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new intern?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Roundtable ==<br />
<br />
= &lt;meta&gt; =<br />
<br />
Notes and non-voice status updates that aren't part of the live meeting go here.<br />
<br />
== Status Updates By Team (*non-voice* updates) ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Services ===<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== WebQA ====<br />
<br />
==== QA Community ====<br />
<br />
=== Automation & Tools ===<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
==== PR ====<br />
<br />
==== Events ====<br />
<br />
==== Creative Team ====<br />
<br />
==== Community Marketing ====<br />
<br />
=== Support ===<br />
<br />
=== Metrics ===<br />
<br />
=== Evangelism ===<br />
<br />
=== Labs ===<br />
<br />
=== Apps ===<br />
<br />
=== Developer Tools ===<br />
<br />
=== Add-ons ===<br />
<br />
=== Webdev ===<br />
<br />
=== L10n ===<br />
<br />
=== People Team ===<br />
<br />
=== WebFWD ===<br />
<br />
== Foundation Updates ==</div>Adesaihttps://wiki.mozilla.org/index.php?title=WeeklyUpdates/2012-08-13&diff=460474WeeklyUpdates/2012-08-132012-08-13T17:52:26Z<p>Adesai: /* Grow Mozilla */</p>
<hr />
<div><small>[[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} -1 week}}|« previous week]] | [[WeeklyUpdates|index]] | [[WeeklyUpdates/{{#time:Y-m-d|{{SUBPAGENAME}} +1 week}}|next week »]]</small><br />
<br />
{{conf|8600}}<br />
<br />
__TOC__<br />
<br />
= All-hands Status Meeting Agenda =<br />
<br />
Items in this section will be shared during the live all-hand status meeting.<br />
<br />
== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==<br />
<br />
== Upcoming Events ==<br />
<br />
=== This Week ===<br />
<br />
=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===<br />
<br />
=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===<br />
<br />
=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===<br />
<br />
=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===<br />
<br />
=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===<br />
<br />
=== Next Week ===<br />
<br />
== Product Status Updates (voice updates) ==<br />
<br />
=== Firefox Desktop ===<br />
''Speaker Location: toronto (johnath)''<br />
* Stub Installer work progressing. UI interaction build made available on 8/6. Functional build in about a week. We'll QA and release, possibly with a funnelcake study, when it's ready (doesn't ride trains.)<br />
* HiDPI work for retina Macs well underway. Try server build at https://bugzilla.mozilla.org/show_bug.cgi?id=674373 that makes text really pretty. <br />
* These notes shamelessly cribbed from the [https://wiki.mozilla.org/Firefox/Planning Wednesday product coordination call], maybe you should attend!<br />
<br />
=== Firefox Mobile ===<br />
''Speaker Location: toronto (johnath)'' <br />
* Mobile team meeting up in Boston this week to plan the rest of 2012 (and beyond!)<br />
** We will also be hosting a "[http://mozhackbos.eventbrite.com/ Games & Add-on Hack Day]" on Thursday.<br />
* Many Google properties now sending us mobile content. Thanks to the web compat folks!<br />
* Finkle [http://starkravingfinkle.org/blog/2012/08/firefox-for-android-remote-debugging-is-here/ blogged about remote debugging in Firefox for Android]<br />
<br />
=== Thunderbird ===<br />
''Speaker Location:'' <br />
<br />
=== Older Branch Work ===<br />
''Speaker Location:'' <br />
<br />
=== Webmaker ===<br />
''Speaker Location:''<br />
<br />
=== Identity ===<br />
''Speaker Location:''<br />
<br />
=== Services ===<br />
''Speaker Location:''<br />
<br />
=== Firefox OS ===<br />
''Speaker Location: Dietrich''<br />
<br />
The team is focused on P1 priorities and has started daily B2G and Gaia triage sessions to close bugs and reduce scope to essential v1 requirements. Follow along on Lawrence's [http://people.mozilla.org/~lmandel/basecamp/ blocker dashboard].<br />
<br />
* Gaia: New UI pieces: overlays for Scanning, No Photos, No SD Card messages, the date/time picker landed, some Email visual design implementation, carrier name shows in utility tray, image picker in Contacts. Lots of localization work and updates to new permissions system landing. Flux in requirements for consumption control and first-run experience is ongoing risk.<br />
* Platform: Most of cell broadcast is finished. More work in permissions, camera, headset, and automatic updates continue to land.<br />
* Security: Existing permission whitelist is being replaced with proper permission checks and prompts. Need to lock down permissions and app data jars. App signing for privileged apps - at risk.<br />
* Release Coordinators: Blocked on device availability for dogfooding as well as FOTA updates that don't wipe user data<br />
* Release Engineering: Repo layouts for developers on github. Resolved some contract and security access questions which impact release mechanics. Need information from agal on contractual details of how updates are to be served.<br />
* L10n: AMO & Marketplace: es 100%, pt-BR 71%; Persona: es 100%, pt-BR 100%.<br />
* QA: Test coverage metrics on daily smoke tests available, working with A-team to publish daily manifests so TEF can test daily builds. Smoke test metrics are still averaging about 26% failures and Blocking-Basecamp+ count is high.<br />
* Tools and Automation: Mochitests and WebAPI tests running per-commit to m-c and getting triaged 3x week.<br />
<br />
=== Grow Mozilla ===<br />
''Speaker Location: San Francisco''<br />
<br />
* Kicking off a weekly [[Grow|Grow Mozilla]] update! As a reminder, Grow Mozilla helps us achieve our ambitious goals by bringing new people into the project, increasing skills of community members and expanding our culture as we grow larger.<br />
<br />
* Check out the new about:community blog at [https://blog.mozilla.org/community/ blog.mozilla.org/community] for Grow Mozilla and Mozilla community-related news. <br />
<br />
* [[MozCampEU2012|MozCamp EU]]: We are currently in the process of sending out attendance and session acceptance notifications to paid staff and booking volunteer travel. Note: We are still evaluating some proposals and everyone should be notified of their status by end of week.<br />
<br />
* Mozillians.org now offers searching by group and an API to determine if someone is vouched within our community. Read more on the [https://blog.mozilla.org/community/2012/08/09/a-layer-of-trust-for-the-mozilla-community/ announcement blogpost].<br />
<br />
== Speakers ==<br />
<br />
The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.<br />
<br />
{| class="fullwidth-table"<br />
|-<br />
! Title<br />
! Presenter<br />
! Topic<br />
! Media<br />
! More Details<br />
|-<br />
| Senior Privacy Manager<br />
| Stacy Martin<br />
| How to Use the Cloud at Work<br />
| Links to slides or images you want displayed on screen<br />
| https://intranet.mozilla.org/Cloud<br />
|-<br />
|}<br />
<br />
== Introducing New Hires ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Hire<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new hire?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
| ''Bhavana Bajaj''<br />
| ''Johnathan Nightingale''<br />
| ''Toronto, Ontario, Canada''<br />
| ''Engineering Project Manager''<br />
|-<br />
| ''Lisa Brewster''<br />
| ''Justin Scott''<br />
| ''Mountain View,CA''<br />
| ''Marketplace App Review Lead''<br />
|-<br />
|}<br />
<br />
== Introducing New Interns ==<br />
{| class="fullwidth-table"<br />
|-<br />
! New Intern<br />
! Introduced by<br />
! Speaker location<br />
! Will be working on<br />
|-<br />
| ''Who is the new intern?''<br />
| ''Who will be introducing that person?''<br />
| ''From which office will that introduction be transmitted?''<br />
| ''What will the new person be working on?''<br />
|-<br />
<!-- Insert new rows here --><br />
|-<br />
|}<br />
<br />
== Roundtable ==<br />
<br />
= &lt;meta&gt; =<br />
<br />
Notes and non-voice status updates that aren't part of the live meeting go here.<br />
<br />
== Status Updates By Team (*non-voice* updates) ==<br />
<br />
=== Firefox ===<br />
<br />
=== Platform ===<br />
<br />
=== Services ===<br />
<br />
=== Messaging ===<br />
<br />
=== Mobile ===<br />
<br />
=== IT ===<br />
<br />
=== Release Engineering ===<br />
<br />
=== QA ===<br />
<br />
==== Test Execution ====<br />
<br />
==== WebQA ====<br />
*Affiliates<br />
** Small l10n pushed -- [https://bugzilla.mozilla.org/show_bug.cgi?id=780622 milestone 2012-08-06]<br />
** Pushing another small release today - [https://bugzilla.mozilla.org/show_bug.cgi?id=781550 bug 781550]<br />
*AMO<br />
**[http://cl.ly/3T07243A1z1h 2012-08-09] is going live today.<br />
*Jetpack Builder (aka FlightDeck)<br />
** Small push on Friday to [https://bugzilla.mozilla.org/show_bug.cgi?id=779553 upgrade the SDK to version 1.9]<br />
*Mozilla.com<br />
** Small content pushes<br />
*Mozillians<br />
** [https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED;query_format=advanced;component=Phonebook;product=Community%20Tools;target_milestone=2012-08-08;list_id=3967880 milestone 2012-08-08] pushed<br />
*MDN<br />
** Continuing work on [https://hacks.mozilla.org/2012/08/its-time-mdn-relaunch-on-kuma-wiki-on-august-3/ post-KUMA] fixes and tweaks<br />
*Socorro<br />
** <strike>[https://bugzilla.mozilla.org/show_bug.cgi?id=771218 Bug 771218] - Ongoing problems with Socorro staging</strike><br />
*** Resolved, and pushed a small, infra-related release<br />
*SUMO<br />
** Continuous deployment, no updates<br />
<br />
==== QA Community ====<br />
<br />
=== Automation & Tools ===<br />
<br />
=== Security ===<br />
<br />
=== Engagement ===<br />
<br />
==== PR ====<br />
<br />
==== Events ====<br />
<br />
==== Creative Team ====<br />
<br />
==== Community Marketing ====<br />
<br />
=== Support ===<br />
<br />
=== Metrics ===<br />
<br />
=== Evangelism ===<br />
<br />
=== Labs ===<br />
<br />
=== Apps ===<br />
<br />
=== Developer Tools ===<br />
<br />
=== Add-ons ===<br />
<br />
=== Webdev ===<br />
<br />
=== L10n ===<br />
<br />
=== People Team ===<br />
<br />
=== WebFWD ===<br />
<br />
== Foundation Updates ==</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=460427Mozillians/Phonebook/Services2012-08-13T17:03:13Z<p>Adesai: /* Short-Term/K9O */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
* Yammer - Authorize contributors to have access within the "Mozillians" group.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.<br />
<br />
== Implementation ==<br />
<br />
'''Privacy Review'''<br />
* {{done|}} - [[Privacy/Reviews/PhonebookAPI|Privacy Review]]<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=775556 Land Per-User Vouched API] || {{done|}} || Q3 2012<br />
|-<br />
| [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{ok|}} || Q3 2012<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=752997 Profile Data Proliferation (Oauth)] || {{ok|}} || Q3 2012<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=459746Mozillians/Phonebook/Services2012-08-09T17:33:23Z<p>Adesai: </p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.<br />
<br />
== Implementation ==<br />
<br />
'''Privacy Review'''<br />
* {{done|}} - [[Privacy/Reviews/PhonebookAPI|Privacy Review]]<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=775556 Land Per-User Vouched API] || {{done|}} || Q3 2012<br />
|-<br />
| [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{ok|}} || Q3 2012<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=752997 Profile Data Proliferation (Oauth)] || {{ok|}} || Q3 2012<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=459745Mozillians/Phonebook/Services2012-08-09T17:32:58Z<p>Adesai: /* Implementation */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
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.<br />
<br />
== Implementation ==<br />
<br />
'''Privacy Review'''<br />
* {{done|}} - [[Privacy/Reviews/PhonebookAPI|Privacy Review]]<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=775556 Land Per-User Vouched API] || {{done|}} || Q3 2012<br />
|-<br />
| [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{ok|}} || Q3 2012<br />
|-<br />
| [https://bugzilla.mozilla.org/show_bug.cgi?id=752997 Profile Data Proliferation (Oauth)] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=459743Mozillians/Phonebook/Services2012-08-09T17:30:40Z<p>Adesai: /* Implementation */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
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.<br />
<br />
== Implementation ==<br />
<br />
'''Privacy Review'''<br />
* {{done|}} - [[Privacy/Reviews/PhonebookAPI|Privacy Review]]<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| Land Per-User Vouched API || {{done|}} || Q3 2012<br />
|-<br />
| Profile Data Proliferation (Oauth) || {{ok|}} || Q3 2012<br />
|}<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=459741Mozillians/Phonebook/Services2012-08-09T17:30:18Z<p>Adesai: /* Features */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
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.<br />
<br />
== Implementation ==<br />
<br />
'''Privacy Review'''<br />
* {{done|}} - [[Privacy/Reviews/PhonebookAPI|Privacy Review]]<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| Land Per-User Vouched API || {{done|}} || Q3 2012<br />
|-<br />
| Profile Data Proliferation (Oauth) || {{ok|}} || Q3 2012<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=459042Mozillians/Phonebook/Services2012-08-08T03:51:27Z<p>Adesai: /* Profile Sharing */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=459041Mozillians/Phonebook/Services2012-08-08T03:49:38Z<p>Adesai: /* Mozillian Passport */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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: <br />
<br />
# An API key available on a per-user basis<br />
# A token-based API key available to Applications via OAuth<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=454384Mozillians/Phonebook/Services2012-07-25T16:06:07Z<p>Adesai: /* Mozillian Passport */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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 authorize users as Vouched Mozillians; thus, giving them greater access to functionality. An API key will be available to Applications/Consumers via OAuth.<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians&diff=454373Mozillians2012-07-25T15:43:44Z<p>Adesai: /* Contribute Code! */</p>
<hr />
<div>== Summary ==<br />
<br />
=== Mission ===<br />
We plan to build [http://farm8.staticflickr.com/7166/6771918759_4e2a828c2c_o.png tools and platforms that add that necessary layer of abstraction] that augment our current community platforms, programs and product pages to support Mozilla’s [http://farm8.staticflickr.com/7202/6777403942_5d8e9d2274_o.png ability to on-ramp, retain and easily organize contributors in the Mozilla Project].<br />
<br />
'''2012 Goals'''<br />
* Getting involved in the Mozilla project only takes 2-steps from any place in our community.<br />
* Mozillians will be able to know what and how they're contributing to the project.<br />
* Mozillians will be able to recognize and reward someone's contributions to the project in real-time.<br />
* Community Managers will be able to track and measure the effectiveness of their communities.<br />
<br />
=== Context ===<br />
The Mozilla project has grown to support many products and projects over the past year: Firefox (Desktop and Mobile), Thunderbird, Boot2Gecko, Apps and Identity. These products arrived in quick succession making it difficult to organize, grow, and direct the project’s communities to support them. To ramp-up our organically-created and modestly-supported community to meet the needs of this situation, the Engagement and People teams have begun driving an initiative called “Grow Mozilla”. It aims to build, develop and enable a global community of paid and volunteer Mozillians to propel our [http://www.mozilla.org/about/mission.html mission] and build great products for the web.<br />
<br />
Both teams are doing great work in building [https://wiki.mozilla.org/Grow_Mozilla#Programs programs] that helps to on-board new contributors, retain them and develop them to become leaders. We’re becoming more organized in how we approach contributor engagement. The Mozilla Reps and Stewards programs have robust infrastructure and people in place to help on-ramp and advise Mozillians at a level we haven't had before. Contributors are finding people responding to their inquiries to get involved and being directed to tasks available via many of our functional areas.<br />
<br />
Though, this isn't enough. For the thousands of requests we receive to get involved per month, about 20 end up as contributors. Further, these Stewards and Reps have limited tools at their disposal that come standard in many community-based organizations: they don't know who does what, how much they do it or when they do it across all of our communities. We need to do more to help grow our community's size and involvement that can propel our mission to support our current and future endeavors.<br />
<br />
=== Tools ===<br />
Mozillians.org is comprised of a collection of tools built to enhance engagement from our contributor base. An introduction and explanation of what each tool is and does can be found in the following wikis:<br />
<br />
# [[Mozillians/Phonebook|Phonebook]] - A platform to share, identify and communicate with Mozillians in our community. Active/Core Mozillians will be able to use their profile as a resume and passport for who they are and what they do in our community. For Reps & Stewards, they'll be able to better manage and show-off who is in their communities. New/potential contributors that come across it will be served up ways to get involved.<br />
# [[Mozillians/TaskBoard|TaskBoard]] - A platform to uplift and share all contributor-facing tasks in our community into one easy to find app. It will act as the basis for contributors to easily find (2-steps!) a task or job available to finish in the project. The app will help Mozillians increase participation across their projects, areas and teams by offering ways to embed relevant tasks on any on-ramp across the community.<br />
# [[Mozillians/Events_Manager|Events Manager]] - A platform to uplift and share all contributor-facing events in our community into one easy to find app. It's purpose is for contributors to easily find and participate in any event happening in our community anywhere in the world at any given time.<br />
<br />
== Management ==<br />
<br />
=== Meetings ===<br />
We have a weekly meeting where the team comes together to get synced up on various overarching topics on the product path. We post those meeting times and schedules on our google group, but you can also find that information below:<br />
<br />
* Tuesdays, 11:30AM Pacific<br />
* Backchannel: #commtools<br />
* Vidyo: 370<br />
<br />
[[Mozillians/Meetings|Meeting Archives]]<br />
<br />
=== Roadmap ===<br />
The site will be built over a series of phases. Our current thinking about milestones is below:<br />
<br />
* <strike>[[Mozillians/Milestones/Phase1|Phase1 Roadmap]] (initial launch)</strike><br />
* [[Mozillians/Milestones/Phase2|Phase2 Roadmap]] (determine and grow retention)<br />
* [[Mozillians/Milestones/Phase3|Phase3 Roadmap]] (determine and grow contributor base)<br />
<br />
Information related to the 2012 roadmap can be found [http://aakash.doesthings.com/2012/03/19/community-tools-platforms-roadmap-2012/ here]<br />
<br />
=== Documents ===<br />
* [[Mozillians/RACI |Team RACI]]<br />
* [[Mozillians/Seed group|Seed group]] -- Group of people invited to join site at launch to form a seed of phonebook data<br />
* [[Mozillians/Releases/Process|Release Process]]<br />
<br />
== Get Involved ==<br />
If you have comments, questions, suggestions or ideas, feel free to join the discussion at:<br />
<br />
* [irc://irc.mozilla.org#commtools #commtools IRC channel]<br />
* [http://groups.google.com/group/mozilla-dev-community-tools/topics Google Group]<br />
<br />
<br />
=== Contribute Code! ===<br />
* [https://gist.github.com/2979120 Get set up with your virtualenv]<br />
* Find the code on our [http://www.github.com/mozilla/mozillians Github Repository]<br />
* [https://gist.github.com/2422571 Mozillians Git-Fu]<br />
* Take a look at the [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=%5Bgood%20first%20bug%5D;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=Community%20Tools starter bugs that we've selected]<br />
<br />
To get set up, we've created a set of documentation [http://mozillians.rtfd.org/ to help guide you through the process]. For any questions or comments, please talk to aakashd or tallOwen on [irc://irc.mozilla.org#mozillians #mozillians on irc.mozilla.org] or contact us through our [https://lists.mozilla.org/listinfo/mozillians mailing list]!<br />
<br />
=== Test Releases before they go out! ===<br />
<br />
=== Translate Strings on Mozillians.org ===<br />
For this project, we're using Mozilla's Verbatim(Pootle). If you want to contribute, please register on [http://localize.mozilla.org Verbatim], then go to [https://localize.mozilla.org/projects/mozillians/ Mozillians Project], find your language and start translating.<br />
<br />
If you're not a localization leader, you're going to be able to suggest translations, and localization leader for your language will check those later and either accept or refuse those suggestions. We're advising all our contributors to contact Mozilla Localization Team for their locale(language), and coordinate with them. Localization teams contact pages can be found at https://wiki.mozilla.org/L10n:Teams . Sending an email to localization leader would be good start.<br />
<br />
In case you can't find your language in Mozillians project on Verbatim, that means nobody yet volunteered to start working on it. But that can as well be you. You can request for Mozillians project to be added in your language via [https://l10n-stage-sj.mozilla.org/webby/mozillians Webby application](using your LDAP credentials), or you can ping Milos on irc.mozilla.org, channel #l10n and #mozillians<br />
<br />
And last but certainly not the least, we've recently created a [http://l10n.mozilla-community.org/~milos/l10n-calendar/ l10n-calendar] which holds info on when do we add new strings to Verbatim and when do we release.<br />
<br />
We would love to have you on board!</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians&diff=454372Mozillians2012-07-25T15:42:54Z<p>Adesai: /* Contribute Code! */</p>
<hr />
<div>== Summary ==<br />
<br />
=== Mission ===<br />
We plan to build [http://farm8.staticflickr.com/7166/6771918759_4e2a828c2c_o.png tools and platforms that add that necessary layer of abstraction] that augment our current community platforms, programs and product pages to support Mozilla’s [http://farm8.staticflickr.com/7202/6777403942_5d8e9d2274_o.png ability to on-ramp, retain and easily organize contributors in the Mozilla Project].<br />
<br />
'''2012 Goals'''<br />
* Getting involved in the Mozilla project only takes 2-steps from any place in our community.<br />
* Mozillians will be able to know what and how they're contributing to the project.<br />
* Mozillians will be able to recognize and reward someone's contributions to the project in real-time.<br />
* Community Managers will be able to track and measure the effectiveness of their communities.<br />
<br />
=== Context ===<br />
The Mozilla project has grown to support many products and projects over the past year: Firefox (Desktop and Mobile), Thunderbird, Boot2Gecko, Apps and Identity. These products arrived in quick succession making it difficult to organize, grow, and direct the project’s communities to support them. To ramp-up our organically-created and modestly-supported community to meet the needs of this situation, the Engagement and People teams have begun driving an initiative called “Grow Mozilla”. It aims to build, develop and enable a global community of paid and volunteer Mozillians to propel our [http://www.mozilla.org/about/mission.html mission] and build great products for the web.<br />
<br />
Both teams are doing great work in building [https://wiki.mozilla.org/Grow_Mozilla#Programs programs] that helps to on-board new contributors, retain them and develop them to become leaders. We’re becoming more organized in how we approach contributor engagement. The Mozilla Reps and Stewards programs have robust infrastructure and people in place to help on-ramp and advise Mozillians at a level we haven't had before. Contributors are finding people responding to their inquiries to get involved and being directed to tasks available via many of our functional areas.<br />
<br />
Though, this isn't enough. For the thousands of requests we receive to get involved per month, about 20 end up as contributors. Further, these Stewards and Reps have limited tools at their disposal that come standard in many community-based organizations: they don't know who does what, how much they do it or when they do it across all of our communities. We need to do more to help grow our community's size and involvement that can propel our mission to support our current and future endeavors.<br />
<br />
=== Tools ===<br />
Mozillians.org is comprised of a collection of tools built to enhance engagement from our contributor base. An introduction and explanation of what each tool is and does can be found in the following wikis:<br />
<br />
# [[Mozillians/Phonebook|Phonebook]] - A platform to share, identify and communicate with Mozillians in our community. Active/Core Mozillians will be able to use their profile as a resume and passport for who they are and what they do in our community. For Reps & Stewards, they'll be able to better manage and show-off who is in their communities. New/potential contributors that come across it will be served up ways to get involved.<br />
# [[Mozillians/TaskBoard|TaskBoard]] - A platform to uplift and share all contributor-facing tasks in our community into one easy to find app. It will act as the basis for contributors to easily find (2-steps!) a task or job available to finish in the project. The app will help Mozillians increase participation across their projects, areas and teams by offering ways to embed relevant tasks on any on-ramp across the community.<br />
# [[Mozillians/Events_Manager|Events Manager]] - A platform to uplift and share all contributor-facing events in our community into one easy to find app. It's purpose is for contributors to easily find and participate in any event happening in our community anywhere in the world at any given time.<br />
<br />
== Management ==<br />
<br />
=== Meetings ===<br />
We have a weekly meeting where the team comes together to get synced up on various overarching topics on the product path. We post those meeting times and schedules on our google group, but you can also find that information below:<br />
<br />
* Tuesdays, 11:30AM Pacific<br />
* Backchannel: #commtools<br />
* Vidyo: 370<br />
<br />
[[Mozillians/Meetings|Meeting Archives]]<br />
<br />
=== Roadmap ===<br />
The site will be built over a series of phases. Our current thinking about milestones is below:<br />
<br />
* <strike>[[Mozillians/Milestones/Phase1|Phase1 Roadmap]] (initial launch)</strike><br />
* [[Mozillians/Milestones/Phase2|Phase2 Roadmap]] (determine and grow retention)<br />
* [[Mozillians/Milestones/Phase3|Phase3 Roadmap]] (determine and grow contributor base)<br />
<br />
Information related to the 2012 roadmap can be found [http://aakash.doesthings.com/2012/03/19/community-tools-platforms-roadmap-2012/ here]<br />
<br />
=== Documents ===<br />
* [[Mozillians/RACI |Team RACI]]<br />
* [[Mozillians/Seed group|Seed group]] -- Group of people invited to join site at launch to form a seed of phonebook data<br />
* [[Mozillians/Releases/Process|Release Process]]<br />
<br />
== Get Involved ==<br />
If you have comments, questions, suggestions or ideas, feel free to join the discussion at:<br />
<br />
* [irc://irc.mozilla.org#commtools #commtools IRC channel]<br />
* [http://groups.google.com/group/mozilla-dev-community-tools/topics Google Group]<br />
<br />
<br />
=== Contribute Code! ===<br />
* Find the code on our [http://www.github.com/mozilla/mozillians Github Repository]<br />
* [https://gist.github.com/2422571 Mozillians Git-Fu]<br />
* Take a look at the [https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=%5Bgood%20first%20bug%5D;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=Community%20Tools starter bugs that we've selected]<br />
<br />
To get set up, we've created a set of documentation [http://mozillians.rtfd.org/ to help guide you through the process]. For any questions or comments, please talk to aakashd or tallOwen on [irc://irc.mozilla.org#mozillians #mozillians on irc.mozilla.org] or contact us through our [https://lists.mozilla.org/listinfo/mozillians mailing list]!<br />
<br />
=== Test Releases before they go out! ===<br />
<br />
=== Translate Strings on Mozillians.org ===<br />
For this project, we're using Mozilla's Verbatim(Pootle). If you want to contribute, please register on [http://localize.mozilla.org Verbatim], then go to [https://localize.mozilla.org/projects/mozillians/ Mozillians Project], find your language and start translating.<br />
<br />
If you're not a localization leader, you're going to be able to suggest translations, and localization leader for your language will check those later and either accept or refuse those suggestions. We're advising all our contributors to contact Mozilla Localization Team for their locale(language), and coordinate with them. Localization teams contact pages can be found at https://wiki.mozilla.org/L10n:Teams . Sending an email to localization leader would be good start.<br />
<br />
In case you can't find your language in Mozillians project on Verbatim, that means nobody yet volunteered to start working on it. But that can as well be you. You can request for Mozillians project to be added in your language via [https://l10n-stage-sj.mozilla.org/webby/mozillians Webby application](using your LDAP credentials), or you can ping Milos on irc.mozilla.org, channel #l10n and #mozillians<br />
<br />
And last but certainly not the least, we've recently created a [http://l10n.mozilla-community.org/~milos/l10n-calendar/ l10n-calendar] which holds info on when do we add new strings to Verbatim and when do we release.<br />
<br />
We would love to have you on board!</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians&diff=454369Mozillians2012-07-25T15:41:23Z<p>Adesai: /* Contribute Code! */</p>
<hr />
<div>== Summary ==<br />
<br />
=== Mission ===<br />
We plan to build [http://farm8.staticflickr.com/7166/6771918759_4e2a828c2c_o.png tools and platforms that add that necessary layer of abstraction] that augment our current community platforms, programs and product pages to support Mozilla’s [http://farm8.staticflickr.com/7202/6777403942_5d8e9d2274_o.png ability to on-ramp, retain and easily organize contributors in the Mozilla Project].<br />
<br />
'''2012 Goals'''<br />
* Getting involved in the Mozilla project only takes 2-steps from any place in our community.<br />
* Mozillians will be able to know what and how they're contributing to the project.<br />
* Mozillians will be able to recognize and reward someone's contributions to the project in real-time.<br />
* Community Managers will be able to track and measure the effectiveness of their communities.<br />
<br />
=== Context ===<br />
The Mozilla project has grown to support many products and projects over the past year: Firefox (Desktop and Mobile), Thunderbird, Boot2Gecko, Apps and Identity. These products arrived in quick succession making it difficult to organize, grow, and direct the project’s communities to support them. To ramp-up our organically-created and modestly-supported community to meet the needs of this situation, the Engagement and People teams have begun driving an initiative called “Grow Mozilla”. It aims to build, develop and enable a global community of paid and volunteer Mozillians to propel our [http://www.mozilla.org/about/mission.html mission] and build great products for the web.<br />
<br />
Both teams are doing great work in building [https://wiki.mozilla.org/Grow_Mozilla#Programs programs] that helps to on-board new contributors, retain them and develop them to become leaders. We’re becoming more organized in how we approach contributor engagement. The Mozilla Reps and Stewards programs have robust infrastructure and people in place to help on-ramp and advise Mozillians at a level we haven't had before. Contributors are finding people responding to their inquiries to get involved and being directed to tasks available via many of our functional areas.<br />
<br />
Though, this isn't enough. For the thousands of requests we receive to get involved per month, about 20 end up as contributors. Further, these Stewards and Reps have limited tools at their disposal that come standard in many community-based organizations: they don't know who does what, how much they do it or when they do it across all of our communities. We need to do more to help grow our community's size and involvement that can propel our mission to support our current and future endeavors.<br />
<br />
=== Tools ===<br />
Mozillians.org is comprised of a collection of tools built to enhance engagement from our contributor base. An introduction and explanation of what each tool is and does can be found in the following wikis:<br />
<br />
# [[Mozillians/Phonebook|Phonebook]] - A platform to share, identify and communicate with Mozillians in our community. Active/Core Mozillians will be able to use their profile as a resume and passport for who they are and what they do in our community. For Reps & Stewards, they'll be able to better manage and show-off who is in their communities. New/potential contributors that come across it will be served up ways to get involved.<br />
# [[Mozillians/TaskBoard|TaskBoard]] - A platform to uplift and share all contributor-facing tasks in our community into one easy to find app. It will act as the basis for contributors to easily find (2-steps!) a task or job available to finish in the project. The app will help Mozillians increase participation across their projects, areas and teams by offering ways to embed relevant tasks on any on-ramp across the community.<br />
# [[Mozillians/Events_Manager|Events Manager]] - A platform to uplift and share all contributor-facing events in our community into one easy to find app. It's purpose is for contributors to easily find and participate in any event happening in our community anywhere in the world at any given time.<br />
<br />
== Management ==<br />
<br />
=== Meetings ===<br />
We have a weekly meeting where the team comes together to get synced up on various overarching topics on the product path. We post those meeting times and schedules on our google group, but you can also find that information below:<br />
<br />
* Tuesdays, 11:30AM Pacific<br />
* Backchannel: #commtools<br />
* Vidyo: 370<br />
<br />
[[Mozillians/Meetings|Meeting Archives]]<br />
<br />
=== Roadmap ===<br />
The site will be built over a series of phases. Our current thinking about milestones is below:<br />
<br />
* <strike>[[Mozillians/Milestones/Phase1|Phase1 Roadmap]] (initial launch)</strike><br />
* [[Mozillians/Milestones/Phase2|Phase2 Roadmap]] (determine and grow retention)<br />
* [[Mozillians/Milestones/Phase3|Phase3 Roadmap]] (determine and grow contributor base)<br />
<br />
Information related to the 2012 roadmap can be found [http://aakash.doesthings.com/2012/03/19/community-tools-platforms-roadmap-2012/ here]<br />
<br />
=== Documents ===<br />
* [[Mozillians/RACI |Team RACI]]<br />
* [[Mozillians/Seed group|Seed group]] -- Group of people invited to join site at launch to form a seed of phonebook data<br />
* [[Mozillians/Releases/Process|Release Process]]<br />
<br />
== Get Involved ==<br />
If you have comments, questions, suggestions or ideas, feel free to join the discussion at:<br />
<br />
* [irc://irc.mozilla.org#commtools #commtools IRC channel]<br />
* [http://groups.google.com/group/mozilla-dev-community-tools/topics Google Group]<br />
<br />
<br />
=== Contribute Code! ===<br />
* Find the code on our [http://www.github.com/mozilla/mozillians Github Repository]<br />
* [https://gist.github.com/2422571 Mozillians Git-Fu]<br />
* Take a look at the [https://bugzilla.mozilla.org/buglist.cgi?list_id=3826627;status_whiteboard_type=allwordssubstr;query_format=advanced;status_whiteboard=[good%20first%20bug];bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=Community%20Tools starter bugs that we've selected]<br />
<br />
To get set up, we've created a set of documentation [http://mozillians.rtfd.org/ to help guide you through the process]. For any questions or comments, please talk to aakashd or tallOwen on [irc://irc.mozilla.org#mozillians #mozillians on irc.mozilla.org] or contact us through our [https://lists.mozilla.org/listinfo/mozillians mailing list]!<br />
<br />
=== Test Releases before they go out! ===<br />
<br />
=== Translate Strings on Mozillians.org ===<br />
For this project, we're using Mozilla's Verbatim(Pootle). If you want to contribute, please register on [http://localize.mozilla.org Verbatim], then go to [https://localize.mozilla.org/projects/mozillians/ Mozillians Project], find your language and start translating.<br />
<br />
If you're not a localization leader, you're going to be able to suggest translations, and localization leader for your language will check those later and either accept or refuse those suggestions. We're advising all our contributors to contact Mozilla Localization Team for their locale(language), and coordinate with them. Localization teams contact pages can be found at https://wiki.mozilla.org/L10n:Teams . Sending an email to localization leader would be good start.<br />
<br />
In case you can't find your language in Mozillians project on Verbatim, that means nobody yet volunteered to start working on it. But that can as well be you. You can request for Mozillians project to be added in your language via [https://l10n-stage-sj.mozilla.org/webby/mozillians Webby application](using your LDAP credentials), or you can ping Milos on irc.mozilla.org, channel #l10n and #mozillians<br />
<br />
And last but certainly not the least, we've recently created a [http://l10n.mozilla-community.org/~milos/l10n-calendar/ l10n-calendar] which holds info on when do we add new strings to Verbatim and when do we release.<br />
<br />
We would love to have you on board!</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Milestones/Phase2&diff=454360Mozillians/Milestones/Phase22012-07-25T15:34:57Z<p>Adesai: /* P1: Phonebook */</p>
<hr />
<div>It’s difficult to build any plan without a basic set of metrics to guide decision-making. The purpose of this <br />
milestone is to deliver a solution that will consolidate contributor information into a centralized <br />
area. The outcomes are to garner better geographical/demographic, contributors-participation metrics and help guide the prioritization of needs for the development of tools for them.<br />
<br />
== Build tools to help retention and build involvement of our ''current'' contributors ==<br />
<br />
=== P1: [[Mozillians/Phonebook|Phonebook]] ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=657069 Land "Groups"] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=665373 Login with Browserid] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=706626 Design Overhaul] || {{done|}} || Q1 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.2/Location|Location & Timezones in Profiles]] || {{done|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Services|Phonebook API (and primary integration touch points)]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Search|Search Results]] Improvements || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || Simpler [[Mozillians/Phonebook/Registration|Registration Flow]] || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [[Mozillians/One_Phonebook_to_Rule_Them_All|Only One Mozillian Phonebook]] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
=== P2: [[Mozillians/TaskBoard|TaskBoard]] '''<font color="red">[On Hold]</font>''' ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || Release an initial task discovery tool for Mozilla || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=701899 Add in "goodfirstbug" into tasks] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
== Community Data and Visualization ==<br />
<br />
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Goal'''<br />
| style="background-color: #efefef;"| '''Metrics Sources'''<br />
| style="background-color: #efefef; width: 150px;"| '''Status'''<br />
|-<br />
| Determine the number of contributors in our community<br />
|<br />
* Mozillians' accounts<br />
|<br />
* {{done|}}<br />
|-<br />
| Determine contributor characteristics per community<br />
|<br />
* volume of contributors across groups<br />
* percentage of contributors across group tags against aggregate<br />
* volume of contributors per geographic location<br />
* percentages of contributors per geographic location against aggregate<br />
|<br />
* {{done|}}<br />
|}<br />
<br />
== Promotions ==<br />
<br />
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community and align our contributor base with their phonebook profiles. Phase 2 will be heavily promoted to our existing channels within sub-community sites such as AMO, QMO, SUMO, etc.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Channel'''<br />
| style="background-color: #efefef;"| '''Messaging'''<br />
| style="background-color: #efefef;"| '''Audience'''<br />
|-<br />
| Contributor Services w/ user accounts<br />
|<br />
* Promotions of the show vouched mozillians will have greater privileges, where possible, across the Mozilla universe.<br />
|<br />
* contributors with user accounts on our various web services such as AMO, QMO, SUMO, etc.<br />
|-<br />
| Community/Get Involved Site and Events<br />
|<br />
* Implant snippets on /contribute to contact phonebook users in "steward" group and other associations.<br />
* Add link and description to event get involved fliers to get to the snippets and contact someone<br />
* Integrate Taskboard entries specific to the host<br />
|<br />
* New/Potential contributors<br />
|-<br />
| Personal Signatures (twitter, facebook, e-mail signatures)<br />
|<br />
* Promote links to Mozillian Phonebook profiles as signatures to who they are as Mozillian contributors<br />
|<br />
* Core/Active contributors<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Milestones/Phase2&diff=454359Mozillians/Milestones/Phase22012-07-25T15:34:16Z<p>Adesai: /* P1: Phonebook */</p>
<hr />
<div>It’s difficult to build any plan without a basic set of metrics to guide decision-making. The purpose of this <br />
milestone is to deliver a solution that will consolidate contributor information into a centralized <br />
area. The outcomes are to garner better geographical/demographic, contributors-participation metrics and help guide the prioritization of needs for the development of tools for them.<br />
<br />
== Build tools to help retention and build involvement of our ''current'' contributors ==<br />
<br />
=== P1: [[Mozillians/Phonebook|Phonebook]] ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=657069 Land "Groups"] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=665373 Login with Browserid] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=706626 Design Overhaul] || {{done|}} || Q1 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.2/Location|Location & Timezones in Profiles]] || {{done|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Services|Phonebook API (and primary integration touch points)]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Search|Search Results]] Improvements || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || Simpler [[Mozillians/Phonebook/Registration|Registration Flow]] || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [[Mozillians/One_Phonebook_to_Rule_Them_All|Only One Mozillian Phonebook]] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
=== P2: [[Mozillians/TaskBoard|TaskBoard]] '''<font color="red">[On Hold]</font>''' ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || Release an initial task discovery tool for Mozilla || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=701899 Add in "goodfirstbug" into tasks] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
== Community Data and Visualization ==<br />
<br />
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Goal'''<br />
| style="background-color: #efefef;"| '''Metrics Sources'''<br />
| style="background-color: #efefef; width: 150px;"| '''Status'''<br />
|-<br />
| Determine the number of contributors in our community<br />
|<br />
* Mozillians' accounts<br />
|<br />
* {{done|}}<br />
|-<br />
| Determine contributor characteristics per community<br />
|<br />
* volume of contributors across groups<br />
* percentage of contributors across group tags against aggregate<br />
* volume of contributors per geographic location<br />
* percentages of contributors per geographic location against aggregate<br />
|<br />
* {{done|}}<br />
|}<br />
<br />
== Promotions ==<br />
<br />
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community and align our contributor base with their phonebook profiles. Phase 2 will be heavily promoted to our existing channels within sub-community sites such as AMO, QMO, SUMO, etc.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Channel'''<br />
| style="background-color: #efefef;"| '''Messaging'''<br />
| style="background-color: #efefef;"| '''Audience'''<br />
|-<br />
| Contributor Services w/ user accounts<br />
|<br />
* Promotions of the show vouched mozillians will have greater privileges, where possible, across the Mozilla universe.<br />
|<br />
* contributors with user accounts on our various web services such as AMO, QMO, SUMO, etc.<br />
|-<br />
| Community/Get Involved Site and Events<br />
|<br />
* Implant snippets on /contribute to contact phonebook users in "steward" group and other associations.<br />
* Add link and description to event get involved fliers to get to the snippets and contact someone<br />
* Integrate Taskboard entries specific to the host<br />
|<br />
* New/Potential contributors<br />
|-<br />
| Personal Signatures (twitter, facebook, e-mail signatures)<br />
|<br />
* Promote links to Mozillian Phonebook profiles as signatures to who they are as Mozillian contributors<br />
|<br />
* Core/Active contributors<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=452671Mozillians/Phonebook/Services2012-07-19T22:44:34Z<p>Adesai: /* Profile Sharing */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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 authorize users as Vouched Mozillians; thus, giving them greater access to functionality.<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# 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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=452667Mozillians/Phonebook/Services2012-07-19T22:38:09Z<p>Adesai: /* Mozillian Resume [Later] */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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 authorize users as Vouched Mozillians; thus, giving them greater access to functionality.<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Milestones/Phase2&diff=451728Mozillians/Milestones/Phase22012-07-17T21:08:58Z<p>Adesai: /* P1: Phonebook */</p>
<hr />
<div>It’s difficult to build any plan without a basic set of metrics to guide decision-making. The purpose of this <br />
milestone is to deliver a solution that will consolidate contributor information into a centralized <br />
area. The outcomes are to garner better geographical/demographic, contributors-participation metrics and help guide the prioritization of needs for the development of tools for them.<br />
<br />
== Build tools to help retention and build involvement of our ''current'' contributors ==<br />
<br />
=== P1: [[Mozillians/Phonebook|Phonebook]] ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=657069 Land "Groups"] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=665373 Login with Browserid] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=706626 Design Overhaul] || {{done|}} || Q1 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.2/Location|Location & Timezones in Profiles]] || {{done|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Services|Phonebook API (and primary integration touch points)]] || {{done|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Search|Search Results]] Improvements || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || Simpler [[Mozillians/Phonebook/Registration|Registration Flow]] || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [[Mozillians/One_Phonebook_to_Rule_Them_All|Only One Mozillian Phonebook]] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
=== P2: [[Mozillians/TaskBoard|TaskBoard]] '''<font color="red">[On Hold]</font>''' ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || Release an initial task discovery tool for Mozilla || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=701899 Add in "goodfirstbug" into tasks] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
== Community Data and Visualization ==<br />
<br />
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Goal'''<br />
| style="background-color: #efefef;"| '''Metrics Sources'''<br />
| style="background-color: #efefef; width: 150px;"| '''Status'''<br />
|-<br />
| Determine the number of contributors in our community<br />
|<br />
* Mozillians' accounts<br />
|<br />
* {{done|}}<br />
|-<br />
| Determine contributor characteristics per community<br />
|<br />
* volume of contributors across groups<br />
* percentage of contributors across group tags against aggregate<br />
* volume of contributors per geographic location<br />
* percentages of contributors per geographic location against aggregate<br />
|<br />
* {{done|}}<br />
|}<br />
<br />
== Promotions ==<br />
<br />
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community and align our contributor base with their phonebook profiles. Phase 2 will be heavily promoted to our existing channels within sub-community sites such as AMO, QMO, SUMO, etc.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Channel'''<br />
| style="background-color: #efefef;"| '''Messaging'''<br />
| style="background-color: #efefef;"| '''Audience'''<br />
|-<br />
| Contributor Services w/ user accounts<br />
|<br />
* Promotions of the show vouched mozillians will have greater privileges, where possible, across the Mozilla universe.<br />
|<br />
* contributors with user accounts on our various web services such as AMO, QMO, SUMO, etc.<br />
|-<br />
| Community/Get Involved Site and Events<br />
|<br />
* Implant snippets on /contribute to contact phonebook users in "steward" group and other associations.<br />
* Add link and description to event get involved fliers to get to the snippets and contact someone<br />
* Integrate Taskboard entries specific to the host<br />
|<br />
* New/Potential contributors<br />
|-<br />
| Personal Signatures (twitter, facebook, e-mail signatures)<br />
|<br />
* Promote links to Mozillian Phonebook profiles as signatures to who they are as Mozillian contributors<br />
|<br />
* Core/Active contributors<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Milestones/Phase2&diff=450239Mozillians/Milestones/Phase22012-07-12T18:05:26Z<p>Adesai: /* P1: Phonebook */</p>
<hr />
<div>It’s difficult to build any plan without a basic set of metrics to guide decision-making. The purpose of this <br />
milestone is to deliver a solution that will consolidate contributor information into a centralized <br />
area. The outcomes are to garner better geographical/demographic, contributors-participation metrics and help guide the prioritization of needs for the development of tools for them.<br />
<br />
== Build tools to help retention and build involvement of our ''current'' contributors ==<br />
<br />
=== P1: [[Mozillians/Phonebook|Phonebook]] ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=657069 Land "Groups"] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=665373 Login with Browserid] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=706626 Design Overhaul] || {{done|}} || Q1 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.2/Location|Location & Timezones in Profiles]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Services|Phonebook API (and primary integration touch points)]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Search|Search Results]] Improvements || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || Simpler [[Mozillians/Phonebook/Registration|Registration Flow]] || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [[Mozillians/One_Phonebook_to_Rule_Them_All|Only One Mozillian Phonebook]] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
=== P2: [[Mozillians/TaskBoard|TaskBoard]] '''<font color="red">[On Hold]</font>''' ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || Release an initial task discovery tool for Mozilla || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=701899 Add in "goodfirstbug" into tasks] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
== Community Data and Visualization ==<br />
<br />
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Goal'''<br />
| style="background-color: #efefef;"| '''Metrics Sources'''<br />
| style="background-color: #efefef; width: 150px;"| '''Status'''<br />
|-<br />
| Determine the number of contributors in our community<br />
|<br />
* Mozillians' accounts<br />
|<br />
* {{done|}}<br />
|-<br />
| Determine contributor characteristics per community<br />
|<br />
* volume of contributors across groups<br />
* percentage of contributors across group tags against aggregate<br />
* volume of contributors per geographic location<br />
* percentages of contributors per geographic location against aggregate<br />
|<br />
* {{done|}}<br />
|}<br />
<br />
== Promotions ==<br />
<br />
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community and align our contributor base with their phonebook profiles. Phase 2 will be heavily promoted to our existing channels within sub-community sites such as AMO, QMO, SUMO, etc.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Channel'''<br />
| style="background-color: #efefef;"| '''Messaging'''<br />
| style="background-color: #efefef;"| '''Audience'''<br />
|-<br />
| Contributor Services w/ user accounts<br />
|<br />
* Promotions of the show vouched mozillians will have greater privileges, where possible, across the Mozilla universe.<br />
|<br />
* contributors with user accounts on our various web services such as AMO, QMO, SUMO, etc.<br />
|-<br />
| Community/Get Involved Site and Events<br />
|<br />
* Implant snippets on /contribute to contact phonebook users in "steward" group and other associations.<br />
* Add link and description to event get involved fliers to get to the snippets and contact someone<br />
* Integrate Taskboard entries specific to the host<br />
|<br />
* New/Potential contributors<br />
|-<br />
| Personal Signatures (twitter, facebook, e-mail signatures)<br />
|<br />
* Promote links to Mozillian Phonebook profiles as signatures to who they are as Mozillian contributors<br />
|<br />
* Core/Active contributors<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=449271Privacy/Reviews/PhonebookAPI2012-07-10T18:25:19Z<p>Adesai: /* Phonebook API */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Phonebook API ===<br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| email <br />
| app database<br />
|-<br />
| display_name <br />
| app database<br />
|-<br />
| ircname <br />
| app database<br />
|-<br />
| website <br />
| app database<br />
|-<br />
| groups <br />
| app database<br />
|-<br />
| skills<br />
| app database<br />
|-<br />
| country<br />
| app database<br />
|-<br />
| region<br />
| app database<br />
|-<br />
| city<br />
| app database<br />
|}<br />
<br />
'''Communication with Community Site/Tool (ex. Exact Target)''' <br />
<br />
* Vouched Mozillian Authorization<br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| N/A<br />
| query including e-mail address <br />
| <br />
|-<br />
| ''Out:'' <br />
| N/A<br />
| is_vouched status of e-mail address<br />
| <br />
|}<br />
<br />
* Sharing of Mozillian E-mails<br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| query including specified group(s), skills or country/region/city<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| Blob of e-mail addresses corresponding to message <br />
| <br />
|}<br />
<br />
* Sharing Mozillian profile data<br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| query including specified e-mail address<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| Blob of Mozillian profile data: display_name, ircname, country/region/city, groups, skills, website<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448877Privacy/Reviews/PhonebookAPI2012-07-09T23:04:59Z<p>Adesai: /* Phonebook API */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Phonebook API ===<br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| email <br />
| app database<br />
|-<br />
| display_name <br />
| app database<br />
|-<br />
| ircname <br />
| app database<br />
|-<br />
| website <br />
| app database<br />
|-<br />
| groups <br />
| app database<br />
|-<br />
| skills<br />
| app database<br />
|-<br />
| country<br />
| app database<br />
|-<br />
| region<br />
| app database<br />
|-<br />
| city<br />
| app database<br />
|}<br />
<br />
'''Communication with Community Site/Tool (ex. Exact Target)''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| Blob of e-mail addresses corresponding to message <br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448875Privacy/Reviews/PhonebookAPI2012-07-09T22:33:09Z<p>Adesai: /* Phonebook API */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Phonebook API ===<br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| email <br />
| app database<br />
|-<br />
| display_name <br />
| app database<br />
|-<br />
| ircname <br />
| app database<br />
|-<br />
| website <br />
| app database<br />
|-<br />
| groups <br />
| app database<br />
|-<br />
| skills<br />
| app database<br />
|-<br />
| country<br />
| app database<br />
|-<br />
| region<br />
| app database<br />
|-<br />
| city<br />
| app database<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448874Privacy/Reviews/PhonebookAPI2012-07-09T22:32:17Z<p>Adesai: /* TastyPie API */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Phonebook API ===<br />
<br />
The Phonebook API allows <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| email <br />
| app database<br />
|-<br />
| display_name <br />
| app database<br />
|-<br />
| ircname <br />
| app database<br />
|-<br />
| website <br />
| app database<br />
|-<br />
| groups <br />
| app database<br />
|-<br />
| skills<br />
| app database<br />
|-<br />
| country<br />
| app database<br />
|-<br />
| region<br />
| app database<br />
|-<br />
| city<br />
| app database<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448872Privacy/Reviews/PhonebookAPI2012-07-09T22:22:37Z<p>Adesai: /* Services Tab */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== TastyPie API ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448871Privacy/Reviews/PhonebookAPI2012-07-09T22:22:21Z<p>Adesai: /* Components */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Services Tab ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
=== TastyPie API ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448856Privacy/Reviews/PhonebookAPI2012-07-09T21:50:14Z<p>Adesai: /* Components */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* Services Tab: Paid staff account will have a "Services" tab which offers an API Key Generator and instructions on how to use the API. <br />
** API Key Generator: The API Key generator is paired with the Phonebook user's log-in e-mail address and allows them access to the API. Within the "Services" tab, they'll have a reset button which gives them a newly generated API key.<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Services Tab ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
=== TastyPie API ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448855Privacy/Reviews/PhonebookAPI2012-07-09T21:47:21Z<p>Adesai: /* Architecture */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* {{bug|752997|Tracker Bug}}<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* Services Tab: Paid staff account will have a "Services" tab which offers an API Key Generator and instructions on how to use the API. <br />
** API Key Generator: The API Key generator is paired with the Phonebook user's log-in e-mail address and allows them access to the API. Within the "Services" tab, they'll have a reset button which gives them a newly generated API key.<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Component X ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448834Privacy/Reviews/PhonebookAPI2012-07-09T21:25:55Z<p>Adesai: /* Architecture */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
* [https://github.com/mozilla/mozillians/blob/master/apps/users/api.py api.py]<br />
* [http://django-tastypie.readthedocs.org/en/latest/index.html Tastypie Docs]<br />
<br />
== Components ==<br />
<br />
* Services Tab: Paid staff account will have a "Services" tab which offers an API Key Generator and instructions on how to use the API. <br />
** API Key Generator: The API Key generator is paired with the Phonebook user's log-in e-mail address and allows them access to the API. Within the "Services" tab, they'll have a reset button which gives them a newly generated API key.<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Component X ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448832Privacy/Reviews/PhonebookAPI2012-07-09T21:25:09Z<p>Adesai: /* Components */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
== Components ==<br />
<br />
* Services Tab: Paid staff account will have a "Services" tab which offers an API Key Generator and instructions on how to use the API. <br />
** API Key Generator: The API Key generator is paired with the Phonebook user's log-in e-mail address and allows them access to the API. Within the "Services" tab, they'll have a reset button which gives them a newly generated API key.<br />
* TastyPie API: Offers Paid Staff to GET from the Mozillians' Phonebook API. Currently, we only allow users to get information for irc nickname and display name, but will also include e-mail address, groups and location (by country, state/province and/or city).<br />
<br />
<br />
=== Component X ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448829Privacy/Reviews/PhonebookAPI2012-07-09T21:15:47Z<p>Adesai: /* Architecture */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' safely share Mozillian data inputted into Mozillians.org to community sites and Mozilla paid staff. The purpose is to allow contributors greater access to getting involved into our community, while making their path to contribution easier and more seamless. <br />
<br />
There are two major use cases we're trying to solve:<br />
<br />
* 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.<br />
* For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis. <br />
<br />
'''Design Documents''': <br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
== Components ==<br />
<br />
* API Key Generator: <br />
* TastyPie API:<br />
<br />
<br />
=== Component X ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Privacy/Reviews/PhonebookAPI&diff=448807Privacy/Reviews/PhonebookAPI2012-07-09T20:47:26Z<p>Adesai: /* Document Overview */</p>
<hr />
<div>= Document Overview =<br />
<br />
{|<br />
|'''Feature/Product:''' || Phonebook API<br />
|-<br />
|'''Projected Feature Freeze Date:''' || <section begin='eta' />tbd<section end='eta' /><br />
|-<br />
|'''Product Champions:''' || Aakash Desai, Jishnu Menon, James Socol<br />
|-<br />
|'''Privacy Champions:''' || (the privacy Friend you're working with)<br />
|-<br />
|'''Security Contact:''' || Curtis Koenig<br />
|-<br />
|'''Document State:''' || <section begin='status'/>{{new|template created}}<section end='status'/><br />
|}<br />
<br />
<br />
Timeline:<br />
<br />
{|<br />
|'''Architectural Overview:''' || (date TBD)<br />
|-<br />
|'''Recommendation Meeting:''' || (date TBD)<br />
|-<br />
|'''Review Complete ETA:''' || <section begin='revieweta' />tbd<section end='revieweta' /><br />
|}<br />
<br />
= Architecture =<br />
<br />
In this section, the product's architecture is described. Any individual components or actors are identified, their "knowledge" or what data they store is identified, and data flow between components and external entities is described. <br />
<br />
'''The main objective of this feature/product is:''' (describe the goals of the feature/product here)<br />
<br />
'''Design Documents''': <br />
Link to any design or architectural documents here.<br />
<br />
== Components ==<br />
<br />
Describe any major components in the system and how they interact. Also include any third-party APIs (those Mozilla does not control) and what type of data is sent or received via those APIs.<br />
<br />
=== Component X ===<br />
<br />
This component does A, B and C and interacts with component Y to do D.<br />
<br />
The tables below simply summarize the data encountered by this component. <br />
<br />
'''Stored Data:''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! What <br />
! Where<br />
|-<br />
| data type <br />
| where stored<br />
|}<br />
<br />
'''Communication with Component Y''' <br />
<br />
{| class="wikitable"<br />
|-<br />
! Direction <br />
! Message<br />
! Data <br />
! Notes<br />
|-<br />
| ''In:'' <br />
| message 1<br />
| types of data received from component Y with the message<br />
| <br />
|-<br />
| ''Out:'' <br />
| message 2<br />
| types of data sent to component Y with the message<br />
| <br />
|}<br />
<br />
<br />
= User Data Risk Minimization =<br />
<br />
In this section, the privacy champion will identify areas of user data risk and recommendations for minimizing the risk.<br />
<br />
= Alignment with Privacy Operating Principles =<br />
<br />
In this section, the privacy champion will identify how the feature lines up with Mozilla's privacy operating principles.<br />
<br />
See Also: [[Privacy/Roadmap_2011#Operating_Principles:]]<br />
<br />
====Principle: Transparency / No Surprises====<br />
(How the feature addresses this) <br />
<br />
''Recommendations'': (what can be improved)<br />
<br />
<br />
====Principle: Real Choice====<br />
<br />
''Recommendations'': <br />
<br />
<br />
====Principle: Sensible Defaults====<br />
<br />
''Recommendations'':<br />
<br />
<br />
====Principle: Limited Data====<br />
<br />
''Recommendations'':<br />
<br />
= Follow-up Tasks and tracking =<br />
<br />
{|class='wikitable'<br />
! What<br />
! Who<br />
! Bug<br />
! Details<br />
|-<br />
| {{new|Initial Overview Discussion}}<br />
| ?<br />
| <br />
| Meeting time TBD<br />
|}<br />
<br />
<br />
[[Category:Privacy/Reviews|Template]]</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Milestones/Phase2&diff=448734Mozillians/Milestones/Phase22012-07-09T17:22:35Z<p>Adesai: /* P1: Phonebook */</p>
<hr />
<div>It’s difficult to build any plan without a basic set of metrics to guide decision-making. The purpose of this <br />
milestone is to deliver a solution that will consolidate contributor information into a centralized <br />
area. The outcomes are to garner better geographical/demographic, contributors-participation metrics and help guide the prioritization of needs for the development of tools for them.<br />
<br />
== Build tools to help retention and build involvement of our ''current'' contributors ==<br />
<br />
=== P1: [[Mozillians/Phonebook|Phonebook]] ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=657069 Land "Groups"] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=665373 Login with Browserid] || {{done|}} || Q4 2011<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=706626 Design Overhaul] || {{done|}} || Q1 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.2/Location|Location & Timezones in Profiles]] || {{done|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Phonebook/Services|Phonebook API (and primary integration touch points)]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/Releases/1.4/Privacy|Privacy Controls]] || {{miss|}} || Q2 2012<br />
|-<br />
| P1 || [[Mozillians/One_Phonebook_to_Rule_Them_All|Only One Mozillian Phonebook]] || {{ok|}} || Q3 2012<br />
|-<br />
| P2 || [[Mozillians/Phonebook/Search|Search Results]] Improvements || {{ok|}} || Q3 2012<br />
|-<br />
| P2 || Simpler [[Mozillians/Phonebook/Registration|Registration Flow]] || {{ok|}} || Q4 2012<br />
|}<br />
<br />
=== P2: [[Mozillians/TaskBoard|TaskBoard]] '''<font color="red">[On Hold]</font>''' ===<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef; width: 20px;"| '''Priority'''<br />
| style="background-color: #efefef;"| '''Item'''<br />
| style="background-color: #efefef; width: 100px;"| '''Status'''<br />
| style="background-color: #efefef; width: 100px;"| '''Time Frame'''<br />
|-<br />
| P1 || Release an initial task discovery tool for Mozilla || {{ok|}} || Q3 2012<br />
|-<br />
| P1 || [https://bugzilla.mozilla.org/show_bug.cgi?id=701899 Add in "goodfirstbug" into tasks] || {{ok|}} || Q3 2012<br />
|}<br />
<br />
== Community Data and Visualization ==<br />
<br />
A public dashboard, updated daily, will need to be created that offers the following metrics for releases within this phase and previous phases.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Goal'''<br />
| style="background-color: #efefef;"| '''Metrics Sources'''<br />
| style="background-color: #efefef; width: 150px;"| '''Status'''<br />
|-<br />
| Determine the number of contributors in our community<br />
|<br />
* Mozillians' accounts<br />
|<br />
* {{done|}}<br />
|-<br />
| Determine contributor characteristics per community<br />
|<br />
* volume of contributors across groups<br />
* percentage of contributors across group tags against aggregate<br />
* volume of contributors per geographic location<br />
* percentages of contributors per geographic location against aggregate<br />
|<br />
* {{done|}}<br />
|}<br />
<br />
== Promotions ==<br />
<br />
We'll need a basic structure and plan as to how to send out applicable promotions to grow the community and align our contributor base with their phonebook profiles. Phase 2 will be heavily promoted to our existing channels within sub-community sites such as AMO, QMO, SUMO, etc.<br />
<br />
{| width="100%" cellpadding="3"<br />
|-<br />
| style="background-color: #efefef;"| '''Channel'''<br />
| style="background-color: #efefef;"| '''Messaging'''<br />
| style="background-color: #efefef;"| '''Audience'''<br />
|-<br />
| Contributor Services w/ user accounts<br />
|<br />
* Promotions of the show vouched mozillians will have greater privileges, where possible, across the Mozilla universe.<br />
|<br />
* contributors with user accounts on our various web services such as AMO, QMO, SUMO, etc.<br />
|-<br />
| Community/Get Involved Site and Events<br />
|<br />
* Implant snippets on /contribute to contact phonebook users in "steward" group and other associations.<br />
* Add link and description to event get involved fliers to get to the snippets and contact someone<br />
* Integrate Taskboard entries specific to the host<br />
|<br />
* New/Potential contributors<br />
|-<br />
| Personal Signatures (twitter, facebook, e-mail signatures)<br />
|<br />
* Promote links to Mozillian Phonebook profiles as signatures to who they are as Mozillian contributors<br />
|<br />
* Core/Active contributors<br />
|}</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Registration&diff=447476Mozillians/Phonebook/Registration2012-07-03T20:21:58Z<p>Adesai: </p>
<hr />
<div>Simply put, any contributor that wants to find another in the Mozilla Community can use the Phonebook to do that. To do so, they just need to create an account and become "Vouched" by another Vouched Mozillian already in the system. To make that easy as cutting knife through butter, the app should make it entirely easy for contributors to be found. In this wiki, we detail how the Mozillians Phonebook registration process works.<br />
<br />
== Requesting to Get Involved ==<br />
<br />
=== HomePage ===<br />
* [http://people.mozilla.com/~bpitoyo/mozillians/registration-ux/1-home.png Mock-Up]<br />
<br />
The homepage is the first page a user (e.g. registered and non-registered Mozillians.org users) likely will see. Its purpose is to explain the benefits of joining Mozillians.org. We'll need content and images that explain/display what a person can do on the site as well as the benefits that derive from its usage. Ultimately, we want users to sign-in using BrowserId whether they are logging in or registering onto the site.<br />
<br />
=== Create Profile and Matching ===<br />
* Profile Registration Mock-Up<br />
* [http://people.mozilla.com/~bpitoyo/mozillians/registration-ux/3a-groups-entered.png Skills Mock-Up]<br />
<br />
After signing in using BrowserId, the user has created a non-vouched account within the system. The next step will have them offering us greater details that help us better link them to a mentor (i.e. a Steward or Rep) within Mozilla. This entails two pages: the current create profile page and a 2nd page that asks for their interests (i.e. Groups) and abilties (i.e. skills).<br />
<br />
The groups listed will be automatically populated based off of whether there is at least one "Steward" (i.e. a person tagged to that group) who is grouped to a specified system level group. Skills are intended to be autocomplete-capable text fields.<br />
<br />
=== Follow-Up ===<br />
* [http://people.mozilla.com/~bpitoyo/mozillians/registration-ux/4-registration-finished.png Mock-Up]<br />
<br />
The last step is the follow-up page where a user can follow-up and get involved into the community on their own while they wait for a Steward/Rep to contact them. From the group's they've selected, meta-data from each group is going to be displayed (e.g. websites, code repositories, IRC channels, and steward’s profiles). <br />
<br />
When a user decides to sign-in to the Phonebook in the future, while still as a non-vouched user, they will see only this page. The full functionality of the app will only be available once that user has been vouched by another vouched Mozillian.<br />
<br />
== Vouching and Responding to Requests ==<br />
<br />
To Stewards and Mozilla Reps (those that are in those groups), the edit profile pane will feature three separate panels to handle the load of incoming requests to get involved.<br />
<br />
=== Vouching Pane ===<br />
* [http://people.mozilla.com/~bpitoyo/mozillians/edit-profile-ux/settings-vouches-invites-overview.png Vouching/Invites Overview Mock-Up]<br />
* [http://people.mozilla.com/~bpitoyo/mozillians/edit-profile-ux/vouch-multiple.png Vouching Action Behavior Diagram]<br />
<br />
This is pane is available to all users to vouch for (via the autocomplete and search) and invite Mozillians onto the Phonebook app. Users will be able to "Un-Vouch" a user by simply clicking on the close/"X" button next to a previously vouched account. From there, that account will be offered a temporary time period to stay as vouched and find another Vouched Mozillian to vouch for them. If they are not able to find a person to vouch them, their account will go to a non-vouched state.<br />
<br />
=== Received Requests Pane ===<br />
* [http://people.mozilla.com/~bpitoyo/mozillians/edit-profile-ux/settings-vouches-invites-received.png Received Requests Mock-Up]<br />
<br />
This pane will show Stewards/Reps a list of non-responded inquiries to get involved by non-vouched phonebook registrants. The inquiries listed are for those who added an Area of Interest/Group that the Steward/Rep is group'd in. Those who can view this pane, will be able to respond via e-mail to one or many of these inquiries through the pane. When a response is sent, the entry will be removed from this list and moved over to the "Responded Requests" pane. All other Stewards/Reps will also see the entry be moved into the "Responded Requests" pane as well. <br />
<br />
=== Responded Requests Pane ===<br />
* [http://people.mozilla.com/~bpitoyo/mozillians/edit-profile-ux/settings-vouches-invites-responded.png Responded Requests Mock-Up]<br />
<br />
Once a contributor has done enough for a Steward/Rep to feel like they are an active part of the community, those Stewards/Reps will have the ability to vouch one or many registrants via this pane. Once an entry has been vouched, they move off of the list and have an e-mail sent noting they are vouched and can access other parts of the app.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=447474Mozillians/Phonebook/Services2012-07-03T20:02:24Z<p>Adesai: </p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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 authorize users as Vouched Mozillians; thus, giving them greater access to functionality.<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis.<br />
<br />
=== <strike>Mozillian Resume</strike> '''<font color="red">[Later]</font>''' ===<br />
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.<br />
<br />
==Targeted Use Cases and Goals==<br />
<br />
===Short-Term/K9O===<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
===Long-Term===<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=447473Mozillians/Phonebook/Services2012-07-03T20:01:43Z<p>Adesai: /* Mozillian Passport */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
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 authorize users as Vouched Mozillians; thus, giving them greater access to functionality.<br />
<br />
====Targeted Use Cases and Goals====<br />
<br />
'''Short-Term/K9O'''<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
'''Long-Term'''<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis.<br />
<br />
=== <strike>Mozillian Resume</strike> '''<font color="red">[Later]</font>''' ===<br />
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.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesaihttps://wiki.mozilla.org/index.php?title=Mozillians/Phonebook/Services&diff=447472Mozillians/Phonebook/Services2012-07-03T20:01:10Z<p>Adesai: /* Targeted Use Cases and Goals */</p>
<hr />
<div>The phonebook is an excellent resource for Mozilla contributor information. We've had a bevy of requests to make that information more widely available to other mozilla.org properties and campaigns. The "Services" feature in the app will be a step forward to making Mozilla Connect profiles to be the one-stop-shop for contributor personas within the Mozilla Project.<br />
<br />
== Functional Principles ==<br />
<br />
* Single contributor profile across all of Mozilla.org<br />
* Standardize, Standardize, Standardize<br />
* Simple Use Cases First<br />
<br />
== Features ==<br />
=== Mozillian Passport ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894192756 Flow Diagram]<br />
<br />
Mozillians currently have a difficult time connecting and getting access to Projects and Products in our community. Further, they have to constantly type in the same information they've already added on the Mozillians Phonebook. The Phonebook aims to fix this problem by offering an API that authorize users as Vouched Mozillians (giving them greater access to functionality) as well as easily move their contributor identity across any and all mozilla.org properties. <br />
<br />
====Targeted Use Cases and Goals====<br />
<br />
'''Short-Term/K9O'''<br />
* 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.<br />
* Pierros Papadeas - Mozilla Reps Portal - Authorize contributors for greater access to features on reps.mozilla.org.<br />
* Air Mozilla - Authorize contributors to view Vouched-Mozillian-only streaming video.<br />
<br />
'''Long-Term'''<br />
* 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.<br />
* Taskboard - Authorize contributors for greater access. Populate profiles with Mozillians data. Write data into Mozillians.org profiles.<br />
* Les Orchard - MDN - Authorize contributors with greater access to wiki-editing. Populate profiles with greater amounts of data.<br />
<br />
=== Profile Sharing ===<br />
* [http://www.flickr.com/photos/aakashhdesai/6894222294 Flow Diagram]<br />
<br />
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:<br />
<br />
# 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. <br />
# For mozilla.org properties, they should be able to use to grab contributor information on a per user, per group or per location basis.<br />
<br />
=== <strike>Mozillian Resume</strike> '''<font color="red">[Later]</font>''' ===<br />
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.<br />
<br />
== Non-Goals ==<br />
* Make Mozillians.org the single sign-on solution for the Mozilla Project.</div>Adesai