qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] Summer of Code 2010
Date: Tue, 09 Mar 2010 08:14:32 -0600	[thread overview]
Message-ID: <4B9657C8.3080605@codemonkey.ws> (raw)
In-Reply-To: <20100308172047.6a0371b6@redhat.com>

On 03/08/2010 02:20 PM, Luiz Capitulino wrote:
>   Hi there,
>
>   Google has this wonderful program called Summer of Code, in which open source
> projects like ours, suggest possible projects and provide mentors to help
> selected students to do them.
>
>   It's a great opportunity for students to get in touch with open source
> development, also good for us to get some projects done and more people
> involved (students are paid too, btw).
>
>   The dead-line is a bit short: next friday (March, 12), more information
> in the program's page:
>
> http://socghop.appspot.com/
>    

I'd suggest creating a page on the qemu.org wiki and start collecting 
ideas.  I'd strongly suggest that all ideas are constructed like a 
release feature and have an appropriate wiki page.

I think the key to success with a student project is to have a wide 
range of success criteria.   If people post ideas to a common wiki page, 
we can review them and come up with a set of suggested items.

Regards,

Anthony Liguori

>   I didn't read it fully yet, but I _guess_ the most important is to come
> up with project ideas and mentors. Everything should be in a wiki.
>
> PS: I have participated as a student some years ago, didn't produce anything
>      useful, but was a great experience.
>
>
>    

  parent reply	other threads:[~2010-03-09 14:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-08 20:20 [Qemu-devel] Summer of Code 2010 Luiz Capitulino
2010-03-08 22:53 ` Alexander Graf
2010-03-09 13:19   ` Luiz Capitulino
2010-03-09 15:44   ` Natalia Portillo
2010-03-09 15:46     ` Alexander Graf
2010-03-09 15:50       ` Natalia Portillo
2010-03-09 15:56         ` Alexander Graf
2010-03-09 16:01           ` Natalia Portillo
2010-03-09 18:07             ` [Qemu-devel] " Paolo Bonzini
2010-03-09 18:36               ` Johannes Schindelin
2010-03-10  8:12                 ` Paolo Bonzini
2010-03-10 18:31                   ` Johannes Schindelin
2010-03-11  9:37                     ` Paolo Bonzini
2010-03-09 16:48           ` [Qemu-devel] " malc
2010-03-09 16:50             ` Alexander Graf
2010-03-10 11:23           ` Jes Sorensen
2010-03-10 11:26             ` Alexander Graf
2010-03-09  9:31 ` Johannes Schindelin
2010-03-09 10:58   ` Stefan Hajnoczi
2010-03-09 13:33   ` Luiz Capitulino
2010-03-09 14:53     ` Johannes Schindelin
2010-03-09 18:51       ` Jamie Lokier
2010-03-10 20:08       ` Luiz Capitulino
2010-03-09 14:14 ` Anthony Liguori [this message]
2010-03-09 15:55   ` Natalia Portillo
2010-03-09 16:48     ` Brian Jackson
2010-03-10 20:11     ` Luiz Capitulino
2010-03-10 20:33       ` Natalia Portillo

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=4B9657C8.3080605@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).