git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Google Summer of Code 2007
Date: Sun, 25 Feb 2007 02:59:18 -0500	[thread overview]
Message-ID: <20070225075917.GC1676@spearce.org> (raw)

ShadeHawk and robinr brought up Google's Summer of Code on #git the
other day.  I had also been thinking about seeing if we cannot get
Git involved with SoC, so here goes... ;-)

The application deadline for organizations is March 12th.
The earliest that we can submit an application is March 5th, so we
still have time to kick ideas around and see if the community is
interested in participating in SoC.

Google's FAQ has a lot of details, but the important part which
lists what should be included in an application can be found here:

  http://code.google.com/support/bin/answer.py?answer=60303&topic=10727

I don't know how the great SoC filter works for organizations,
but last year's list (found at http://code.google.com/soc/) has a
number of projects listed on it that are actively using Git for their
version control.  It would be nice if the SoC program was able to
benefit multiple projects in one shot, by helping to improve Git. :)

I'd be happy to help put the application together and to probably
also serve as a mentor, but I'm only willing to put in the effort
if others are genuinely interested and will also help out.

Thoughts?

-- 
Shawn.

             reply	other threads:[~2007-02-25  7:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25  7:59 Shawn O. Pearce [this message]
2007-02-27 20:47 ` Google Summer of Code 2007 Johannes Schindelin
2007-02-28  8:42 ` Andy Parkins
2007-02-28  9:03   ` Matthieu Moy
2007-03-02 20:36     ` Johannes Schindelin
2007-02-28  9:35 ` Raimund Bauer
2007-02-28 15:39   ` Brian Gernhardt
2007-02-28 15:47     ` Shawn O. Pearce
2007-02-28 16:00       ` Brian Gernhardt
2007-03-01  2:08 ` Jakub Narebski
2007-03-01  8:03   ` Matthieu Moy
2007-03-01 21:34   ` Shawn O. Pearce
2007-03-04 22:10     ` Martin Langhoff

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=20070225075917.GC1676@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).