netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: netdev development stats for 6.1?
Date: Fri, 7 Oct 2022 09:44:27 +0300	[thread overview]
Message-ID: <Yz/KyyT/oLsy4lK5@unreal> (raw)
In-Reply-To: <20221004212721.069dd189@kernel.org>

On Tue, Oct 04, 2022 at 09:27:21PM -0700, Jakub Kicinski wrote:
> Hi!
> 
> For a while now I had been curious if we can squeeze any interesting
> stats from the ML traffic. In particular I was curious "who is helping",
> who is reviewing the most patches (but based on the emails sent not just
> review tags).
> 
> I quickly wrote a script to scan emails sent to netdev since 5.19 was
> tagged (~14k) and count any message which has subject starting with
> '[' as a patch and anything else as a comment/review. It's not very
> scientific but the result for the most part matches my expectations.
> 
> A disclaimer first - this methodology puts me ahead because I send
> a lot of emails. Most of them are not reviews, so ignore me.
> 
> Second question to address upfront is whether publishing stats is
> useful or mostly risks people treating participation as a competition
> and trying to game the system? Hard to say, but if even a single person
> can point to these stats to help justify more time spent reviewing to
> their management - it's worth it.
> 
> That said feedback is very welcome, public or private.

I think that it is right initiative which will make netdev community
stronger and wider.

As for the feedback, which express my personal view as an outsider in netdev.

I think that more clear goals for that statistics can help to purify
which tables are actually needed as I'm sure that not all are needed.

My goals are:
1. See that load spreads more equity. It will indirectly cause to spread
of the knowledge. The most active reviewers are the most knowledgeable
developers too.
2. Push companies to participate in code maintenance (review) and not
only enjoy from free rides.

Thanks

  reply	other threads:[~2022-10-07  6:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05  4:27 netdev development stats for 6.1? Jakub Kicinski
2022-10-07  6:44 ` Leon Romanovsky [this message]
2022-10-07 18:59 ` Florian Fainelli
2022-10-09  3:21 ` Sean Anderson
2022-10-17 18:03 ` 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=Yz/KyyT/oLsy4lK5@unreal \
    --to=leon@kernel.org \
    --cc=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;
as well as URLs for NNTP newsgroup(s).