From: Greg KH <gregkh@linuxfoundation.org>
To: Moritz Fischer <mdf@kernel.org>
Cc: linux-fpga@vger.kernel.org, hao.wu@intel.com, yilun.xu@intel.com
Subject: Re: Maintenance of Linux FPGA
Date: Sun, 26 Sep 2021 11:32:02 +0200 [thread overview]
Message-ID: <YVA+EvWpX4vNKqTf@kroah.com> (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.
>
> 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?
There's lots of different ways they work, depends on what works best for
you all.
Some take turns on a weekly basis to commit patches to the tree. Some
require multiple acks/reviews by the others before they are allowed to
merge to their tree. Some just do what they can and merge what they
want :)
So it's all up to you all as to what you all find works best. I'll
gladly take patches from whatever you all determine to do.
thanks,
greg k-h
prev parent reply other threads:[~2021-09-26 9:32 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
2021-09-26 9:32 ` Greg KH [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=YVA+EvWpX4vNKqTf@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hao.wu@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.