966101 - [meta] Create a service for tracking contribution

Status: RESOLVED FIXED

(Webmaker Graveyard :: Engagement Ladder, defect)

Description

[Brett Gaylor [:brett]]

When users cross a conversion point on our engagement ladder, makermind should update our user model and then take action.  See attached systems map.

Comment 1

[Brett Gaylor [:brett]]

Attachment: makermind.pdf

Comment 2

[Michelle Thorne]

Attachment: makermind prototype screenshot.png

Screenshot of the prototype Jbuck made at the workweek

Comment 3

[Adam Lofting (:adamlofting)]

Following our call, here is the spec for the API we need in order to extract contributor numbers from this: https://docs.google.com/a/mozillafoundation.org/document/d/16Sas-dbBzSftWqacYhFRojjXLCkAXu6h2XxbkfALG-Q/edit

Initial goal is to get this running for the Events database.

Comment 4

[Matt Thompson (@OpenMatt :OpenMatt)]

* Sweet! Status update on this one?
* Can we do a check-in on Maker Mind status in Mar 26 Webmaker.org call?

Comment 5

[Adam Lofting (:adamlofting)]

FYI, we're now in a position to start using this data-source on the live dashboard (when it's ready):
http://adamlofting.com/1057/a-quick-update-on-the-interim-contributor-dashboard/

Comment 6

[Brett Gaylor [:brett]]

Jon is creating a series of apps for this work based on themes surrounding "logs".  Stay tuned.

Comment 7

[Adam Lofting (:adamlofting)]

I suggest we close this particular ticket now.

The new bugs we've setup capture the work required to count contributors and get them onto the dashboard, and the general task of 'prototyping MakerMind' was completed at the work-week.

How about we re-use the MakerMind name for the API project reporting on user metrics? (Bug 994565) It could be the MakerMindReader ;)

Comment 8

[Jon Buckley [:jbuck]]

It's not closed until the dependent bugs sing!

Comment 9

[Matt Thompson (@OpenMatt :OpenMatt)]

Thanks for renaming this JBuck -- smart hack.