qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Gurchetan Singh <gurchetansingh@chromium.org>
Cc: qemu-devel <qemu-devel@nongnu.org>, Sergio Lopez <slp@redhat.com>
Subject: Re: Call for GSoC/Outreachy internship project ideas
Date: Wed, 31 Jan 2024 19:11:27 -0500	[thread overview]
Message-ID: <CAJSP0QXMarmQ5GiR8944YJ0-1rPtae5yekhvt1xNXwCv6O60Lg@mail.gmail.com> (raw)
In-Reply-To: <CAAfnVBnfkyCkY5Vsj7FaUWQxGq3YD4q_AE=BsYwnpLki75MxhQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]

On Wed, Jan 31, 2024, 18:55 Gurchetan Singh <gurchetansingh@chromium.org>
wrote:

>
>
> On Wed, Jan 24, 2024 at 4:51 AM Stefan Hajnoczi <stefanha@gmail.com>
> wrote:
>
>> On Tue, 23 Jan 2024 at 22:47, Gurchetan Singh
>> <gurchetansingh@chromium.org> wrote:
>> > Title:
>> > - Improve display integration for upstream virtualized graphics
>> >
>> > Summary:
>> > - The Rutabaga Virtual Graphics interface's UI integration upstream is
>> very simple, but in deployment it will be complex.  This project aims to
>> bridge the gap between downstream consumers and upstream QEMU.
>> >
>> > Looking for someone interested in Rust + system level graphics to help
>> realize the next steps.
>>
>> Hi Gurchetan,
>> It's unclear what this project idea entails.
>>
>> Based on your email my guess is you're looking for someone to help
>> upstream code into QEMU, but I'm not sure. Last year there was a
>> project to upstream bsd-user emulation code into QEMU and I think that
>> type of project can work well.
>>
>> Or maybe you're looking for someone to write a QEMU UI code that uses
>> rutabaga_gfx.
>>
>> Can you describe the next steps in more detail?
>>
>> The project description should contain enough information for someone
>> who knows how to program but has no domain knowledge in Rutabaga,
>> virtio-gpu, or QEMU.
>>
>> > Note: developers should be willing to sign Google CLA, here:
>> >
>> > https://cla.developers.google.com/about/google-individual
>> >
>> > But everything will be FOSS.
>>
>> Which codebase will this project touch? If a CLA is required then it
>> sounds like it's not qemu.git?
>>
>
> Good points, I think we need to think about this a bit more ....  I hereby
> withdraw the idea!
>

The project doesn't necessarily need to be in qemu.git. Just something that
is related to QEMU. Past projects have included rust-vmm crates, libnbd,
libblkio, etc.

If the code is used in conjunction with a QEMU guest, then it is probably
in scope.

We can discuss further if you like.

Stefan


>
>>
>> > Links
>> > - https://crosvm.dev/book/appendix/rutabaga_gfx.html
>> > -
>> https://patchew.org/QEMU/20230421011223.718-1-gurchetansingh@chromium.org/
>> >
>> > Skills
>> >  - Level: Advanced
>> >  - Rust, Vulkan, virtualization, cross-platform graphics
>>
>

[-- Attachment #2: Type: text/html, Size: 4086 bytes --]

  reply	other threads:[~2024-02-01  0:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15 16:32 Call for GSoC/Outreachy internship project ideas Stefan Hajnoczi
     [not found] ` <CAAfnVBn0+627rLGXeLdsvUge0_VegcbTVuQf8rQwtjuJ3hcJnA@mail.gmail.com>
2024-01-24 12:51   ` Stefan Hajnoczi
2024-01-31 23:55     ` Gurchetan Singh
2024-02-01  0:11       ` Stefan Hajnoczi [this message]
2024-01-29 18:53 ` Eugenio Perez Martin
2024-01-29 19:39   ` Stefan Hajnoczi
2024-01-30 12:08     ` Eugenio Perez Martin
2024-01-30 19:34       ` Stefan Hajnoczi
2024-01-31 10:37         ` Eugenio Perez Martin
2024-01-30 19:16 ` Alexander Graf
2024-01-30 20:15   ` Stefan Hajnoczi
2024-01-30 19:40 ` Palmer Dabbelt
2024-01-30 20:28   ` Stefan Hajnoczi
2024-01-31  0:29     ` Palmer Dabbelt
2024-01-31  1:26       ` Alistair Francis
2024-01-31  1:50         ` Palmer Dabbelt
2024-02-01 17:39       ` Alex Bennée
2024-02-01 18:01         ` Palmer Dabbelt
2024-02-01 18:57           ` Alex Bennée
2024-02-01 19:06             ` Palmer Dabbelt
2024-01-31 14:39   ` Stefan Hajnoczi
2024-01-31 15:59     ` Palmer Dabbelt
2024-01-31 18:20       ` 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=CAJSP0QXMarmQ5GiR8944YJ0-1rPtae5yekhvt1xNXwCv6O60Lg@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=gurchetansingh@chromium.org \
    --cc=qemu-devel@nongnu.org \
    --cc=slp@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).