From: Stefano Garzarella <sgarzare@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>,
"Rust-VMM Mailing List" <rust-vmm@lists.opendev.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"John Snow" <jsnow@redhat.com>, "Sergio Lopez" <slp@redhat.com>,
"Florescu, Andreea" <fandree@amazon.com>,
"Alex Agache" <aagch@amazon.com>,
"Damien Le Moal" <Damien.LeMoal@wdc.com>,
"Hannes Reinecke" <hare@suse.de>,
"Dmitry Fomichev" <Dmitry.Fomichev@wdc.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>
Subject: Re: Call for GSoC and Outreachy project ideas for summer 2022
Date: Mon, 14 Feb 2022 12:48:25 +0100 [thread overview]
Message-ID: <20220214114825.pi44m7mqyqvvtt52@step1g3> (raw)
In-Reply-To: <CACGkMEvtENvpubmZY3UKptD-T=c9+JJV1kRm-ZPhP08xOJv2fQ@mail.gmail.com>
On Mon, Feb 14, 2022 at 03:11:20PM +0800, Jason Wang wrote:
>On Fri, Jan 28, 2022 at 11:47 PM Stefan Hajnoczi <stefanha@gmail.com> wrote:
>>
>> Dear QEMU, KVM, and rust-vmm communities,
>> QEMU will apply for Google Summer of Code 2022
>> (https://summerofcode.withgoogle.com/) and has been accepted into
>> Outreachy May-August 2022 (https://www.outreachy.org/). You can now
>> submit internship project ideas for QEMU, KVM, and rust-vmm!
>>
>> If you have experience contributing to QEMU, KVM, or rust-vmm you can
>> be a mentor. It's a great way to give back and you get to work with
>> people who are just starting out in open source.
>>
>> Please reply to this email by February 21st with your project ideas.
>>
>> Good project ideas are suitable for remote work by a competent
>> programmer who is not yet familiar with the codebase. In
>> addition, they are:
>> - Well-defined - the scope is clear
>> - Self-contained - there are few dependencies
>> - Uncontroversial - they are acceptable to the community
>> - Incremental - they produce deliverables along the way
>>
>> Feel free to post ideas even if you are unable to mentor the project.
>> It doesn't hurt to share the idea!
>
>Implementing the VIRTIO_F_IN_ORDER feature for both Qemu and kernel
>(vhost/virtio drivers) would be an interesting idea.
>
>It satisfies all the points above since it's supported by virtio spec.
Yep, I agree!
>
>(Unfortunately, I won't have time in the mentoring)
I can offer my time to mentor this idea.
Thanks,
Stefano
next prev parent reply other threads:[~2022-02-14 11:50 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 15:47 Call for GSoC and Outreachy project ideas for summer 2022 Stefan Hajnoczi
2022-02-09 14:49 ` Alexander Graf
2022-02-14 13:58 ` Stefan Hajnoczi
2022-03-16 13:16 ` Stefan Hajnoczi
2022-03-16 13:35 ` Alexander Graf
2022-03-29 20:29 ` Stefan Hajnoczi
2022-02-14 7:11 ` Jason Wang
2022-02-14 11:48 ` Stefano Garzarella [this message]
2022-02-15 7:48 ` Jason Wang
2022-02-14 14:01 ` Stefan Hajnoczi
2022-02-15 7:49 ` Jason Wang
2022-02-17 14:12 ` Stefano Garzarella
2022-02-17 16:27 ` Stefan Hajnoczi
2022-02-17 17:49 ` Paolo Bonzini
2022-02-19 9:36 ` Stefan Hajnoczi
2022-02-14 13:16 ` Alex Bennée
2022-02-14 14:10 ` Stefan Hajnoczi
2022-02-17 7:08 ` Alice Frosi
2022-02-17 16:26 ` Stefan Hajnoczi
2022-02-17 17:52 ` Paolo Bonzini
2022-02-18 11:39 ` Michal Prívozník
2022-02-18 16:03 ` Paolo Bonzini
2022-02-19 13:46 ` Stefan Hajnoczi
2022-02-21 9:36 ` Michal Prívozník
2022-02-21 11:27 ` Paolo Bonzini
2022-02-21 15:23 ` Michal Prívozník
2022-02-19 13:48 ` Stefan Hajnoczi
2022-02-18 21:03 ` Alexander Bulekov
2022-02-21 9:34 ` Stefan Hajnoczi
2022-02-21 6:14 ` Klaus Jensen
2022-02-21 9:51 ` Stefan Hajnoczi
2022-02-21 12:00 ` Klaus Jensen
2022-02-22 9:48 ` Stefan Hajnoczi
2022-02-22 15:03 ` Keith Busch
2022-02-25 12:39 ` Stefan Hajnoczi
2022-02-23 8:47 ` Andreea Florescu
2022-02-25 12:55 ` 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=20220214114825.pi44m7mqyqvvtt52@step1g3 \
--to=sgarzare@redhat.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=aagch@amazon.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=fandree@amazon.com \
--cc=hare@suse.de \
--cc=hreitz@redhat.com \
--cc=jasowang@redhat.com \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rust-vmm@lists.opendev.org \
--cc=slp@redhat.com \
--cc=stefanha@gmail.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).