add analytics script

[ayhamthemayhem]

Hey there,

This is part of our work at Neighbourhoodie/ with STF's Bug Resilience Program for Log4j.

This is a PR to add a script file that can be loaded into other logging websites to load matomo analytics scripts for website based on if they are dormant or active.

I used an example of a matomo script that we found here

Do you maybe have an example of what a matomo script for dormant websites looks like ?

[rgoers]

Why would you skip dormant projects? At some point flume will be coming back into the fold and I won't want to remember to have to modify this.

@grobmeier It looks like you added a link to analytics.apache.org? What is that?

[ppkarwasz]

@ayhamthemayhem,

Could you also remove Matomo from footer.html and add a reference to your script to header.html?

I don't think there should be a difference between dormant and active subproject. Maybe we could add some custom dimension, but I don't know what would make sense.
Certainly, for GDPR reasons we need to ask user for their consent to track them (see managing consent). That fact must have slipped our mind when we added Matomo. @grobmeier, am I right?

@rgoers,

analytics.apache.org contains an on premises installation of the Matomo tracking software. It should be useful to track the popularity of pages and also find out the 404 errors.

[ayhamthemayhem]

Why would you skip dormant projects? At some point flume will be coming back into the fold and I won't want to remember to have to modify this.

Hey, dormant projects are not skipped they just have a different script than others but that is also still unclear and up to discussing which projects go to which array but and that is up to the log4j team to decide.

[ayhamthemayhem]

Could you also remove Matomo from footer.html and add a reference to your script to header.html?

done !

[ayhamthemayhem]

If there is a list or more info on which websites are dormant or skipped that would be great.
I would adjust the PR quickly as needed :)

[ppkarwasz]

This looks good to me,
but I would wait for a review of our V.P. Data Privacy (@grobmeier) before merging it. 😉