Capture policy regarding the use of Google Analytics on project pages
Submitted by Wayne Beaton @wbeaton
Link to original bug (#522674)
Description
We could frame this as an example or, perhaps, as an FAQ entry in the handbook.
The gist is that it's okay to use Google Analytics. We even provide instructions (Chris, can you provide me with a link to those instructions?). But the "keys must be shared" rule needs to be followed. No single individual (or organization) can own access to the configuration or data.
Activity
@cguindonsaid:(In reply to Wayne Beaton from comment 0)
We could frame this as an example or, perhaps, as an FAQ entry in the handbook.
The gist is that it's okay to use Google Analytics. We even provide instructions (Chris, can you provide me with a link to those instructions?). But the "keys must be shared" rule needs to be followed. No single individual (or organization) can own access to the configuration or data.
Hi Wayne,
thanks for opening a bug for this, it was on my todo list.
Here's the information for adding a custom GA code on a project website: https://wiki.eclipse.org/Using_Phoenix#Google_Analytics
@geniesaid:This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.
If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
-- The automated Eclipse Genie.
@wbeatonsaid:(In reply to Christopher Guindon from comment 1)
Here's the information for adding a custom GA code on a project website: https://wiki.eclipse.org/Using_Phoenix#Google_Analytics
This is a "how to" that will be useful for project teams that use Phoenix.
I'd like to capture the policy. Based on what I see here, we're basically saying that a project committer can insert the own analytics id onto the project pages and they're good-to-go.
I believe that in this case, the general policy regarding the use of "external" services applies: the keys to the analytics account must be shared and there must be a documented path to gaining access to that account/data.
Does that sound about right?
@cguindonsaid:(In reply to Wayne Beaton from comment 3)
(In reply to Christopher Guindon from comment 1)
Here's the information for adding a custom GA code on a project website: https://wiki.eclipse.org/Using_Phoenix#Google_Analytics
This is a "how to" that will be useful for project teams that use Phoenix.
I'd like to capture the policy. Based on what I see here, we're basically saying that a project committer can insert the own analytics id onto the project pages and they're good-to-go.
I believe that in this case, the general policy regarding the use of "external" services applies: the keys to the analytics account must be shared and there must be a documented path to gaining access to that account/data.
Does that sound about right?
The official policy is posted here: https://www.eclipse.org/org/documents/eclipse-foundation-hosted-services-privacy-and-acceptable-usage-policy.pdf
Google Analytics is the only approved tool for collecting user data. Use of any other tool for collecting user data requires the explicit consent of the Eclipse Foundation, which can be sought by sending a request to privacy@eclipse.org.
To use use Google Analytics, you must ensure: a) All committers on a project must have access to the data collected for that project upon request b) Eclipse Webmaster (webmaster@eclipse-foundation.org) must be an administrator on all Google Analytics properties c) The Eclipse Foundation has right to audit the use of Google analytics and the data collected, and the project must support the Eclipse Foundation in performing the audit and adjust their analytical tooling if required d) A user must be requested to give their consent, and explicit consent must be given by the user before data is collected regarding that user e) Google Analytics IP Anonymization feature must be turned on f) Projects must ensure that they are not transmitting PII to Google Analytics g) Projects must accept and follow Google Analytics Terms of Service
