[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [qemu-web RFC PATCH] Add Sponsors page
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [qemu-web RFC PATCH] Add Sponsors page |
Date: |
Tue, 14 Sep 2021 08:16:32 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 |
On 9/14/21 7:41 AM, Thomas Huth wrote:
> On 13/09/2021 20.25, Philippe Mathieu-Daudé wrote:
>> Add a page listing QEMU sponsors and displaying their logos.
>>
>> Logo sources:
>> - https://www.rackspace.com/es/newsroom/media-kit
>> - https://developer.arm.com/solutions/infrastructure/works-on-arm
>> - https://gitlab.com/fosshost/assets/logo
>> - https://www.linkedin.com/company/cip-united
>>
>> Resolves: https://gitlab.com/qemu-project/qemu-web/-/issues/2
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> There are probably more, but I'm not aware of them.
>>
>> Maybe we should list past sponsors, precising a year range?
>
> I think we might have a hard time to compile a complete list, so I'd
> rather not start that job.
>
>> ---
>> _includes/nav.html | 1 +
>> sponsors.md | 22 ++++++++++++++++++++++
>> sponsors/cipunited.jpg | Bin 0 -> 10607 bytes
>> sponsors/fosshost.png | Bin 0 -> 18251 bytes
>> sponsors/rackspace.png | Bin 0 -> 7363 bytes
>> sponsors/worksonarm.png | Bin 0 -> 9965 bytes
>> 6 files changed, 23 insertions(+)
>> create mode 100644 sponsors.md
>> create mode 100644 sponsors/cipunited.jpg
>> create mode 100644 sponsors/fosshost.png
>> create mode 100644 sponsors/rackspace.png
>> create mode 100644 sponsors/worksonarm.png
>>
>> diff --git a/_includes/nav.html b/_includes/nav.html
>> index 73b39b3..49ad4cd 100644
>> --- a/_includes/nav.html
>> +++ b/_includes/nav.html
>> @@ -8,6 +8,7 @@
>> </li><li {% if current[1] == 'contribute'
>> %}class='current'{% endif %}><a href="{{ relative_root
>> }}/contribute">Contribute</a>
>> </li><li {% if current[1] == 'documentation'
>> %}class='current'{% endif %}><a href="{{ relative_root
>> }}/documentation">Docs</a>
>> </li><li><a href="https://wiki.qemu.org">Wiki</a>
>> + </li><li {% if current[1] == 'sponsors'
>> %}class='current'{% endif %}><a href="{{ relative_root
>> }}/sponsors">Sponsors</a>
>
> Not sure whether we need that link on every page (i.e. in the navigation
> menu)? Maybe it's enough to put the link somewhere on the home page?
Daniel recently changed that, so Cc'ing him in case he has a preference.
>> </li><li {% if current[1] == 'blog' %}class='current'{%
>> endif %}><a href="{{ relative_root }}/blog">Blog</a></li>
>> </ul>
>> </nav>
>> diff --git a/sponsors.md b/sponsors.md
>> new file mode 100644
>> index 0000000..da1bf19
>> --- /dev/null
>> +++ b/sponsors.md
>> @@ -0,0 +1,22 @@
>> +---
>> +title: QEMU sponsors
>> +permalink: /sponsors/
>> +---
>> +
>> +QEMU has sponsors!
>> +
>> +The website is hosted by [Rackspace
>> Technology](https://www.rackspace.com/).
>> +
>> +For continuous integration and testing, hardware is provided by:
>> +- Arm and Equinix Metal via the [Works on Arm
>> program](https://www.worksonarm.com/)
>> +- [Fosshost](https://fosshost.org/)
>> +- [CIP United](https://www.cipunited.com/)
>> +
>> +
>> +![Rackspace Technology](rackspace.png)
>> +
>> +![Works on Arm](worksonarm.png)
>> +
>> +![Fosshost](fosshost.png)
>> +
>> +![CIP United](cipunited.jpg)
>
> Some remarks:
>
> 1) Could you please use the original URLs as source for the pictures
> instead of copying them over into our website? Some folks don't like it
> when their images are copied...
OK but then it might bitrot.
> 2) Could we have a short description about what the CI hardware is used
> for? I can figure out that worksonarm likely provides the hardware for
> the aarch64 gitlab runner, but what are the others good for?
OK.
> 3) What about the s390x gitlab runner?
I don't have that information, who can I contact/ask for this?
Should I split this patch as a series with one sponsor per patch
and better document each patch?
> 4) Shouldn't we mention gitlab.com here, too? They did not actively
> offer hardware to us, but we're using their free gitlab infrastructure a
> lot, so I think we should provide a link to them here, too.
OK but then also cirrus-ci.
BTW is the mailing list somehow sponsored?
Thanks,
Phil.