From: Jakub Kicinski <kuba@kernel.org>
To: workflows@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: corbet@lwn.net, ast@kernel.org
Subject: Simple analytics for docs.kernel.org and patchwork, please?
Date: Fri, 23 Feb 2024 08:31:54 -0800 [thread overview]
Message-ID: <20240223083154.4fbee63c@kernel.org> (raw)
Hi!
We have a few netdev-related bots with various simple status pages.
I hooked them up to analytics recently, here's the dash:
https://plausible.io/netdev.bots.linux.dev
Plausible was described here: https://lwn.net/Articles/822568/
it's supposedly-open, and privacy-focused, no cookies etc.
It's useful for me when deciding where to invest my time,
and to back up the efforts to my employer with some data.
Now, most of us agree that kernel docs leave something to be desired.
At the same time maintainers are repeatedly faced with people who post
code without reading the docs, which puts the time invested in writing
them into question. I can't help but think that providing some
analytics for docs.kernel.org traffic would be beneficial.
I would use it.
Thoughts?
Does anyone think that even non-intrusive analytics are a no go?
Does anyone know better alternatives than Plausible?
next reply other threads:[~2024-02-23 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:31 Jakub Kicinski [this message]
2024-02-23 17:14 ` Simple analytics for docs.kernel.org and patchwork, please? Mauro Carvalho Chehab
2024-02-23 17:49 ` Jonathan Corbet
2024-02-23 20:02 ` Jakub Kicinski
2024-02-26 19:06 ` Jakub Kicinski
2024-02-26 19:24 ` Konstantin Ryabitsev
2024-02-26 19:43 ` Jakub Kicinski
2024-02-26 19:58 ` Jonathan Corbet
2024-02-26 22:52 ` Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240223083154.4fbee63c@kernel.org \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=workflows@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).