Canmove, confirm
841
edits
Changes
Created page with "= Background = Question: How do we make vouching more meaningful so it demonstrates someone's involvement with Mozilla and helps members of Mozillians.org understand who they'..."
= Background =
Question: How do we make vouching more meaningful so it demonstrates someone's involvement with Mozilla and helps members of Mozillians.org understand who they're sharing their information with?
This is the second iteration of a proposal to improve how people sign up for Mozillians.org. The [http://hoosteeno.com/2013/10/14/refactoring-the-mozillians-org-authorization-scheme/ original context about authorization] and [http://hoosteeno.com/2013/12/17/a-new-mozillians-org-signup-process proposal] give more information.
= How vouching currently works =
* A public user can create a profile and that person's account is unvouched
* Unvouched users can only browse public profiles and do not see profiles shown only to Mozillians
* Vouched users are able to view all profiles on the site
* Any user can be vouched by another vouched user
* Paid staff are automatically vouched if they have a mozilla.org/.com email address
* If a person receives an email invitation from a vouched user, that person becomes vouched when they create an account
= New proposal =
* Vouch descriptions. Vouchers are required to give a short descripton of how the vouchee contributes to Mozilla. These descriptions are displayed on both the voucher and the vouchee's profile and are only visible to Mozillians, not shown publicly.
* Multiple vouches. A user can be vouched more than one time.
* Network of trust for vouching privilige. You must be vouched by three people in order to have the ability to vouch for other people. Once you are vouched by three people, you receive the "can_vouch" flag.
* Planned second phase that allows for automated vouching through the API.
* Visibility of profiles remains the same. Vouched users are able to view all profiles on the site.
* UI improvements include detailed language explaining who can see my information and how the network will grow.
= Upgrade path =
* All contributors who attended [[Summit2013|Summit 2013]] and all paid staff will remain vouched with their original vouch.
* All attendees of the Summit (~1750 volunteers and staff) will get 2 additional vouches with comment "Attended Summit 2013" for attending the summit (bringing their total to 3, enough to vouch others)
* Immediately following this change, vouches without comments (including those of summit attendees) will have 60 days to supplement their vouches with comments. All vouches not updated will be discarded.
* If a user with one vouch fails to get their vouch supplemented with a comment, that user will be changed to "Unvouched".
* We'll email reminders about the need to supplement vouches with comments several times during the 60-day window.
* Unvouched accounts will remain unvouched
* Employees will continue to receive one vouch upon hire, with message "Hired by Mozilla on DATE"
Question: How do we make vouching more meaningful so it demonstrates someone's involvement with Mozilla and helps members of Mozillians.org understand who they're sharing their information with?
This is the second iteration of a proposal to improve how people sign up for Mozillians.org. The [http://hoosteeno.com/2013/10/14/refactoring-the-mozillians-org-authorization-scheme/ original context about authorization] and [http://hoosteeno.com/2013/12/17/a-new-mozillians-org-signup-process proposal] give more information.
= How vouching currently works =
* A public user can create a profile and that person's account is unvouched
* Unvouched users can only browse public profiles and do not see profiles shown only to Mozillians
* Vouched users are able to view all profiles on the site
* Any user can be vouched by another vouched user
* Paid staff are automatically vouched if they have a mozilla.org/.com email address
* If a person receives an email invitation from a vouched user, that person becomes vouched when they create an account
= New proposal =
* Vouch descriptions. Vouchers are required to give a short descripton of how the vouchee contributes to Mozilla. These descriptions are displayed on both the voucher and the vouchee's profile and are only visible to Mozillians, not shown publicly.
* Multiple vouches. A user can be vouched more than one time.
* Network of trust for vouching privilige. You must be vouched by three people in order to have the ability to vouch for other people. Once you are vouched by three people, you receive the "can_vouch" flag.
* Planned second phase that allows for automated vouching through the API.
* Visibility of profiles remains the same. Vouched users are able to view all profiles on the site.
* UI improvements include detailed language explaining who can see my information and how the network will grow.
= Upgrade path =
* All contributors who attended [[Summit2013|Summit 2013]] and all paid staff will remain vouched with their original vouch.
* All attendees of the Summit (~1750 volunteers and staff) will get 2 additional vouches with comment "Attended Summit 2013" for attending the summit (bringing their total to 3, enough to vouch others)
* Immediately following this change, vouches without comments (including those of summit attendees) will have 60 days to supplement their vouches with comments. All vouches not updated will be discarded.
* If a user with one vouch fails to get their vouch supplemented with a comment, that user will be changed to "Unvouched".
* We'll email reminders about the need to supplement vouches with comments several times during the 60-day window.
* Unvouched accounts will remain unvouched
* Employees will continue to receive one vouch upon hire, with message "Hired by Mozilla on DATE"
