[forge-dev] Analytics for JBoss Forge

Max Rydahl Andersen max.andersen at redhat.com
Thu Aug 23 04:17:30 EDT 2012

Yup - Rodney is right.

There is also http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/ which also is a requirement from legal (outlining/explaining what is done/how to opt-out again if need be etc.) 

if you want to extract some of the ubercomplexcrappygoogleanalyticsfiddly code into a shared library that would be cool by us.

p.s. google analytics has limits which we are already hitting with our usage levels so i'm considering alternative options; i.e. a openshift data collector across projects/products instead
of individuals google analytics accounts which also requiring multiple http request (bad) to gather more interesting stats 


On 22 Aug 2012, at 19:42, Rodney Russ <rruss at redhat.com> wrote:

> Lincoln,
> You can look at the Methodology section of Max's blog on this:
> https://community.jboss.org/en/tools/blog/2012/07/30/observations-from-two-year-of-ping-backs-from-jboss-tools-users
> and look through the code here:
> http://anonsvn.jboss.org/repos/jbosstools/trunk/usage/plugins/org.jboss.tools.usage/src/org/jboss/tools/usage/
> to start.
> -Rodney
> ----- "Lincoln Baxter, III" <lincolnbaxter at gmail.com> wrote:
>> Hey Max,
>> How have you guys done this in JBoss tools? Got some code/setup tips
>> we can look at? We're aware we'll need to ask the user if this is OK
>> when we start up.
>> https://issues.jboss.org/browse/FORGE-224
>> --
>> Lincoln Baxter, III
>> http://ocpsoft.org
>> "Simpler is better."
>> _______________________________________________
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/forge-dev

More information about the forge-dev mailing list