Add matomo tracker for javadoc #15326
Conversation
|
I don't think we should add such trackers to javadoc. To the website - yes, but not to the javadoc. I don't think it'll be useful. |
|
Maybe it could tell us something about the versions of the documentation being looked up |
|
I'm reluctant about this. It gets added to all javadocs everywhere - even if you generate them locally. I'm not so fond of those trackers, maybe that's why I feel uneasy about adding them here. |
|
If you install ublock origin lite, the network request will never even happen. |
|
I do have it. It's in my head though (the tracker). |
|
hi folks!
I was adding this since the website is minimal, and I figured we'd
understand the usage patterns of the docs better (e.g. most useful classes
/ versions being used) - however I understand your reluctance. Also, I
agree it wouldn't make sense to have reporting for local builds of the
javadoc.
A counter-argument for the version question (having used versioned javadocs
myself) is that I often don't care much about the version and will just
click whatever Google gives me unless the thing I'm using was added
recently.
Happy to wait for more feedback, or just close this.
…On Fri, Oct 10, 2025 at 1:02 PM Dawid Weiss ***@***.***> wrote:
*dweiss* left a comment (apache/lucene#15326)
<#15326 (comment)>
I do have it. It's in my head though (the tracker).
—
Reply to this email directly, view it on GitHub
<#15326 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ5Z3GSKNVL4676XB6PDW33XAGFBAVCNFSM6AAAAACI3UN4JSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJSGE2TGOBXGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
Would it be ok to add it optionally? So, for example, we can add it only to releases? |
|
I moved the tracker to be added when building release javadoc! (depending on lucenedocurl, which is only defined on releases). LMK what y'all think @dweiss |
3 participants
Description