qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [GSoC] Wanted: small warmup tasks


From: Peter Crosthwaite
Subject: Re: [Qemu-devel] [GSoC] Wanted: small warmup tasks
Date: Fri, 25 Apr 2014 19:22:52 +1000

On Fri, Apr 25, 2014 at 5:55 PM, Marc Marí <address@hidden> wrote:
> I'm now looking at the conditional fprintf's. I'll need a bit of help later
> in sending the patches :D.
>

CC me in on the results.

Regards,
Peter

> Marc
>
>
> 2014-04-25 9:24 GMT+02:00 Jan Kiszka <address@hidden>:
>
>> On 2014-04-24 08:19, Jan Kiszka wrote:
>> > On 2014-04-23 11:25, Stefan Hajnoczi wrote:
>> >> Dear QEMU, Libvirt, and KVM communities,
>> >> We are participating in Google Summer of Code 2014
>> >> (http://google-melange.com/) and Outreach Program for Women
>> >> (http://opw.gnome.org/).  Both programs fund candidates to work on our
>> >> open source projects for 12 weeks this summer.
>> >
>> > To follow up on this: I'm currently looking for optional tiny "warmup"
>> > tasks for our QEMU students during the bonding period (till May 18). If
>> > you have any trivial issues or extensions in mind that someone could
>> > address within a few days or even hours, that would be perfect. It could
>> > even be something like "reformat the printing of these messages" or so.
>> >
>> > We used this mechanism last year with the KVM student quite
>> > successfully. The idea is to give the student very early a chance to get
>> > in contact with the community and with the patch submission & review
>> > procedure. So the focus is more on dealing with patches than on solving
>> > a technical problem in QEMU. If all works fine, this should encourage
>> > her/him to work with the community right from the beginning, ask
>> > question, post things early etc.
>>
>> Thanks for all these suggestion so far! I personally wasn't able to look
>> into them in details yet.
>>
>> A wish to the mentors and students: if someone picks up a task, please
>> drop a note here so that we can avoid duplicate work!
>>
>> Jan
>>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]