From: Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
To: Stefan Beller <sbeller@google•com>, Jeff King <peff@peff•net>,
larsxschneider <larsxschneider@gmail•com>,
Johannes Schindelin <johannes.schindelin@gmail•com>,
"Junio C. Hamano" <gitster@pobox•com>,
Edward Thomson <ethomson@github•com>,
Christian Couder <christian.couder@gmail•com>,
saurabhsuniljain@gmail•com, pranit.bauva@gmail•com,
mehul.jain2029@gmail•com, tigerkid001@gmail•com,
huiyiqun@gmail•com, senorsen.zhang@gmail•com,
dpdineshp2@gmail•com, sauravsachidanand@gmail•com,
lists@moritzneeb•de
Cc: git <git@vger•kernel.org>
Subject: GSoC 2016: application period ongoing, a few advices
Date: Sat, 19 Mar 2016 13:26:29 +0100 [thread overview]
Message-ID: <vpqfuvmirgq.fsf@anie.imag.fr> (raw)
Hi,
Recipients of this email: the Git list, mentors and admins (I tried to
use the address you normally use, or the one on the GSoC site. Let me
know if I shall use another one), and students who showed interest in
GSoC (I may have missed some ...). Bcc-ed is a student who applied via
the web interface but did not disclose his email publicly yet.
As a reminder, the GSoC students application period has started (since
March 14, deadline = March 25th = soon).
Up to now, we have 2 ongoing applications (1 final PDF and one draft).
I didn't see much discussion about students proposals, and I'm a bit
worried about it. My main advice to students: make sure your
applications are seen and reviewed by as many people as possible, and
give them time to send feedback.
A few important things to know:
* Anything submitted on https://summerofcode.withgoogle.com/ is visible
only to people invited there. Don't hesitate to discuss on-list to get
feedback from other people (and don't hesitate to Cc people that may
be interested, not everybody reads the whole list).
* PDF final proposals are visible to mentors only after the deadline.
Nobody can comment on it before. Right now there's a final proposal
without a draft, I suspect I'd have a lot of comments to make on it
given the abstract, but I can't because I can't read the text.
* OTOH, drafts are meant to be read and commented before the deadline.
The new site suggests using a google doc that can be edited,
commented, ... and the same link can be posted to the list.
To potential mentors: please log in on the GSoC website and keep an eye
on the list of proposals. Note that unlike the old system, comments we
add there are only for mentors & admins, not seen by students.
Regards,
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next reply other threads:[~2016-03-19 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 12:26 Matthieu Moy [this message]
2016-03-23 7:23 ` GSoC 2016: application period ongoing, a few advices Moritz Neeb
2016-03-24 12:32 ` GSoC 2016: application period ongoing, deadline = tomorrow Matthieu Moy
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=vpqfuvmirgq.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp$(echo .)fr \
--cc=christian.couder@gmail$(echo .)com \
--cc=dpdineshp2@gmail$(echo .)com \
--cc=ethomson@github$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=huiyiqun@gmail$(echo .)com \
--cc=johannes.schindelin@gmail$(echo .)com \
--cc=larsxschneider@gmail$(echo .)com \
--cc=lists@moritzneeb$(echo .)de \
--cc=mehul.jain2029@gmail$(echo .)com \
--cc=peff@peff$(echo .)net \
--cc=pranit.bauva@gmail$(echo .)com \
--cc=saurabhsuniljain@gmail$(echo .)com \
--cc=sauravsachidanand@gmail$(echo .)com \
--cc=sbeller@google$(echo .)com \
--cc=senorsen.zhang@gmail$(echo .)com \
--cc=tigerkid001@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