From: Stefan Beller <sbeller@google.com>
To: Jeff King <peff@peff.net>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git GSoC 2015
Date: Tue, 17 Feb 2015 16:05:24 -0800 [thread overview]
Message-ID: <CAGZ79kbFntyRSgNraz_UG6GstSDCvNZeg5_e1daFYnUGjDpFJg@mail.gmail.com> (raw)
In-Reply-To: <20150212093435.GA20118@peff.net>
On Thu, Feb 12, 2015 at 1:34 AM, Jeff King <peff@peff.net> wrote:
> The beginnings of the Google Summer of Code deadlines are upon us again.
> Organization applications are due February 20th (next Friday).
>
> - Do we want to do it?
>
> - Who would like to volunteer to be the org admin?
>
> I would like for it not to be me again, but I can help walk anyone
> through the application process (which largely just pulls from the
> prior year's application).
>
> - Any thoughts on procedures or lessons learned from last year?
>
> Personally, I really liked the "micro-project" system from last year.
> It made it easy to drop spammy candidates (because they didn't bother
> to do a micro-project at all), and it gave us some interaction with
> the candidates before we had to make a decision.
>
> -Peff
I have observed the GSoC last year and the micro projects seem to be
have helped a lot. Although I don't have a strong proficiency yet, I'd
may be a mentor this year?
Why do you not like to be the org admin again this year?
Thanks,
Stefan
next prev parent reply other threads:[~2015-02-18 0:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 9:34 Git GSoC 2015 Jeff King
2015-02-12 19:53 ` Junio C Hamano
2015-02-17 23:12 ` Moritz Neeb
2015-02-18 0:05 ` Stefan Beller [this message]
2015-02-18 15:58 ` Jeff King
2015-02-18 9:24 ` karthik nayak
2015-02-18 9:28 ` 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=CAGZ79kbFntyRSgNraz_UG6GstSDCvNZeg5_e1daFYnUGjDpFJg@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).