qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Alexander Graf <agraf@suse.de>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] GSoC mentor summit session "how to bind students long-term"
Date: Thu, 3 Nov 2011 11:32:20 -0200	[thread overview]
Message-ID: <20111103113220.4ae5fc7f@doriath> (raw)
In-Reply-To: <20111031085556.GA1557@stefanha-thinkpad.localdomain>

On Mon, 31 Oct 2011 08:55:56 +0000
Stefan Hajnoczi <stefanha@gmail.com> wrote:

> On Sat, Oct 29, 2011 at 04:00:34PM +0200, Alexander Graf wrote:
> > During the GSoC mentor summit there was a pretty interesting session on how to get students to stick with your project even after GSoC has ended. So far we haven't really been exactly successful in that respect :). I'll just post my notes below:
> > 
> >   - send successful students to conferences
> >   - set expectations on what we expect from students after gsoc, lay out the achievement plan for students to times beyond gsoc
> >   - give students responsibility, make them maintain parts (makes it harder for them to just leave, because they feel obliged)
> >   - shove students to community, no sidechannel communication, make them do A&Os on the public list
> 
> My personal experience being a GSoC student was that responsibility and
> fellowship matters most - it's what makes contributing addictive.  It's
> one thing to do an interesting project for 12 weeks but another to stick
> around because the group of developers have become your friends and you
> feel responsibility and satisfaction from supporting users on
> IRC/mailing lists.
> 
> The easiest way to give students responsibility is to get them actively
> involved in supporting users on IRC/mailing lists and fixing bugs.
> Doing this in addition to the official GSoC project is more likely to
> keep them hooked.  It helps turn them into a QEMU expert and someone who
> can help others - and hopefully they'll want to continue using this
> skill once the summer is over.

Please, let's create a http://wiki.qemu.org/GSoCMentors or something.

> 
> Stefan
> 

      reply	other threads:[~2011-11-03 13:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 14:00 [Qemu-devel] GSoC mentor summit session "how to bind students long-term" Alexander Graf
2011-10-31  8:55 ` Stefan Hajnoczi
2011-11-03 13:32   ` Luiz Capitulino [this message]

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=20111103113220.4ae5fc7f@doriath \
    --to=lcapitulino@redhat.com \
    --cc=agraf@suse.de \
    --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 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).