From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Jeff King <peff@peff•net>
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>,
"Siddharth Kannan" <kannan.siddharth12@gmail•com>
Subject: Re: GSoC 2017: application open, deadline = February 9, 2017
Date: Wed, 08 Feb 2017 15:54:25 +0100 [thread overview]
Message-ID: <vpq37fowx5q.fsf@anie.imag.fr> (raw)
In-Reply-To: 20170125204504.ebw2sa4uokfwwfnt@sigill.intra.peff.net
Jeff King <peff@peff•net> writes:
> On Mon, Jan 23, 2017 at 04:02:02PM +0100, Matthieu Moy wrote:
>
>> * 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.
OK, it seems the last message did not raise a lot of enthousiasm (unless
I missed some off-list discussion at Git-Merge?).
The application deadline is tomorrow. I think it's time to admit that we
won't participate this year, unless someone steps in really soon.
If we don't participate, I'll add a disclaimer at the top of the
SoC-related pages on git.github.io to make sure students don't waste
time preparing an application.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2017-02-08 14:54 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
2017-02-08 14:54 ` Matthieu Moy [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vpq37fowx5q.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=christian.couder@gmail$(echo .)com \
--cc=cmn@dwim$(echo .)me \
--cc=git@vger$(echo .)kernel.org \
--cc=kannan.siddharth12@gmail$(echo .)com \
--cc=larsxschneider@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=pranit.bauva@gmail$(echo .)com \
--cc=t.gummerer@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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