[
https://issues.apache.org/jira/browse/UIMA-4563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15062679#comment-15062679
]
Lou DeGenaro commented on UIMA-4563:
------------------------------------
The uima-ducc-demo http://uima-ducc-demo.apache.org:42133/jobs.jsp has been
recently Google Analytics (GA) enabled. Here's what's been done:
1. I visited https://www.google.com/analytics/ and created an account called
uima-ducc-demo.apache.org
2. I took the small generated javascript and the account id and marked up the
DUCC demo pages, which results in the recording of visits to GA
3. I added the uima-ducc committers as having the ability to view and manage
the GA account, including adding/deleting/modifying users by using the Admin tab
This means that GA is active for the uima-ducc-demo, and that the uima-ducc
committers are able to both view reports and manage users. Possible GA
privileges are: Manages Users, Edit, Collaborate, Read and Analyze.
Some questions:
1. What should the policy be for different GA privileges?
2. Do we add the other Apache UIMA web pages to GA?
3. If so, do we want to have one GA account for all or should the
uima-ducc-demo remain separate?
4. Other concerns?
I agree with Richard that the privacy statement already in place seems to meet
our obligations.
I see no problem with adding other UIMA committers to have Read and Analyze (at
the minimum) authority to the uima-ducc-demo GA account, initially.
Discussion welcomed.
> Traffic monitoring using Google Analytics
> -----------------------------------------
>
> Key: UIMA-4563
> URL: https://issues.apache.org/jira/browse/UIMA-4563
> Project: UIMA
> Issue Type: Improvement
> Components: Website
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
>
> Apparently, the ASF main page uses Google Analytics now as well, so I think
> we can also do that - they have privacy statement that we can simply reuse.
> http://www.apache.org/foundation/policies/privacy.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
