From: Luiz Capitulino <lcapitulino@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
libvir-list@redhat.com, Anthony Liguori <anthony@codemonkey.ws>,
joro@8bytes.org, avi@redhat.com, stefanha@gmail.com,
veillard@redhat.com
Subject: Re: Google Summer of Code 2011
Date: Mon, 31 Jan 2011 09:39:47 -0200 [thread overview]
Message-ID: <20110131093947.7c66bdea@doriath> (raw)
In-Reply-To: <16F905E1-1E57-4FA4-9661-F80022B0C82B@suse.de>
On Sun, 30 Jan 2011 16:06:20 +0100
Alexander Graf <agraf@suse.de> wrote:
>
> On 28.01.2011, at 21:10, Luiz Capitulino wrote:
>
> > Hi there,
> >
> > GSoC 2011 has been announced[1]. As we were pretty successful last year,
> > I think we should participate again. I've already created a wiki page:
> >
> > http://wiki.qemu.org/Google_Summer_of_Code_2011
> >
> > We should now populate it with projects and people willing to be mentors
> > should say so (or just add a project)[2].
> >
> > Also, I'd like to do something different this year, I'd like to invite
> > libvirt people to join. There are two ways of doing this:
> >
> > 1. They join in the program as a regular mentoring organization, or
> >
> > 2. They join with QEMU
> >
> > The second option means that libvirt can suggest and run its own projects
> > (preferably with QEMU relevance), but from a GSoC perspective, the project
> > will be part of the QEMU org.
>
> Keep in mind that every full org gets a free trip to the west coast for 2 people ;). So splitting up means we could almost do a mini-summit at the google campus on google's expenses ;).
Actually, they have a limited budget and if you live too far (say, in Brazil),
the trip might not be 100% free :)
> Please coordinate that with Carol. Apparently traction for GSOC is declining (according to last year's summit). So there might be plenty of available slots this year. So I'd say sign up separately for now and if you don't get accepted, just join forces with us!
Yes, that's a good plan and I fully agree that we get more benefits if we
apply separately. It's a call to libvirt's people.
WARNING: multiple messages have this Message-ID (diff)
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm@vger.kernel.org, libvir-list@redhat.com, stefanha@gmail.com,
joro@8bytes.org, qemu-devel@nongnu.org, avi@redhat.com
Subject: [Qemu-devel] Re: Google Summer of Code 2011
Date: Mon, 31 Jan 2011 09:39:47 -0200 [thread overview]
Message-ID: <20110131093947.7c66bdea@doriath> (raw)
In-Reply-To: <16F905E1-1E57-4FA4-9661-F80022B0C82B@suse.de>
On Sun, 30 Jan 2011 16:06:20 +0100
Alexander Graf <agraf@suse.de> wrote:
>
> On 28.01.2011, at 21:10, Luiz Capitulino wrote:
>
> > Hi there,
> >
> > GSoC 2011 has been announced[1]. As we were pretty successful last year,
> > I think we should participate again. I've already created a wiki page:
> >
> > http://wiki.qemu.org/Google_Summer_of_Code_2011
> >
> > We should now populate it with projects and people willing to be mentors
> > should say so (or just add a project)[2].
> >
> > Also, I'd like to do something different this year, I'd like to invite
> > libvirt people to join. There are two ways of doing this:
> >
> > 1. They join in the program as a regular mentoring organization, or
> >
> > 2. They join with QEMU
> >
> > The second option means that libvirt can suggest and run its own projects
> > (preferably with QEMU relevance), but from a GSoC perspective, the project
> > will be part of the QEMU org.
>
> Keep in mind that every full org gets a free trip to the west coast for 2 people ;). So splitting up means we could almost do a mini-summit at the google campus on google's expenses ;).
Actually, they have a limited budget and if you live too far (say, in Brazil),
the trip might not be 100% free :)
> Please coordinate that with Carol. Apparently traction for GSOC is declining (according to last year's summit). So there might be plenty of available slots this year. So I'd say sign up separately for now and if you don't get accepted, just join forces with us!
Yes, that's a good plan and I fully agree that we get more benefits if we
apply separately. It's a call to libvirt's people.
next prev parent reply other threads:[~2011-01-31 11:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 20:10 Google Summer of Code 2011 Luiz Capitulino
2011-01-28 20:10 ` [Qemu-devel] " Luiz Capitulino
2011-01-30 15:06 ` Alexander Graf
2011-01-30 15:06 ` [Qemu-devel] " Alexander Graf
2011-01-31 11:39 ` Luiz Capitulino [this message]
2011-01-31 11:39 ` Luiz Capitulino
-- strict thread matches above, loose matches on Subject: below --
2011-03-03 18:08 Shawn Pearce
2011-03-03 18:59 ` Jeff King
2011-03-03 19:04 ` Shawn Pearce
2011-03-03 20:33 ` Jeff King
2011-03-03 21:25 ` Jakub Narebski
2011-03-09 16:38 ` Jeff King
2011-03-09 16:39 ` Jeff King
2011-03-09 16:47 ` Shawn Pearce
2011-03-09 17:49 ` Jeff King
2011-03-09 17:52 ` Shawn Pearce
2011-03-03 21:04 ` Ramkumar Ramachandra
2011-03-03 22:08 ` Jonathan Nieder
2011-03-07 12:15 ` Sverre Rabbelier
2011-03-08 12:33 ` Ramkumar Ramachandra
2011-03-08 12:49 ` Sverre Rabbelier
2011-03-03 22:38 ` Jens Lehmann
2011-03-05 4:05 ` Christian Couder
2011-03-06 19:24 ` Sam Vilain
2011-03-07 19:40 ` Heiko Voigt
2011-03-07 20:50 ` Fredrik Gustafsson
2011-03-09 15:18 ` Thomas Rast
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=20110131093947.7c66bdea@doriath \
--to=lcapitulino@redhat.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=veillard@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 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.