Closed Bug 846049 Opened 9 years ago Closed 9 years ago

Add privacy state to profile data

Categories

(Participation Infrastructure :: Phonebook, defect)

defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED
2013-03-28

People

(Reporter: hoosteeno, Assigned: giorgos)

References

Details

On the front end we'll have dropdowns on individual profile fields that allow them to be in one of two states: "public" or "mozillians". Later there will be two more states, "staff" and "privileged". We need those states to be related to the fields they modify somehow.

The simplest proposal is of course just to add another field to the profile for each field that gets a privacy control. But this doubles the number of fields on the profile and may not be the most elegant solution. It may be the case that another model in relationship to the profile is better.

Here are the fields: 

Profile photo
Full name
IRC Nickname
Website
Bio
Country
Province/State
City
[visiblity group] Skills, Languages, Groups

The last item is a visibility group: It will have one control for the group on the frontend, but on the backend should be implemented as if it had one control per field.

We initially hoped to group Location in a visibility group, but early feedback suggests that people may want to make parts of Location public and keep other parts more protected.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
QA verified on stage - lg[reat]tm - the default setting for each field is 'Mozillian.'

Privacy settings are available for the following fields (mozillian/public):
Profile photo
Full name
IRC Nickname
Website
Bio
Country
Province/State
City
[visiblity group] Skills, Languages, Groups
Status: RESOLVED → VERIFIED
Thanks mbrandt nice work!

Just a small note that there is also a privacy setting for Persona Email in the Account section, and there privacy settings for Skills, Languages and Groups are independent. We decided not to group them together for the privacy setting :)
Thx williamr -  you confirmed my suspicion :)
You need to log in before you can comment on or make changes to this bug.