Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Subject: [ANN] netdev stats and patch scoring now credit the patch author
Date: Tue, 27 Oct 2026 08:32:55 -0700	[thread overview]
Message-ID: <20261027083255.14fe214f@kernel.org> (raw)

Hi!

We're experimenting with/changing how we count patch authorship
in ml-stats. tl;dr is that we used to always count patches as
authored by the poster, now we extract authorship from within
the email, like git does.

Before
------

Previously everything in a posting counted for the sender, as an author.
Everyone else replying in the thread counted as a reviewer. 
Pull requests did not count as postings at all.

The motivation was to place the person acting as a maintainer
as a representative. For NIC vendors especially, I thought
it would be unrealistic to get all the authors to review
code upstream. Conversely the maintainers should follow the list
and bring the knowledge back to internal review.

Sadly, none of the vendor "representatives" acted on those incentives.
Perhaps it's Planck's principle at work, who knows.

The old system while trying to "incentivise" vendor representative
participation was unfairly punishing sub-maintainers (netfilter,
can, mptcp etc.) Instead of trying to separate the two groups
I decided to change the accounting.

After
-----

The patches now count for their author. Whoever sent them is still 
on the "submitting side" of the thread - their replies there are not
reviews - but they are only charged for what they wrote themselves,
like the cover letter. Authors whose patch someone else posted are
authors of that thread, not reviewers.

The "author" ranking shuffles quite a bit as all sub-maintainers 
drop out. But the top 15 individual score table does not change.
Pengutronix drops out of the negative score table since all CAN
submissions are no longer counted as Marc's work.

This change will obviously impact SUIE scores and therefore processing
order. We will keep an eye on the scores and adjust the logic as necessary.
I'm not entirely sure what to expect there, TBH.

                 reply	other threads:[~2026-10-27 15:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20261027083255.14fe214f@kernel.org \
    --to=kuba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox