Niall Pemberton created JCLOUDS-1645:
----------------------------------------

             Summary: Remove Google Analytics from Old Javadoc Versions
                 Key: JCLOUDS-1645
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1645
             Project: jclouds
          Issue Type: Task
          Components: docs
            Reporter: Niall Pemberton
            Assignee: Andrew Gaul


Hi jclouds team!

There are *56,000+* files in your old javadocs (versions *1.7.x* to 
{*}2.1.x{*}) that contain _*Google Analytics*_ on the jclouds website:

 
||Location||Number of Files||
|reference/javadoc/1.7.x/|10,643|
|reference/javadoc/1.8.x/|11,080|
|reference/javadoc/1.9.x/|10,567|
|reference/javadoc/2.0.x/|11,428|
|reference/javadoc/2.1.x/|13,023|
|*Total*|*56,741*|

 

The ASF {_}*Privacy Policy*{_}[1][2] does not permit the use of _*Google 
Analytics.*_ Please could you remove the use of the Google Analytics from the 
jclouds website?
 *  [https://lists.apache.org/thread/c1cyqcfv1t9kkxpd3797ltooolo8hojg]

 

The ASF Infra team will soon enforce a {_}*Content Security Policy*{_}(CSP) 
that will block access to external trackers:
 * [https://lists.apache.org/thread/w34sd92v4rz3j28hyddmt5tbprbdq6lc]

I would also recommend reviewing any external resources loaded by your website. 
The Content Security Policy will prevent any resources being loaded from 3rd 
Party providers that the ASF does not have a Data Processing Agreement (DPA) 
with. On the 1st February Infra will begin a temporary "brownout" when the CSP 
will be turned on for a short period. This will allow projects to check which 
parts, if any, of their websites will stop working. The Privacy FAQ answers a 
number of questions about which external providers are permitted or not:
 * [https://privacy.apache.org/faq/committers.html]

Thanks

Niall

[1] [https://privacy.apache.org/policies/website-policy.html]
[2] [https://privacy.apache.org/faq/committers.html#can-i-use-google-analytics]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to