netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>, Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, netdev-driver-reviewers@vger.kernel.org,
	"Stanislav Fomichev" <sdf@fomichev.me>,
	"Simon Horman" <horms@kernel.org>,
	"Toke Høiland-Jørgensen" <toke@redhat.com>
Subject: Re: [ANN] netdev development stats for 6.7
Date: Wed, 8 Nov 2023 08:33:07 -0800	[thread overview]
Message-ID: <20231108083307.364cfe91@kernel.org> (raw)
In-Reply-To: <ff7104c9-6db9-449f-bcb4-6c857798698f@lunn.ch>

On Wed, 8 Nov 2023 14:19:31 +0100 Andrew Lunn wrote:
> > I just noticed this stats report from Simon. Thanks for your work and
> > sharing. I want to know if there is a way to bind my personal email
> > with my company so my review could increase my company's score :)  

Thanks for asking, the company association is my least favorite part 
of this work, and you gave me an excuse to rant about it :)

> Jonathan Corbet <corbet@lwn.net> maintains a list of email addresses
> to organisations mapping. Let him know who you work for and the next
> cycle you should count to your company.

Yes, unfortunately I do not have access to that list. The LWN list was
compiled with some assurances of the list not being shared. Jon / Greg
understandably did not want to send me the list and break that promise.

So telling Jon won't help me.

Now, CNCF has a similar setup: https://github.com/cncf/gitdm
and they do share their database. So I use that, plus my local hacky
mapping. Unfortunately the CNCF DB is not very up to date for kernel
folks.

Hangbin, according to CNCF you're at Red Hat, which seems sane, and
that's how I count you :)

Now the rant.

Unfortunately I can't handle creating a company/developer DB myself,
because of GDPR etc. I work for a company which takes personal
information very, very seriously.

I brought creating a public DB up at Linux Foundation TAB meetings,
but after some poking there's no movement.

To add insult to injury, if you watch past the end of the recent
(excellent) talk from Jon - https://lwn.net/Articles/949647/ you will
see Jim Zemlin pop up on the stage after Jon finishes, and you will
hear him tout the great "analytics tools" that Linux Foundation
has been working. I think he's talking about this:
https://insights.lfx.linuxfoundation.org/projects/korg/dashboard

It would be great if Linux Foundation helped the community with the
developer/company DB, which is ACTUALLY USEFUL BEFORE WASTING TIME ON
SOME WEB STUFF THAT DOESN'T WORK FOR THE KERNEL.

This makes me so angry.

  reply	other threads:[~2023-11-08 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 23:29 [ANN] netdev development stats for 6.7 Jakub Kicinski
2023-11-08 12:22 ` Hangbin Liu
2023-11-08 13:19   ` Andrew Lunn
2023-11-08 16:33     ` Jakub Kicinski [this message]
2023-11-09  1:17       ` Hangbin Liu

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=20231108083307.364cfe91@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=horms@kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=netdev-driver-reviewers@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@fomichev.me \
    --cc=toke@redhat.com \
    /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).