All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Privoznik <mprivozn@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"libvir-list@redhat.com" <libvir-list@redhat.com>,
	kvm <kvm@vger.kernel.org>
Subject: Re: [libvirt] Call for mentors and project ideas for Google Summer of Code 2016
Date: Wed, 27 Jan 2016 12:06:22 +0100	[thread overview]
Message-ID: <56A8A4AE.7070801@redhat.com> (raw)
In-Reply-To: <20160127105612.GD7103@stefanha-x1.localdomain>

On 27.01.2016 11:56, Stefan Hajnoczi wrote:
> On Tue, Jan 26, 2016 at 11:13:16AM +0100, Michal Privoznik wrote:
>> On 25.01.2016 18:28, Stefan Hajnoczi wrote:
>>> The QEMU wiki page for Google Summer of Code 2016 is now available here:
>>>
>>> http://qemu-project.org/Google_Summer_of_Code_2016
>>>
>>> QEMU will apply for Google Summer of Code 2016 (https://g.co/gsoc/).
>>> If QEMU is accepted there will be funding for students to work on
>>> 12-week full-time open source projects remotely from May to August
>>> 2016.  QEMU provides a mentor for each student who gives advice and
>>> evaluates their progress.
>>>
>>> If you have a project idea, especially if you are a regular
>>> contributor to QEMU and are willing to mentor this summer, please go
>>> to this wiki page and fill out the project idea template:
>>>
>>> http://qemu-project.org/Google_Summer_of_Code_2016
>>>
>>> The project ideas list is part of the application so that QEMU can
>>> participate in GSoC.  It's useful to have your project ideas on the
>>> wiki by February 8th 2016.
>>>
>>> If you have any questions about project ideas or QEMU applying to
>>> GSoC, please reply to this thread.
>>
>> Hey Stefan,
>>
>> so as we spoke earlier in person, I think it's time for libvirt to try
>> and apply as a separate organization.
> 
> Great!
> 
>> I went ahead and created similar GSoC ideas page for libvirt:
>>
>> http://wiki.libvirt.org/page/Google_Summer_of_Code_2016
>>
>> My question is, is qemu willing to back libvirt in case we don't get
>> selected and if so, should we duplicate the idea list into qemu wiki too?
> 
> I'm worried that this would look like orgs trying to game the system.

You're right. Maybe we should not do it after all.

> 
> Are there project ideas that involve both QEMU and libvirt changes?  For
> those I think it's fair to have them in both org's lists.  Anything that
> is purely QEMU or libvirt shouldn't be duplicated.
> 

So far none. But I have adjusted both our wikis to note that.

Michal

WARNING: multiple messages have this Message-ID (diff)
From: Michal Privoznik <mprivozn@redhat.com>
To: 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: [Qemu-devel] [libvirt] Call for mentors and project ideas for Google Summer of Code 2016
Date: Wed, 27 Jan 2016 12:06:22 +0100	[thread overview]
Message-ID: <56A8A4AE.7070801@redhat.com> (raw)
In-Reply-To: <20160127105612.GD7103@stefanha-x1.localdomain>

On 27.01.2016 11:56, Stefan Hajnoczi wrote:
> On Tue, Jan 26, 2016 at 11:13:16AM +0100, Michal Privoznik wrote:
>> On 25.01.2016 18:28, Stefan Hajnoczi wrote:
>>> The QEMU wiki page for Google Summer of Code 2016 is now available here:
>>>
>>> http://qemu-project.org/Google_Summer_of_Code_2016
>>>
>>> QEMU will apply for Google Summer of Code 2016 (https://g.co/gsoc/).
>>> If QEMU is accepted there will be funding for students to work on
>>> 12-week full-time open source projects remotely from May to August
>>> 2016.  QEMU provides a mentor for each student who gives advice and
>>> evaluates their progress.
>>>
>>> If you have a project idea, especially if you are a regular
>>> contributor to QEMU and are willing to mentor this summer, please go
>>> to this wiki page and fill out the project idea template:
>>>
>>> http://qemu-project.org/Google_Summer_of_Code_2016
>>>
>>> The project ideas list is part of the application so that QEMU can
>>> participate in GSoC.  It's useful to have your project ideas on the
>>> wiki by February 8th 2016.
>>>
>>> If you have any questions about project ideas or QEMU applying to
>>> GSoC, please reply to this thread.
>>
>> Hey Stefan,
>>
>> so as we spoke earlier in person, I think it's time for libvirt to try
>> and apply as a separate organization.
> 
> Great!
> 
>> I went ahead and created similar GSoC ideas page for libvirt:
>>
>> http://wiki.libvirt.org/page/Google_Summer_of_Code_2016
>>
>> My question is, is qemu willing to back libvirt in case we don't get
>> selected and if so, should we duplicate the idea list into qemu wiki too?
> 
> I'm worried that this would look like orgs trying to game the system.

You're right. Maybe we should not do it after all.

> 
> Are there project ideas that involve both QEMU and libvirt changes?  For
> those I think it's fair to have them in both org's lists.  Anything that
> is purely QEMU or libvirt shouldn't be duplicated.
> 

So far none. But I have adjusted both our wikis to note that.

Michal

  reply	other threads:[~2016-01-27 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 17:28 Call for mentors and project ideas for Google Summer of Code 2016 Stefan Hajnoczi
2016-01-25 17:28 ` [Qemu-devel] " Stefan Hajnoczi
2016-01-26 10:13 ` [libvirt] " Michal Privoznik
2016-01-26 10:13   ` [Qemu-devel] " Michal Privoznik
2016-01-27 10:56   ` Stefan Hajnoczi
2016-01-27 10:56     ` [Qemu-devel] " Stefan Hajnoczi
2016-01-27 11:06     ` Michal Privoznik [this message]
2016-01-27 11:06       ` Michal Privoznik
2016-01-28 11:01       ` Stefan Hajnoczi
2016-01-28 11:01         ` [Qemu-devel] " 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=56A8A4AE.7070801@redhat.com \
    --to=mprivozn@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@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.