git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Re: GSoC 2008 application summary
Date: Wed, 23 Apr 2008 00:21:22 -0400	[thread overview]
Message-ID: <20080423042122.GL29771@spearce.org> (raw)
In-Reply-To: <20080422015933.GB4828@spearce.org>

"Shawn O. Pearce" <spearce@spearce.org> wrote:
> 
> If you are a student who wasn't selected, you should be receiving
> a more detailed message from me in the next few days regarding
> your proposal.  I really want to let everyone know what happened
> with their proposal, including the general reasoning behind why
> the project wasn't selected.

These notes have now all been individually emailed to students.

As GSoC applications are considered private unless accepted into
the program I have specifically avoided CC'ing these messages to the
mailing list.  Every message obviously contained the student's email
address, but each also addressed specific parts of the student's
non-public project proposal.

The way we selected our 6 students was driven by a number of factors:

 - availability of mentors

   As org admin I was trying to balance one student per mentor,
   so that each individual mentor could focus their available time
   to a single student's benefit.  Most mentors were willing to
   mentor only 1 or 2 specific project ideas.  To maximize our
   accepted students we had to accept a diverse range of projects.

 - limited slots

   With only 6 slots available to us in the end we had to make
   some tough decisions about which projects should be selected,
   and which wouldn't.  It would be nice if there were more slots
   then students (and we could take them all), but that is not the
   way such things work.

 - community interest

   We tried to select projects that will have a visible impact on
   the overall Git user community.

 - proposal quality

   We looked for well defined proposals that had measurable criteria
   for success, and a clear direction for reaching that goal within
   the time allotted by the GSoC calendar.

 - community interaction and student enthusiasm

   We looked for applications where the student was active on our
   IRC channel, or discussed their project on the mailing list, or
   significantly via private email with a potential mentor.

   In all such cases the students showed enthusiasm for the project
   idea and a genuine interest in making Git even better for everone.
   This was not required, but it certainly made the mentors feel
   that the student was more likely to be successful this summer.

If anyone has any questions, or would like further information
about our selection process this year, please feel free to ask.


Oh, and last but not least, I _really_ want to thank our crew of
2008 mentors for helping with the evaluation process.  They spent
some pretty considerable time over the last few weeks talking to
prospective students on IRC, this mailing list, and private email,
as well as reviewing applications through the official GSoC web
application portal thingy (which as it turns out is a lot less
cool of a web application than it sounds).  Their efforts were very
much appreciated.

-- 
Shawn.

  reply	other threads:[~2008-04-23  4:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22  1:32 Welcome to Git's GSoC 2008! Shawn O. Pearce
2008-04-22  1:59 ` GSoC 2008 application summary Shawn O. Pearce
2008-04-23  4:21   ` Shawn O. Pearce [this message]
     [not found] ` <bd6139dc0804212235p250b7335ide5359b43937869b@mail.gmail.com>
2008-04-22  6:03   ` Welcome to Git's GSoC 2008! Shawn O. Pearce
2008-04-25 16:46 ` Jakub Narebski
2008-04-26 17:29   ` Shawn O. Pearce
2008-04-26 18:28     ` Jakub Narebski
2008-04-26 18:59       ` Shawn O. Pearce

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=20080423042122.GL29771@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    /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).