Git GSoC 2015

Git GSoC 2015

[Jeff King]

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

Re: Git GSoC 2015

[Junio C Hamano]

Jeff King <peff@peff.net> writes:

> 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.

Re: Git GSoC 2015

[Moritz Neeb]

Le 12/02/2015 10:34, Jeff King a écrit :
> 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?
>

Unfortunately not so much response on this topic. I was planning to 
apply as a student. Therefore it would be great, if you'd apply. Being 
totally altruistic here, of course.

Moritz

Re: Git GSoC 2015

[Stefan Beller]

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

Re: Git GSoC 2015

[karthik nayak]

On 02/12/2015 03:04 PM, Jeff King 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?
I was planning on applying as a student. Would be wonderful if Git applies.
>   - 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
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Git GSoC 2015

[Matthieu Moy]

Jeff King <peff@peff.net> writes:

> 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?

I would love to participate, but I won't be able to spend as much time
as I did last year.

We always have mixed feelings on the actual outcome of GSoC, but I think
it's a really good thing on overall for the community (Git's, and more
generally "FLOSS") to encourrage young developers to participate.

>    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.

I second that. As a mentor, the work I should have done during the first
few days was already done indeed. It also helped dropping non-spammy
candidates: selecting on the quality of interaction during microproject
is better than judging only on resume+proposal.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: Git GSoC 2015

[Jeff King]

On Tue, Feb 17, 2015 at 04:05:24PM -0800, Stefan Beller wrote:

> 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?

Certainly. The first steps are helping with the project selection,
specifically:

  1. Populating the list of suggested projects (this week).

  2. Helping to review applications once they start coming in (in a
     month or so).

> Why do you not like to be the org admin again this year?

Because it's a non-zero time commitment, and I have many other things
I'd like to do. :)

Actually, I do not mind being the org admin too much if nobody else
wants to step up. But what I really need help on is the proposed project
list, which is part of the application (which is due on Friday). That is
not something I can fill out by myself.

-Peff