[
https://issues.apache.org/jira/browse/GROOVY-11561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926011#comment-17926011
]
Niall Pemberton commented on GROOVY-11561:
------------------------------------------
One other thing to consider is the rest of the Content Security Policy (CSP)
which is due to come into effect permanently next month and will prevent any
resources being loaded from 3rd Party providers that the ASF does not have a
Data Processing Agreement (DPA) with:
* [https://lists.apache.org/thread/w34sd92v4rz3j28hyddmt5tbprbdq6lc]
Whimsy has a tool to check a page and running it against the current Geb Manual
produces the following:
*
[https://whimsy.apache.org/members/page-scanner?url=https://groovy.apache.org/geb/manual/current/]
{code:java}
======
Top-level references:
NO
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
NO https://ssl.google-analytics.com/ga.js
NO
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1078697879&utmhn=groovy.apache.org&utmcs=UTF-8&utmsr=800x600&utmvp=800x600&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=The%20Book%20Of%20Geb&utmhid=1288837981&utmr=-&utmp=%2Fgeb%2Fmanual%2Fcurrent%2F&utmht=1739267047205&utmac=UA-15031038-2&utmcc=__utma%3D47492081.1826786521.1739267047.1739267047.1739267047.1%3B%2B__utmz%3D47492081.1739267047.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=1197247184&utmredir=1&utmu=qACAAAAAAAAAAAAAAAAAAAAE~
Transitive references:
Loaded by:
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css
NO
https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts/fontawesome-webfont.woff2?v=4.7.0
=====
{code}
However, it looks like the Whimsy tool isn't that smart because when I look in
*./css/style.css* it also looks like the page is using *_Google Fonts_* as well
as Fontawesome.
So, not sure what effect that is going to have on the Geb Manual's L&F, but Geb
would need to host these fonts locally within its site to use them.
Lastly, one other issue which may influence the choice you make in how to
resolve this, I notice a broken link in the manual due to the fact that
markmail no longer exists. Perhaps that doesn't matter for old docs, but
extracting from the repo doesn't allow you to fix these types of things if you
desire
* [http://markmail.org/thread/bu3g56oxz2uqzq43]
> Remove Old groovy-pekka-gpars.html File
> ---------------------------------------
>
> Key: GROOVY-11561
> URL: https://issues.apache.org/jira/browse/GROOVY-11561
> Project: Groovy
> Issue Type: Task
> Components: Documentation
> Reporter: Niall Pemberton
> Assignee: Paul King
> Priority: Minor
>
> Hi Groovy Team,
> There is one page on the Groovy Website that contains _*Google Analytics*_
> and it causes Groovy to come up on a monthly report to the {_}*Privacy
> Committee*{_}:
> * [https://groovy.apache.org/blog/groovy-pekka-gpars.html]
> *
> [https://github.com/apache/groovy-dev-site/blob/asf-site/blog/groovy-pekka-gpars.html]
> It hasn't been updated in *2 years* and there is no equivalent file in the
> _*groovy-website*_ repo. It looks like this page was renamed from
> *groovy-pekka-gpars* to *groovy-pekko-gpars:*
> * OLD: [https://groovy.apache.org/blog/groovy-pekka-gpars.html]
> * NEW: [https://groovy.apache.org/blog/groovy-pekko-gpars.html]
> I will submit a PR against the _*groovy-dev-site*_ repo to remove this page.
> Thanks
> Niall
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
