From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:54058) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLxPA-0006CT-1K for qemu-devel@nongnu.org; Thu, 03 Nov 2011 09:32:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RLxP8-00064x-P5 for qemu-devel@nongnu.org; Thu, 03 Nov 2011 09:32:28 -0400 Received: from mx1.redhat.com ([209.132.183.28]:12550) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RLxP8-00064o-Hz for qemu-devel@nongnu.org; Thu, 03 Nov 2011 09:32:26 -0400 Date: Thu, 3 Nov 2011 11:32:20 -0200 From: Luiz Capitulino Message-ID: <20111103113220.4ae5fc7f@doriath> In-Reply-To: <20111031085556.GA1557@stefanha-thinkpad.localdomain> References: <10B0F816-CA40-4642-8334-7C3E7F86D1EA@suse.de> <20111031085556.GA1557@stefanha-thinkpad.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Stefan Hajnoczi Cc: Alexander Graf , "qemu-devel@nongnu.org Developers" On Mon, 31 Oct 2011 08:55:56 +0000 Stefan Hajnoczi 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 >