caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yotam Barnoy <yotambarnoy@gmail.com>
To: Adrien Nader <adrien@notk.org>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Google summer of code
Date: Wed, 15 Jan 2014 10:23:30 -0500	[thread overview]
Message-ID: <CAN6ygOmfhphtKFzqfwZgtddLBMJcPWT9_G6kh8A+eSTYbnP1ew@mail.gmail.com> (raw)
In-Reply-To: <20140115090434.GA10113@notk.org>

[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]

I actually don't think it's very hard to apply (in general). The
requirements page is here (
http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2014/help_page?ModPagespeed=noscript#1._How_does_a_mentoring_organization).
It's certainly much easier than applying for a grant.

Having participated as a mentor in another organization, and having seen
the application process every year, I can say that the main part is coming
up with a webpage full of ideas for projects. I think that already exists
partially on the ocamllabs wiki. I'd really like to see that wiki be
centralized and available from the ocaml.org site. The key thing is to
figure out which projects are doable by people in one summer. The next step
is that people need to volunteer for mentorship. Even 2 people are enough
for a start, but 3-4 are better. Finally, one person takes on the process
of filling out the application and submitting it.

One of the things that concern google, as can be seen in the webpage, is
that there's enough effort from the mentors to
a. weed out the poor candidates and
b. be in touch with/demand enough from the candidates to make sure that
they're actually working and not just slacking off for the summer. In my
old organization, the participants had to post blog updates every week or
so about their progress.

Other than that, there's not much to it.

-Yotam



On Wed, Jan 15, 2014 at 4:04 AM, Adrien Nader <adrien@notk.org> wrote:

> Hi,
>
> On Tue, Jan 14, 2014, Yotam Barnoy wrote:
> > Dear List
> >
> > Are there plans to apply for GSOC mentorship this year? Searching online
> > yielded only a rejected application from 2011. Applications for mentor
> > organizations are due February 14th.
>
> Then, if nothing has been started yet, it's probably already too late.
> GSoC is fairly constraining and time-consuming. Nowadays, projects which
> manage to do it have actually gotten experienced at it and this makes it
> more difficult for new participants: they don't only have to do things
> well, they have to do things better than projects which have been doing
> it for 10 years.
>
> There's also a feeling that Google doesn't care about what happens in
> OCaml-land (that's mostly speculation).
>
> I believe it might be worth trying again. Many things have changed and
> the projects that could be worked on now might appeal more to the GSoC
> organizers. That would be for 2015 in my opinion though.
>
> Regards,
> Adrien Nader
>
>
>

[-- Attachment #2: Type: text/html, Size: 3257 bytes --]

  parent reply	other threads:[~2014-01-15 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-14 23:04 Yotam Barnoy
2014-01-15  9:04 ` Adrien Nader
2014-01-15 13:31   ` Nicolas Braud-Santoni
2014-01-15 15:23   ` Yotam Barnoy [this message]
2014-01-15 18:38     ` Jon Harrop
2014-02-26 11:17 ` Anil Madhavapeddy
2014-02-26 12:06   ` Marco Canini

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=CAN6ygOmfhphtKFzqfwZgtddLBMJcPWT9_G6kh8A+eSTYbnP1ew@mail.gmail.com \
    --to=yotambarnoy@gmail.com \
    --cc=adrien@notk.org \
    --cc=caml-list@inria.fr \
    /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.
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 NNTP newsgroup(s).