From:  Gervase Markham <gerv@mozilla.org>
Date:  29 Mar 2013 18:49:16 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.bugmasters
Subject:  

Re: Bugzilla.mozilla.org user profiles

NNTP-Posting-Host:  63.245.216.66

On 27/03/13 19:21, Liz Henry wrote:
> I know that Gerv has had some intentions to use the Mozillians API in
> some way inside bugzilla, perhaps to display a link to a contributor's
> Mozillians.org profile in a tooltip.

My concern here is that many Mozillians already have multiple profiles -
a Reps one, a mozillians.org one, addons, SUMO... We want to avoid
multiplying profiles across Mozilla sites - it's a pain to keep it all
updated and in sync. Instead, we should be moving towards storing
generic profile information (name, email, photo, interests) centrally in
mozillians.org, and using that data on other products and sites,
displayed together with product-specific stuff like bug filing rates or
whatever.

My plan is basically this. When a user logs into Bugzilla, Bugzilla
checks with mozillians.org to see if they are a vouched Mozillian. If
they are, Bugzilla remembers, and when it serves any bit of UI
mentioning a person, you get a marker next to their name:

Comment 3 by Gervase Markham (?) on 2013-03-04 ...

If you click on the ?, you get an in-page popup, where the page asks
Bugzilla for user info, Bugzilla checks you are authorized to get it,
and then gets it from Mozillians and returns it in a nicely-formatted
form and puts it in the popup. (This slightly roundabout method is
required by the security design of the Mozillians API. If and when
Mozillians allows some info to be public, then this might be changed to
request info directly.)

The popup might look something like this:

Gervase Markham                       Photo
gerv                                  over
Sheffield, UK                         here

I work on: community peacekeeping, Bugzilla and
bugzilla.mozilla.org, security...

[More info]


The point of this is that we can get to know each other better when we
have more info to "hang" an interaction on than just a Bugzilla handle.
It makes people more memorable.

Of course, having a plan and having time to implement it are two
different things. If anyone has some cycles and is interested in doing
this, let me know. Bugzilla's in Perl (although I could help with that),
and you'll need to know JS and CSS too.

Gerv