From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michal Prívozník" <mprivozn@redhat.com>,
"Stefan Hajnoczi" <stefanha@gmail.com>
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: Call for GSoC and Outreachy project ideas for summer 2022
Date: Mon, 21 Feb 2022 12:27:24 +0100 [thread overview]
Message-ID: <1b38c5ea-d908-fe36-05e1-022d402cedbc@redhat.com> (raw)
In-Reply-To: <d2af5caf-5201-70aa-92cc-16790a8159d1@redhat.com>
On 2/21/22 10:36, Michal Prívozník wrote:
> Indeed. Libvirt's participating on its own since 2016, IIRC. Since we're
> still in org acceptance phase we have some time to decide this,
> actually. We can do the final decision after participating orgs are
> announced. My gut feeling says that it's going to be more work on QEMU
> side which would warrant it to be on the QEMU ideas page.
There are multiple projects that can be done on this topic, some
QEMU-only, some Libvirt-only. For now I would announce the project on
the Libvirt side (and focus on those projects) since you are comentoring.
Paolo
next prev parent reply other threads:[~2022-02-21 11:27 UTC|newest]
Thread overview: 70+ 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-01-28 15:47 ` Stefan Hajnoczi
2022-02-09 14:49 ` Alexander Graf
2022-02-14 13:58 ` Stefan Hajnoczi
2022-02-14 13:58 ` Stefan Hajnoczi
2022-03-16 13:16 ` Stefan Hajnoczi
2022-03-16 13:16 ` Stefan Hajnoczi
2022-03-16 13:35 ` Alexander Graf
2022-03-29 20:29 ` Stefan Hajnoczi
2022-03-29 20:29 ` Stefan Hajnoczi
2022-02-14 7:11 ` Jason Wang
2022-02-14 7:11 ` Jason Wang
2022-02-14 11:48 ` Stefano Garzarella
2022-02-14 11:48 ` Stefano Garzarella
2022-02-15 7:48 ` Jason Wang
2022-02-15 7:48 ` Jason Wang
2022-02-14 14:01 ` Stefan Hajnoczi
2022-02-14 14:01 ` Stefan Hajnoczi
2022-02-15 7:49 ` Jason Wang
2022-02-15 7:49 ` Jason Wang
2022-02-17 14:12 ` Stefano Garzarella
2022-02-17 14:12 ` Stefano Garzarella
2022-02-17 16:27 ` Stefan Hajnoczi
2022-02-17 16:27 ` Stefan Hajnoczi
2022-02-17 17:49 ` Paolo Bonzini
2022-02-17 17:49 ` Paolo Bonzini
2022-02-19 9:36 ` Stefan Hajnoczi
2022-02-19 9:36 ` Stefan Hajnoczi
2022-02-14 13:16 ` Alex Bennée
2022-02-14 13:16 ` Alex Bennée
2022-02-14 14:10 ` Stefan Hajnoczi
2022-02-14 14:10 ` Stefan Hajnoczi
2022-02-17 7:08 ` Alice Frosi
2022-02-17 7:08 ` Alice Frosi
2022-02-17 16:26 ` Stefan Hajnoczi
2022-02-17 16:26 ` Stefan Hajnoczi
2022-02-17 17:52 ` Paolo Bonzini
2022-02-17 17:52 ` Paolo Bonzini
2022-02-18 11:39 ` Michal Prívozník
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-19 13:46 ` Stefan Hajnoczi
2022-02-21 9:36 ` Michal Prívozník
2022-02-21 9:36 ` Michal Prívozník
2022-02-21 11:27 ` Paolo Bonzini [this message]
2022-02-21 15:23 ` Michal Prívozník
2022-02-19 13:48 ` Stefan Hajnoczi
2022-02-19 13:48 ` Stefan Hajnoczi
2022-02-17 18:23 ` Thomas Huth
2022-02-19 14:12 ` Stefan Hajnoczi
2022-02-18 21:03 ` Alexander Bulekov
2022-02-18 21:03 ` Alexander Bulekov
2022-02-21 9:34 ` Stefan Hajnoczi
2022-02-21 9:34 ` Stefan Hajnoczi
2022-02-21 6:14 ` Klaus Jensen
2022-02-21 6:14 ` Klaus Jensen
2022-02-21 9:51 ` Stefan Hajnoczi
2022-02-21 9:51 ` Stefan Hajnoczi
2022-02-21 12:00 ` Klaus Jensen
2022-02-21 12:00 ` Klaus Jensen
2022-02-22 9:48 ` Stefan Hajnoczi
2022-02-22 9:48 ` Stefan Hajnoczi
2022-02-22 15:03 ` Keith Busch
2022-02-22 15:03 ` Keith Busch
2022-02-25 12:39 ` Stefan Hajnoczi
2022-02-25 12:39 ` Stefan Hajnoczi
2022-02-23 8:47 ` Andreea Florescu
2022-02-25 12:55 ` Stefan Hajnoczi
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=1b38c5ea-d908-fe36-05e1-022d402cedbc@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.