git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Cc: Shawn Pearce <spearce@spearce.org>, Thomas Rast <tr@thomasrast.ch>
Subject: Git GSoC 2014
Date: Thu, 13 Feb 2014 04:10:37 -0500	[thread overview]
Message-ID: <20140213091037.GA28927@sigill.intra.peff.net> (raw)

The Google Summer of Code application process is upon us. We have about
34 hours until the deadline (2014-02-14T19:00 UTC) . That's not very
much time, but I know some people have been thinking about projects for
a while, so I have hope that we can put together an ideas page.

What we need immediately is:

  - somebody to be the backup admin (I am assuming I'll be the primary
    admin, but as always, if somebody else wants to...)

  - ideas ideas ideas

    The email I sent out last week generated some response, but what I
    really need are people to write up full ideas as they would be read
    by students (and by GSoC personnel who are reading our application).

    As mentioned in a related thread, I'd really like to avoid just
    reposting proposals that didn't get any traction in previous years.

    Tomorrow I'll try to look through some of the links that have been
    posted, or collect stuff from the list. But I really need other
    people to contribute, or it's going to be a lame list.

I've put the application draft here:

  http://git.github.io/SoC-2014-Org-Application.html

You can make suggestions in this thread, or edit it by cloning:

  https://github.com/git/git.github.io

and post a patch, or send a pull request, or I should be able to give
people push access to the repo. It's a bit of an experiment, in the same
realm as the wiki we've used in the past.

The idea page is there, too, but there's nothing good on it yet:

  http://git.github.io/SoC-2014-Ideas.html

-Peff

             reply	other threads:[~2014-02-13  9:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  9:10 Jeff King [this message]
2014-02-13 21:45 ` Git GSoC 2014 Thomas Rast
2014-02-13 22:50   ` Junio C Hamano
2014-02-14  7:26     ` Thomas Rast
2014-02-14  9:44   ` David Kastrup
2014-02-15 12:17     ` Thomas Rast
2014-02-15 12:35       ` Duy Nguyen
2014-02-15 13:03       ` David Kastrup
2014-02-15 23:47       ` Shawn Pearce
2014-02-14 17:53   ` Vicent Martí
2014-02-13 23:17 ` Ramkumar Ramachandra
2014-02-14 10:41   ` Jeff King
2014-02-14 15:30     ` Ramkumar Ramachandra
2014-02-14 17:29       ` Jeff King
2014-02-14 18:56 ` Jeff King

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=20140213091037.GA28927@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    --cc=tr@thomasrast.ch \
    /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).