From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: GSoC 2016: applications open, deadline = Fri, 19/2 Date: Fri, 12 Feb 2016 08:04:46 -0500 Message-ID: <20160212130446.GB10858@sigill.intra.peff.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: git , Christian Couder , Johannes Schindelin , Stefan Beller To: Matthieu Moy X-From: git-owner@vger.kernel.org Fri Feb 12 14:04:56 2016 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aUDP5-0000yd-Dt for gcvg-git-2@plane.gmane.org; Fri, 12 Feb 2016 14:04:55 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752696AbcBLNEv (ORCPT ); Fri, 12 Feb 2016 08:04:51 -0500 Received: from cloud.peff.net ([50.56.180.127]:40988 "HELO cloud.peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752426AbcBLNEt (ORCPT ); Fri, 12 Feb 2016 08:04:49 -0500 Received: (qmail 31120 invoked by uid 102); 12 Feb 2016 13:04:48 -0000 Received: from Unknown (HELO peff.net) (10.0.1.2) by cloud.peff.net (qpsmtpd/0.84) with SMTP; Fri, 12 Feb 2016 08:04:48 -0500 Received: (qmail 15970 invoked by uid 107); 12 Feb 2016 13:04:52 -0000 Received: from sigill.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.7) by peff.net (qpsmtpd/0.84) with SMTP; Fri, 12 Feb 2016 08:04:52 -0500 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Fri, 12 Feb 2016 08:04:46 -0500 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Fri, Feb 12, 2016 at 08:10:34AM +0100, Matthieu Moy wrote: > So, that makes it 4 possible co-mentors, i.e. 2 potential slots. Not > much, but it starts looking like last year ... ;-). > > Peff, would you be willing to co-admin with me (that would be cool, you > are the one with most experience here and you know the SFC stuff for > payment)? Are there any other co-admin volunteer? Yes, I'm willing to co-admin (though I'm also happy to step aside for somebody else if they would like to do it). The biggest task there is getting the application together. I went through the account creation steps at the site (which is different this year), and the application questions are: - Why does your org want to participate in Google Summer of Code? - How many potential mentors have agreed to mentor this year? - How will you keep mentors engaged with their students? - How will you help your students stay on schedule to complete their projects? - How will you get your students involved in your community during GSoC? - How will you keep students involved with your community after GSoC? - Has your org been accepted as a mentoring org in Google Summer of Code before? - Are you part of a foundation/umbrella organization? - What year was your project started? I think we can pull most of these answers from previous-year applications, but I haven't looked yet. In years past we collaborated on the answers via the git.github.io site, and I pasted them in place. -Peff