From: Connor Kuehl <ckuehl@redhat.com>
To: Federico Vaga <federico.vaga@cern.ch>, qemu-devel@nongnu.org
Subject: Re: Contributions: Adding New Devices
Date: Thu, 1 Jul 2021 12:48:03 -0700 [thread overview]
Message-ID: <a394439c-0e82-b915-2e49-70ceda3d7b02@redhat.com> (raw)
In-Reply-To: <20210630140102.ecuyxyeqnthvausb@cwe-513-vol689.cern.ch>
On 6/30/21 7:01 AM, Federico Vaga wrote:
> Hello,
>
> I can't find this information on the website, so here I am.
>
> I developed a QEMU device that virtualises a PCI card that we widely use at CERN.
> But this card is only used at CERN.
>
> Clearly, having CERN specific devices in QEMU does not help much the qemu
> community, hence I maintain an internal QEMU fork.
>
> But, I was wondering what is the QEMU policy about contributions that are known to be
> used only by a handful of people (one organization in this case)? Are they accepted?
Your first instinct is correct that it's unlikely that the community
will be able to maintain a device if it's really so niche as to only
be used at your organization.
However, if you do decide to try to upstream it, it could only help
your chances if you or some of your colleagues agreed to maintain it
for the QEMU community. This mainly involves adding an entry to the
MAINTAINERS file where, if accepted, the expectation is that you'll
be reachable within reason to review patches, make pull requests,
help discuss bugs in the subsystem, etc.
Sorry I don't have a concrete "yes" or "no" for you; but I'd recommend
giving it a shot if you have the time.
Connor
next prev parent reply other threads:[~2021-07-01 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 14:01 Contributions: Adding New Devices Federico Vaga
2021-07-01 19:48 ` Connor Kuehl [this message]
2021-07-01 22:07 ` Philippe Mathieu-Daudé
2021-07-02 12:46 ` Federico Vaga
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=a394439c-0e82-b915-2e49-70ceda3d7b02@redhat.com \
--to=ckuehl@redhat.com \
--cc=federico.vaga@cern.ch \
--cc=qemu-devel@nongnu.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).