git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git GSoC 2015

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 12, 2015, 19:53 UTC
Message-ID
<xmqq7fvmsy8f.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20150212093435.GA20118@peff.net>
Jeff King <peff@peff.net> writes:
Show 9 quoted lines
> The beginnings of the Google Summer of Code deadlines are upon us again.
> Organization applications are due February 20th (next Friday).
>
>  - 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.

Yes, I agree that the micro-project system was the best part of last year's GSoC process. In addition to the benefits you listed above, it allowed students to be exposed the development style here, and engage with the community very early in the program.

Previous: Jeff KingNext: Moritz Neeb
Message 2 of 7 in “Git GSoC 2015”
  1. Jeff KingFeb 12, 2015
  2. Junio C HamanoFeb 12, 2015
  3. Moritz NeebFeb 17, 2015
  4. Stefan BellerFeb 18, 2015
  5. Jeff KingFeb 18, 2015
  6. karthik nayakFeb 18, 2015
  7. Matthieu MoyFeb 18, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.