netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
	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: Thu, 9 Nov 2023 09:17:23 +0800	[thread overview]
Message-ID: <ZUwzI29bQB7G9yUP@Laptop-X1> (raw)
In-Reply-To: <20231108083307.364cfe91@kernel.org>

Hi Jakub,
On Wed, Nov 08, 2023 at 08:33:07AM -0800, Jakub Kicinski wrote:
> 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 :)

Thanks for this info. Glad to know my email and company are mapping correctly.

> I brought creating a public DB up at Linux Foundation TAB meetings,
> but after some poking there's no movement.
> 
> 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.

I personally agree Linux Foundation should maintain a developer/company DB.
The developer could submit their information on a voluntary basis, instead of
letting some tools search the website and collect data.

Thanks
Hangbin

      reply	other threads:[~2023-11-09  1:17 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
2023-11-09  1:17       ` Hangbin Liu [this message]

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=ZUwzI29bQB7G9yUP@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --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).