From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Andrew Randrianasulu <randrianasulu@gmail.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-discuss@nongnu.org,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: dropping 32-bit host support
Date: Thu, 16 Mar 2023 15:39:13 +0000 [thread overview]
Message-ID: <ZBM4IfhnjvJ5iPdh@redhat.com> (raw)
In-Reply-To: <CA+rFky6hnaCxF10ST=qsLsBjH6=M__kQPA=yoZhdCoB8sH96ug@mail.gmail.com>
On Thu, Mar 16, 2023 at 04:01:06PM +0300, Andrew Randrianasulu wrote:
> Well, this language about "market" and "investment" not just figures of
> the speech, sadly? Because paid developers work on areas they paid to
> develop, by boss with big bucks.
This is FUD.
Many QEMU maintainers are employeed, but that does not mean that their
boss gets to dictate what the QEMU community does. The company has its
priorities but this cannot be forced onto the community. Changes have
to be made through tradeoffs and consensus building across all active
maintainers.
To put it another way, responsible open source maintainers/contributors
wear two hats.
With their corporate hat on they have tasks to work on that are directly
important to their employer in the short term. They can make a case for
why these contributions are beneficial, but there's never a guarantee
the community will agree / accept it.
With their community hat on they look at, and work on, what is important
for the health of the community in general. This can sometimes be contrary
to what the employer would otherwise like to see. Wise companies accept
this tradeoff, because the long term health of the community is ultimately
important to them too.
QEMU is fortunate to have many responsible maintainers who balance the
demands of their employer vs the community on an ongoing basis.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-16 15:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+rFky6A9Q_5sJ4WDO-Z2HBT59qiNgr8A-xk+O7-gnAMZmHt2A@mail.gmail.com>
2023-03-16 7:05 ` dropping 32-bit host support Philippe Mathieu-Daudé
2023-03-16 7:17 ` Andrew Randrianasulu
2023-03-16 7:36 ` Philippe Mathieu-Daudé
2023-03-16 7:44 ` Andrew Randrianasulu
2023-03-16 8:31 ` Thomas Huth
2023-03-16 9:17 ` Andrew Randrianasulu
2023-03-16 10:22 ` Andrew Randrianasulu
2023-03-16 10:56 ` Philippe Mathieu-Daudé
2023-03-16 11:04 ` Andrew Randrianasulu
2023-03-16 11:15 ` Thomas Huth
2023-03-16 11:02 ` Thomas Huth
2023-03-16 11:11 ` Andrew Randrianasulu
2023-03-16 12:35 ` Daniel P. Berrangé
2023-03-16 13:01 ` Andrew Randrianasulu
2023-03-16 13:32 ` Thomas Huth
2023-03-16 15:21 ` Warner Losh
2023-03-16 15:29 ` Andrew Randrianasulu
2023-03-16 15:27 ` Andrew Randrianasulu
2023-03-16 15:39 ` Daniel P. Berrangé [this message]
2023-03-17 8:03 ` Andrew Randrianasulu
2023-03-16 10:00 ` Markus Armbruster
2023-03-16 10:05 ` Andrew Randrianasulu
[not found] ` <3DD8295F-4BE0-4262-8C68-4A85A56D63C7@livius.net>
2023-03-16 7:29 ` Philippe Mathieu-Daudé
2023-03-16 7:57 ` Liviu Ionescu
2023-03-16 8:07 ` Liviu Ionescu
2023-03-16 8:36 ` Thomas Huth
2023-03-16 8:42 ` Liviu Ionescu
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=ZBM4IfhnjvJ5iPdh@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=randrianasulu@gmail.com \
--cc=thuth@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).