Niall Pemberton created MADLIB-1519:
---------------------------------------

             Summary: Remove Google Analytics from the MADlib Website
                 Key: MADLIB-1519
                 URL: https://issues.apache.org/jira/browse/MADLIB-1519
             Project: Apache MADlib
          Issue Type: Task
            Reporter: Niall Pemberton


Hi MADlib Team

The {*}ASF Privacy Policy{*}[1][2] does not permit the use of*_ Google 
Analytics_* (GA) on any ASF websites and 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]

>From what I could see, GA was removed from the main website pages in 2016, but 
>remains within the *_MADlib docs,_* from version *1.10* to the latest *2.1.0* 
>& {*}master{*}.

We need Google Analytics to be removed from the MADlib website and it looks 
like that involves changing *_doc/etc/header.html_* in the master branch and 
all branches for each of the doc versions (see below) . Would it be possible to 
do this and re-generate the MADlib docs?

||Version||No. of Files||
|docs/master|185|
|docs/v1.10|185|
|docs/v1.11|187|
|docs/v1.12|205|
|docs/v1.13|207|
|docs/v1.14|210|
|docs/v1.15|214|
|docs/v1.15.1|213|
|docs/v1.16|221|
|docs/v1.17.0|229|
|docs/v1.18.0|237|
|docs/v1.19.0|237|
|docs/v1.20.0|240|
|docs/v1.21.0|240|
|docs/v1.2|196|
|docs/v1.3|195|
|docs/v1.4|197|
|docs/v1.5|208|
|docs/v1.6|209|
|docs/v1.7|223|
|docs/v1.7.1|223|
|docs/v1.8|288|
|docs/v1.9|188|
|docs/v1.9.1|199|
|docs/v2.0.0|240|
|docs/v2.1.0|240|
|TOTAL|5,616|


 
 * [https://lists.apache.org/thread/dlbprhx4d2psjwbt0nbxs8r2j417rc4n]

The ASF hosts its own {*}_Matomo _*instance to provide projects with analytics 
and you can request a tracking id for your project by sending a mail to 
*privacy AT apache.org{*}.
 * 
[https://privacy.apache.org/faq/committers.html#can-i-use-web-analytics-matomo]

Additionally I would 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