Closed Bug 679405 Opened 13 years ago Closed 11 years ago

api: Request for an API for aggregated contributors metrics from MDN

Categories

(developer.mozilla.org Graveyard :: User management, task)

x86
Windows Mobile 6 Professional
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: aakashd, Assigned: lorchard)

References

Details

(Whiteboard: c=api u=mozilla p=2)

The Phonebook team is planning on incorporating contributor metrics into phonebook (i.e. mozillians.org) profiles in the future. To do so, the app will need access to the following information: * contributor e-mail address * number of docs created * number of demos created ...and any other useful statistics. There's no hardset timetable for this, but the sooner the better (i.e. Q4 2011).
Blocks: 679407
pulling into 1.1 so we discuss at our next planning meeting. sounds cool!
Whiteboard: c=api u=mozilla p=
Target Milestone: --- → 1.1
(In reply to Aakash Desai [:aakashd] from comment #0) > The Phonebook team is planning on incorporating contributor metrics into > phonebook (i.e. mozillians.org) profiles in the future. To do so, the app > will need access to the following information: > > * contributor e-mail address > * number of docs created > * number of demos created > > ...and any other useful statistics. There's no hardset timetable for this, > but the sooner the better (i.e. Q4 2011). Would a JSON object per-user work for this? Might not be too hard to knock together a summary report. Also... can you nail down and define "any other useful statistics"? There's no timetable until that happens.
A JSON object per-user would work fine. I just talked to Jay and those two metrics will be enough. So, let's cut out "any other useful statistics" for now until it becomes more hard-defined :).
Summary: Request for an API for aggregated contributors metrics from MDN → api: Request for an API for aggregated contributors metrics from MDN
We'll add a json endpoint for every user with a profile. How do you want to get the list of users? Should we provide a json list too, or do you want to query with a specific parameter? (e.g., email address?)
Whiteboard: c=api u=mozilla p= → c=api u=mozilla p=1
I'd lean toward the latter, but I'd rather have ozten make that call since he's got an idea of how he wants a web service api to work with the phonebook.
Target Milestone: 1.1 → 1.2
Eventually the phonebook would have a "system id" for MDN which is probably the username. Being able to query by username would be great, or you could establish a URI pattern that takes username into account which would be even better.
FWIW, we probably shouldn't ever have an API to list users, at least not as a public resource. That could be troublesome for privacy or other miscellaneous reasons. Easy enough will be something like this: * A <link rel="alternative" type="application/json"> element in the <head> of the HTML version of the page - https://developer.mozilla.org/en-US/profiles/lmorchard/ * JSON resource at an URL like this - https://developer.mozilla.org/en-US/profiles/feeds/json/profile/lmorchard With that, you can ask for either an HTML profile URL and discover the JSON resource, or ask for a username and assemble the JSON resource URL from a template.
All-hands de-reailed 1.2. Bumping to 1.3.
Target Milestone: 1.2 → 1.3
Whiteboard: c=api u=mozilla p=1 → c=api u=mozilla p=2
Target Milestone: 1.3 → 1.4
Assignee: nobody → lorchard
OS: Mac OS X → Windows Mobile 6 Professional
Target Milestone: 1.4 → 1.2
Whoops. Looks like I changed the milestone inadvertently
Target Milestone: 1.2 → 1.4
Target Milestone: 1.4 → ---
Hey All, FYI: We're looking to implement contributor metrics (at least with Bugzilla and any other services that are available) on Mozillians.org in mid-Q1/2012. So, we'd need the hooks by the end of the quarter for enough ramp-up time on our end.
Component: Administration → User management
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.