making cycle/contribution analytics more useful; get parity w/ Gitprime

Problem to solve

It's been brought to field sales' attention that several of our large enterprise customers are using and benefitting from insights provided by https://www.gitprime.com/

Further details

internal dialogue here: https://gitlab.slack.com/archives/C1BBL1V3K/p1532559835000275 https://gitlab.slack.com/archives/C1BBL1V3K/p1506134989000050

Proposal

Review what data is currently collected on user contribution and determine whether that is enough to get us to parity with what our customers are paying gitprime to deliver. Much more TBD by product team assigned.

What does success look like, and how can we measure that?

A more viable -and thus used, version of cycle and contribution analytics. If contribution analytics is something that can be manually turned on/off we will be able to determine how many of our users actually turn it on via usage ping.

Links / references

https://gitlab.com/gitlab-org/gitlab-ee/issues/112

Customers using or investigating gitprime:
https://gitlab.my.salesforce.com/00161000004zq7Q
https://gitlab.my.salesforce.com/0016100001EodCA?srPos=0&srKp=001
https://gitlab.my.salesforce.com/0016100000KvaIg?srPos=1&srKp=001
https://gitlab.my.salesforce.com/00161000002xBeQ?srPos=0&srKp=001
https://gitlab.my.salesforce.com/00161000015M5Hz?srPos=0&srKp=001
https://gitlab.my.salesforce.com/0016100000NmTXS?srPos=1&srKp=001
https://gitlab.my.salesforce.com/00161000002xrgw

cc @aolson @ccornacchia @tommy.morgan @jeremy_

Edited by John Woods