From: Paolo Bonzini <pbonzini@redhat.com> To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>, "libvir-list@redhat.com" <libvir-list@redhat.com> Cc: Mark Kanda <mark.kanda@oracle.com> Subject: Re: Call for GSoC and Outreachy project ideas for summer 2022 Date: Thu, 17 Feb 2022 18:52:25 +0100 [thread overview] Message-ID: <f7dc638d-0de1-baa8-d883-fd8435ae13f2@redhat.com> (raw) In-Reply-To: <CAJSP0QX7O_auRgTKFjHkBbkBK=B3Z-59S6ZZi10tzFTv1_1hkQ@mail.gmail.com> On 1/28/22 16:47, Stefan Hajnoczi 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. I would like to co-mentor one or more projects about adding more statistics to Mark Kanda's newly-born introspectable statistics subsystem in QEMU (https://patchew.org/QEMU/20220215150433.2310711-1-mark.kanda@oracle.com/), for example integrating "info blockstats"; and/or, to add matching functionality to libvirt. However, I will only be available for co-mentoring unfortunately. Paolo > 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! > > I will review project ideas and keep you up-to-date on QEMU's > acceptance into GSoC. > > Internship program details: > - Paid, remote work open source internships > - GSoC projects are 175 or 350 hours, Outreachy projects are 30 > hrs/week for 12 weeks > - Mentored by volunteers from QEMU, KVM, and rust-vmm > - Mentors typically spend at least 5 hours per week during the coding period > > Changes since last year: GSoC now has 175 or 350 hour project sizes > instead of 12 week full-time projects. GSoC will accept applicants who > are not students, before it was limited to students. > > For more background on QEMU internships, check out this video: > https://www.youtube.com/watch?v=xNVCX7YMUL8 > > Please let me know if you have any questions! > > Stefan >
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com> To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>, "libvir-list@redhat.com" <libvir-list@redhat.com> Subject: Re: Call for GSoC and Outreachy project ideas for summer 2022 Date: Thu, 17 Feb 2022 18:52:25 +0100 [thread overview] Message-ID: <f7dc638d-0de1-baa8-d883-fd8435ae13f2@redhat.com> (raw) In-Reply-To: <CAJSP0QX7O_auRgTKFjHkBbkBK=B3Z-59S6ZZi10tzFTv1_1hkQ@mail.gmail.com> On 1/28/22 16:47, Stefan Hajnoczi 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. I would like to co-mentor one or more projects about adding more statistics to Mark Kanda's newly-born introspectable statistics subsystem in QEMU (https://patchew.org/QEMU/20220215150433.2310711-1-mark.kanda@oracle.com/), for example integrating "info blockstats"; and/or, to add matching functionality to libvirt. However, I will only be available for co-mentoring unfortunately. Paolo > 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! > > I will review project ideas and keep you up-to-date on QEMU's > acceptance into GSoC. > > Internship program details: > - Paid, remote work open source internships > - GSoC projects are 175 or 350 hours, Outreachy projects are 30 > hrs/week for 12 weeks > - Mentored by volunteers from QEMU, KVM, and rust-vmm > - Mentors typically spend at least 5 hours per week during the coding period > > Changes since last year: GSoC now has 175 or 350 hour project sizes > instead of 12 week full-time projects. GSoC will accept applicants who > are not students, before it was limited to students. > > For more background on QEMU internships, check out this video: > https://www.youtube.com/watch?v=xNVCX7YMUL8 > > Please let me know if you have any questions! > > Stefan >
next prev parent reply other threads:[~2022-02-17 17:52 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 [this message] 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 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=f7dc638d-0de1-baa8-d883-fd8435ae13f2@redhat.com \ --to=pbonzini@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=libvir-list@redhat.com \ --cc=mark.kanda@oracle.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: linkBe 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.