linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xu Yilun <yilun.xu@intel.com>
To: Moritz Fischer <mdf@kernel.org>
Cc: linux-fpga@vger.kernel.org, gregkh@linuxfoundation.org, hao.wu@intel.com
Subject: Re: Maintenance of Linux FPGA
Date: Sun, 26 Sep 2021 13:44:49 +0800	[thread overview]
Message-ID: <20210926054449.GD806603@yilunxu-OptiPlex-7050> (raw)
In-Reply-To: <YU9s27qwyzmeONiq@epycbox.lan>

On Sat, Sep 25, 2021 at 11:39:23AM -0700, Moritz Fischer wrote:
> Hi all,
> 
> I lately did not have enough time to dedicate to the Linux FPGA
> subsystem, concerns were raised around bus-factor and all.
> 
> Looking at my day-job I don't see this getting better in the short-term
> so I've decided to get a conversation going on how to structure this
> better for the benefit of the Linux FPGA subsystem.
> 
> Maybe a maintainer team approach would address the bus factor and
> workload concerns better?
> 
> In terms of people I was thinking about:
> 
> Hao has done a great job at keeping the DFL part of things going, so I
> think he'd be a great choice.
> 
> Yilun has been very helpful with reviews and I think he'd be a good
> pick, too.

It's my pleasure for the nomination and yes I'd like to be one of the
maintainer team, to be more helpful.

Thanks,
Yilun

> 
> In terms of how to structure this: I'm not sure just yet, open to input.
> 
> How do other multi-maintainer subsystems operate? Ideas? Suggestions?
> 
> Let me know what you think,
> 
> Moritz

  reply	other threads:[~2021-09-26  5:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-25 18:39 Maintenance of Linux FPGA Moritz Fischer
2021-09-26  5:44 ` Xu Yilun [this message]
2021-09-28  4:22   ` Moritz Fischer
2021-09-28  5:51   ` Wu, Hao
2021-09-26  9:32 ` Greg KH

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=20210926054449.GD806603@yilunxu-OptiPlex-7050 \
    --to=yilun.xu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=mdf@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).