joomla-developer-docs
joomla-developer-docs copied to clipboard
Analytics for activity
I need some ideas for what analytics metrics we can use for reporting activity. I want something that is meaningful to show progress but also recognises who is actually doing the work (and hopefully entice others to do the same).
For example, the API for pull requests, http://developer.github.com/v3/pulls/#get-a-single-pull-request, shows additions and deletions which we could use against a user name (number of pull requests, number of adds and deletes, number of comments they have made, etc).
@mbabker and I can add Google Analytics. Also does this help? https://github.com/blog/1672-introducing-github-traffic-analytics
Github is also introducing analytics built into it as well. It would be interesting to see what kind of data that would yield.
Thanks, David Hurley On Jan 12, 2014 1:45 PM, "jessicadunbar" [email protected] wrote:
@mbabker https://github.com/mbabker and I can add Google Analytics. Also does this help? https://github.com/blog/1672-introducing-github-traffic-analytics
— Reply to this email directly or view it on GitHubhttps://github.com/joomla/joomla-developer-docs/issues/16#issuecomment-32129929 .
For GitHub based activity, I'd suggest starting with the data available in the existing graphs and if we need more, then we hook into the API and deploy a small application with our fine tuned data.
Yep, certainly easy to use the existing graphs, the new graph I believe pulls in other analytics as well is all. Their API I'm sure would be more robust if we determine we need that in a custom app.
Thanks, David Hurley On Jan 12, 2014 2:17 PM, "Michael Babker" [email protected] wrote:
For GitHub based activity, I'd suggest starting with the data available in the existing graphs https://github.com/joomla/joomla-developer-docs/graphsand if we need more, then we hook into the API and deploy a small application with our fine tuned data.
— Reply to this email directly or view it on GitHubhttps://github.com/joomla/joomla-developer-docs/issues/16#issuecomment-32130866 .