From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Cc: intel-wired-lan@lists.osuosl.org
Subject: [Intel-wired-lan] [ANN] development stats for time periods
Date: Mon, 23 Jun 2025 10:45:28 -0700 [thread overview]
Message-ID: <20250623104528.74ce41da@kernel.org> (raw)
Hi!
The first half of 2025 is coming to a close and I suspect some
companies are working through employee performance reviews.
Our development stats are are bit awkward to use for performance
reviews because release cycles don't align with 6mo or 12mo windows.
I added a cron job to generate the development stats each weekend
for the last X months:
https://netdev.bots.linux.dev/static/nipa/stats-1mo/
https://netdev.bots.linux.dev/static/nipa/stats-3mo/
https://netdev.bots.linux.dev/static/nipa/stats-6mo/
https://netdev.bots.linux.dev/static/nipa/stats-12mo/
This should hopefully make it easier to claim credit for upstream work.
HTH
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org
Cc: intel-wired-lan@lists.osuosl.org
Subject: [ANN] development stats for time periods
Date: Mon, 23 Jun 2025 10:45:28 -0700 [thread overview]
Message-ID: <20250623104528.74ce41da@kernel.org> (raw)
Hi!
The first half of 2025 is coming to a close and I suspect some
companies are working through employee performance reviews.
Our development stats are are bit awkward to use for performance
reviews because release cycles don't align with 6mo or 12mo windows.
I added a cron job to generate the development stats each weekend
for the last X months:
https://netdev.bots.linux.dev/static/nipa/stats-1mo/
https://netdev.bots.linux.dev/static/nipa/stats-3mo/
https://netdev.bots.linux.dev/static/nipa/stats-6mo/
https://netdev.bots.linux.dev/static/nipa/stats-12mo/
This should hopefully make it easier to claim credit for upstream work.
HTH
next reply other threads:[~2025-06-23 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 17:45 Jakub Kicinski [this message]
2025-06-23 17:45 ` [ANN] development stats for time periods 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=20250623104528.74ce41da@kernel.org \
--to=kuba@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.