From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57240) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RKqNC-0005z1-SY for qemu-devel@nongnu.org; Mon, 31 Oct 2011 07:49:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RKqNC-0005St-02 for qemu-devel@nongnu.org; Mon, 31 Oct 2011 07:49:50 -0400 Received: from mail-fx0-f45.google.com ([209.85.161.45]:62545) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RKqNB-0005Sm-Rk for qemu-devel@nongnu.org; Mon, 31 Oct 2011 07:49:49 -0400 Received: by faap15 with SMTP id p15so6463836faa.4 for ; Mon, 31 Oct 2011 04:49:48 -0700 (PDT) Date: Mon, 31 Oct 2011 08:55:56 +0000 From: Stefan Hajnoczi Message-ID: <20111031085556.GA1557@stefanha-thinkpad.localdomain> References: <10B0F816-CA40-4642-8334-7C3E7F86D1EA@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10B0F816-CA40-4642-8334-7C3E7F86D1EA@suse.de> Subject: Re: [Qemu-devel] GSoC mentor summit session "how to bind students long-term" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: "qemu-devel@nongnu.org Developers" 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. Stefan