qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] Summer of Code 2010
Date: Tue, 9 Mar 2010 10:33:16 -0300	[thread overview]
Message-ID: <20100309103316.7411655f@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.00.1003091030070.7596@pacific.mpi-cbg.de>

On Tue, 9 Mar 2010 10:31:23 +0100 (CET)
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:

> Hi,
> 
> On Mon, 8 Mar 2010, Luiz Capitulino wrote:
> 
> >  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).
> 
> Note that some students do not finish up their work, do not get properly 
> involved with the project, get the pay check, and then go somewhere else. 
> The time of the mentor is quite possibly just wasted in such a case. Quite 
> frustrating experience, believe me.

 I think that the role of the mentor is close to that of a teacher, from
this pov, it's not just wasted time at all (even if the project 'fails').

 Now, I understand what you mean and I fell sorry (and slightly bad)
about it, as my project didn't take the right direction.

 That said, I think that _part_ of the problem is about having the right
expectations and realistic goals.

  parent reply	other threads:[~2010-03-09 13:33 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 [this message]
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
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=20100309103316.7411655f@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=aliguori@us.ibm.com \
    --cc=avi@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).