git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: GSoC 2012 application process
Date: Fri, 2 Mar 2012 04:11:14 -0500	[thread overview]
Message-ID: <20120302091114.GA3984@sigill.intra.peff.net> (raw)

The Google Summer of Code 2012 application process is underway. We have
participated for the past 5 years, so I assume we want to do so again.

If you don't know what GSoC is, read this:

  https://code.google.com/soc/

I've volunteered to be the organization admin again, but I would be
happy to step aside if somebody else wants to do it. I've started things
off by posting a draft of our application and starting a wiki page for
project ideas:

  https://github.com/peff/git/wiki/SoC-2012-Application

  https://github.com/peff/git/wiki/SoC-2012-Ideas

The application is due March 9th (next Friday).

At this point, we need:

  1. Somebody to volunteer as a backup admin.

  2. Project ideas to be added to the ideas page.

  3. Volunteers to mentor students.  Our criteria for mentors in the
     past has been to accept only those who have a history of
     contributing to git. But if you have an idea for a project and
     don't feel that you would be capable of mentoring, please feel free
     to start a discussion on the list. You may interest other people
     who can volunteer to mentor for it.

  4. People to read over the application and suggest improvements. It's
     adapted from last year's application. The general meaning should be
     the same, though I did bring it up to date as well clean up a few
     awkward bits.

In the past, we've used the kernel.org wiki for developing the SoC
materials. However, it's still not editable, and I don't think we have a
plan for what the "new" git wiki will be. I've put things up on this
GitHub wiki in the meantime; they can be migrated to an official wiki if
and when that happens.

I think you'll need a GitHub login to edit the wiki pages via the web
interface. You can also clone it here:

  git://github.com/peff/git.wiki.git

and I will be happy to take patches on the list.

-Peff

             reply	other threads:[~2012-03-02  9:11 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  9:11 Jeff King [this message]
2012-03-02 11:05 ` [git wiki PATCH 1/3] "Improving parallelism in various commands" project Thomas Rast
2012-03-02 11:05   ` [git wiki PATCH 2/3] "Designing a faster index format" project Thomas Rast
2012-03-02 11:08     ` Jeff King
2012-03-02 18:24     ` Junio C Hamano
2012-03-03  3:30       ` Nguyen Thai Ngoc Duy
2012-03-02 11:05   ` [git wiki PATCH 3/3] "Improving the `git add -p` interface" project Thomas Rast
2012-03-02 14:29   ` [git wiki PATCH 1/3] "Improving parallelism in various commands" project Nguyen Thai Ngoc Duy
2012-03-02 17:35   ` James Pickens
2012-03-02 14:52 ` GSoC 2012 application process Nguyen Thai Ngoc Duy
2012-03-02 21:48 ` Junio C Hamano
2012-03-03  0:09   ` Jeff King
2012-03-03 21:14 ` [git wiki PATCH] "Modernizing and expanding Git.pm" project Jakub Narebski
2012-03-03 22:23   ` Jeff King
2012-03-04 23:35 ` [git wiki PATCH] Teaching "--3way" to "git apply" Junio C Hamano
2012-03-05  5:33   ` Jeff King
2012-03-05  8:05     ` Thomas Rast
2012-03-05 10:02       ` Jeff King
2012-03-05 13:38 ` GSoC 2012 application process Matthieu Moy
2012-03-05 13:58   ` Jeff King
2012-03-05 14:42     ` Matthieu Moy
2012-03-05 23:53       ` Jeff King
2012-03-07 14:36 ` GSoC backup admin Jeff King
2012-03-07 15:27   ` Shawn Pearce
2012-03-08 21:18 ` [gsoc2012 wiki PATCH] "Use JavaScript library / framework in gitweb" project Jakub Narebski
2012-03-09  7:24   ` Jeff King
2012-03-10  0:46 ` [gsoc2012 wiki PATCH] "`git instaweb --serve`" project Jakub Narebski
2012-03-11 22:30 ` [gsoc2012 wiki PATCH] "Graphical diff in git-gui" project Jakub Narebski

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120302091114.GA3984@sigill.intra.peff.net \
    --to=peff@peff.net \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).