git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git <git@vger.kernel.org>,
	"Pranit Bauva" <pranit.bauva@gmail.com>,
	"Lars Schneider" <larsxschneider@gmail.com>,
	"Christian Couder" <christian.couder@gmail.com>,
	"Carlos Martín Nieto" <cmn@dwim.me>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Thomas Gummerer" <t.gummerer@gmail.com>
Subject: Re: GSoC 2017: application open, deadline = February 9, 2017
Date: Wed, 25 Jan 2017 15:45:05 -0500	[thread overview]
Message-ID: <20170125204504.ebw2sa4uokfwwfnt@sigill.intra.peff.net> (raw)
In-Reply-To: <vpq1svtstud.fsf@anie.imag.fr>

On Mon, Jan 23, 2017 at 04:02:02PM +0100, Matthieu Moy wrote:

> If the answer to one of the above question is yes, then:
> 
> * Who's willing to mentor? and to admin?

I did co-admin last year and the year before, but I made Matthieu do all
the work. :)

I do not mind doing the administrative stuff.  But the real work is in
polishing up the ideas list and microprojects page. So I think the first
step, if people are interested in GSoC, is not just to say "yes, let's
do it", but to actually flesh out these pages:

> * We need to write the application, i.e. essentially polish and update
>   the text here: https://git.github.io/SoC-2016-Org-Application/ and
>   update the list of project ideas and microprojects :
>   https://git.github.io/SoC-2017-Ideas/
>   https://git.github.io/SoC-2016-Microprojects/

That can be done incrementally by people who care (especially mentors)
over the next week or so, and doesn't require any real admin
coordination. If it happens and the result looks good, then the
application process is pretty straightforward.

If it doesn't, then we probably ought not to participate in GSoC.

-Peff

PS If we do participate, we should consider Outreachy as well, which can
   expand our base of possible applicants. Though note that ones who are
   not eligible for GSoC would need to be funded by us. Last year GitHub
   offered to cover the stipend for an Outreachy intern for Git. If
   there's interest I can see if that offer can be extended for this
   year.

  parent reply	other threads:[~2017-01-25 20:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 15:02 GSoC 2017: application open, deadline = February 9, 2017 Matthieu Moy
2017-01-24 11:28 ` Johannes Schindelin
2017-01-24 13:32   ` Christian Couder
2017-01-25 20:45 ` Jeff King [this message]
2017-02-08 14:54   ` Matthieu Moy
2017-02-08 15:43     ` Jeff King
2017-02-09  9:42     ` Christian Couder
2017-02-09 10:15       ` Matthieu Moy
2017-02-09 10:28         ` Siddharth Kannan
2017-02-09 10:49           ` Christian Couder
2017-02-09 10:45         ` Christian Couder
2017-02-09 12:11           ` Matthieu Moy
2017-02-09 12:22             ` Matthieu Moy
2017-02-09 12:28               ` Matthieu Moy
2017-02-09 13:17               ` Christian Couder
2017-02-09 21:38       ` Johannes Schindelin
2017-02-09 21:47         ` Stefan Beller
2017-02-09 12:18   ` Pranit Bauva
2017-03-18  9:01 ` Duy Nguyen
2017-03-18 17:42   ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170125204504.ebw2sa4uokfwwfnt@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=christian.couder@gmail.com \
    --cc=cmn@dwim.me \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@gmail.com \
    --cc=pranit.bauva@gmail.com \
    --cc=t.gummerer@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).