Closed Bug 966290 Opened 9 years ago Closed 8 years ago

Establish Baseline contributor #s from last year

Categories

(Webmaker Graveyard :: Engagement Ladder, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: michelle, Assigned: michelle)

Details

(Whiteboard: [workweek][workweek-engagement][engagement][infrastructure])

Publish them on the Webmaker wiki.
Whiteboard: [workweek][workweek-engagement] → [workweek][workweek-engagement][engagement]
Setting up a chat with Adam and Jbuck to figure out what #s we want to look at.
Flags: needinfo?(adam)
Assignee: nobody → michelle
I've now filled in a couple of other rows that had my name against them after our last call (mailing list and SUMO).

Is the 5000+ number from my other spreadsheet combining all mofo? In this spreadsheet I think we're ~3200.
Flags: needinfo?(adam)
* Is this one done?
Component: General → Engagement Ladder
QA Contact: brett
Status: NEW → ASSIGNED
I think so. 

My view is that making the baseline numbers any more accurate at this point isn't adding further value. (We have a good feel for the numbers now).

Next step is counting these things for real, in real-time and feeding them into our contributor dashboard.

Here's a general update on the dashboard:
http://adamlofting.com/1057/a-quick-update-on-the-interim-contributor-dashboard/

This is where I'm tracking status of each of the things we want to count:
https://docs.google.com/a/mozillafoundation.org/spreadsheet/ccc?key=0AnUkMzboH_XAdFF5RWdYSjh2Nld1ZVNDVmx5LU8wUWc&usp=drive_web#gid=0

And the priority for webmaker is an API to count events activity as that's the biggest 'pot' of contributors currently in a single database. (Bug 966101)
Whiteboard: [workweek][workweek-engagement][engagement] → [workweek][workweek-engagement][engagement][infrastructure]
This has been resolved and is up to date in Adam's spreadsheets
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.