linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wu, Hao" <hao.wu@intel.com>
To: "Xu, Yilun" <yilun.xu@intel.com>, Moritz Fischer <mdf@kernel.org>
Cc: "linux-fpga@vger.kernel.org" <linux-fpga@vger.kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: RE: Maintenance of Linux FPGA
Date: Tue, 28 Sep 2021 05:51:14 +0000	[thread overview]
Message-ID: <DM6PR11MB3819F88491118D3F6E22D35C85A89@DM6PR11MB3819.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210926054449.GD806603@yilunxu-OptiPlex-7050>

> -----Original Message-----
> From: Xu, Yilun <yilun.xu@intel.com>
> Sent: Sunday, September 26, 2021 1:45 PM
> To: Moritz Fischer <mdf@kernel.org>
> Cc: linux-fpga@vger.kernel.org; gregkh@linuxfoundation.org; Wu, Hao
> <hao.wu@intel.com>
> Subject: Re: Maintenance of Linux FPGA
> 
> 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.

Hi Moritz,

Me too, it's really a great pleasure. Thanks a lot for giving me this
opportunity, I hope I can do more contributions.

Thanks
Hao

> 
> 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

  parent reply	other threads:[~2021-09-28  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
2021-09-28  4:22   ` Moritz Fischer
2021-09-28  5:51   ` Wu, Hao [this message]
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=DM6PR11MB3819F88491118D3F6E22D35C85A89@DM6PR11MB3819.namprd11.prod.outlook.com \
    --to=hao.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=yilun.xu@intel.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).