From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Markey" <admin@fosshost.org>,
qemu-devel@nongnu.org, "Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: Re: [qemu-web PATCH v2] Add Sponsors page
Date: Thu, 18 Nov 2021 15:07:57 +0100 [thread overview]
Message-ID: <edbc5448-b60c-3132-b554-e9811897b7b8@redhat.com> (raw)
In-Reply-To: <YZZcRjJLSBJfALLQ@redhat.com>
On 11/18/21 14:59, Daniel P. Berrangé wrote:
> On Thu, Nov 18, 2021 at 01:54:38PM +0100, Thomas Huth wrote:
>> On 18/11/2021 13.29, Philippe Mathieu-Daudé wrote:
>>> Add a page listing QEMU sponsors.
>>>
>>> For now, only mention Fosshost which requested to be listed:
>>> https://lists.gnu.org/archive/html/qemu-devel/2021-06/msg05381.html
>> ...
>>> +QEMU has sponsors!
>>> +
>>> +For continuous integration and testing, hardware is provided by:
>>> +- [Fosshost](https://fosshost.org/)
>>
>> Are we finally using the server now? ... the last time I asked, it was just
>> idle and we talked about returning it?
>
> IMHO, whether we're currently using it or not is tangential.
>
> The sponsor has granted / reserved resources for QEMU, which can have
> a direct cost for them, and/or take away from what the can grant other
> projects. As such we should be creditting them for giving us this grant,
> even if we've not got around to using it.
>
> If we do decide to give up any particular resources, it is a quick patch
> to update this page again.
>
> My only suggestion would be that we don't explicitly state /what/ we're
> using the resource for, just that we've been granted it
>
> IOW say something more like
>
> [Fosshost](https://fosshost.org/) has provided QEMU
> access to a dedicated physical compute host.
>
> [Microsoft](https://microsoft.com) has provided QEMU
> with credits for use on Azure Cloud.
This sounds good to me. I will respin using your suggested
scheme.
next prev parent reply other threads:[~2021-11-18 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 12:29 [qemu-web PATCH v2] Add Sponsors page Philippe Mathieu-Daudé
2021-11-18 12:54 ` Thomas Huth
2021-11-18 13:24 ` Philippe Mathieu-Daudé
2021-11-18 13:59 ` Daniel P. Berrangé
2021-11-18 14:07 ` Philippe Mathieu-Daudé [this message]
2021-11-18 13:41 ` Paolo Bonzini
2021-11-18 13:56 ` Philippe Mathieu-Daudé
2021-11-18 14:10 ` Philippe Mathieu-Daudé
2021-11-23 6:02 ` Alistair Francis
2021-11-23 12:58 ` Stefan Hajnoczi
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=edbc5448-b60c-3132-b554-e9811897b7b8@redhat.com \
--to=philmd@redhat.com \
--cc=admin@fosshost.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).