Closed
Bug 896484
Opened 11 years ago
Closed 11 years ago
Track the number of monthly KB contributors to each locale
Categories
(support.mozilla.org :: Knowledge Base Software, task, P2)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
VERIFIED
FIXED
2013Q3
People
(Reporter: rrosario, Assigned: rrosario)
References
Details
(Whiteboard: u=contributor c=wiki p=2 s=2013.15)
Community managers and l10n leaders want to see the historical # of active contributors to a locale. In bug 889913, we're creating a model to store these locale-based metrics. We can use that to store monthly localization contributors for each locale. We probably want to add a monthly cronjob that goes through each locale and counts the contributors from the last 30 days and saves it to the metrics table. A contributor is a user that submitted or reviewed a revision for the locale.
Assignee | ||
Updated•11 years ago
|
Whiteboard: u=contributor c=wiki p= s=2013.15
Assignee | ||
Comment 1•11 years ago
|
||
Just need a cron job and a simple~ish orm query to get the users for each locale in a loop. And a test or two. 1pt
Whiteboard: u=contributor c=wiki p= s=2013.15 → u=contributor c=wiki p=1 s=2013.15
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → rrosario
Assignee | ||
Comment 2•11 years ago
|
||
In a pull request: https://github.com/mozilla/kitsune/pull/1535
Assignee | ||
Comment 3•11 years ago
|
||
Landed on master: https://github.com/mozilla/kitsune/compare/2b31452c4d6e...199c203d4804 I underestimated this. Adjusting it to 2pts.
Whiteboard: u=contributor c=wiki p=1 s=2013.15 → u=contributor c=wiki p=2 s=2013.15
Assignee | ||
Comment 4•11 years ago
|
||
Deployed to prod now. This data isn't graphed yet, but you can browse it in the admin: https://support.mozilla.org/admin/dashboards/wikimetric/?code__exact=active_contributors
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 5•11 years ago
|
||
Ricky this is amazing! I'm really looking forward to see the graphs!
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•