git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: "Vicent Martí" <tanoku@gmail.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>, git <git@vger.kernel.org>
Subject: Re: Git in GSoC 2014
Date: Wed, 26 Feb 2014 06:29:07 -0500	[thread overview]
Message-ID: <20140226112907.GA3599@sigill.intra.peff.net> (raw)
In-Reply-To: <CAFFjANTCU-OkydggYGy9tTJqx=TkWoVi2gJge4LUUkKcdB-eZQ@mail.gmail.com>

On Wed, Feb 26, 2014 at 12:25:36PM +0100, Vicent Martí wrote:

> On Wed, Feb 26, 2014 at 11:41 AM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
> > Since time is short, I already started on this.  I wrote a first draft
> > of an introduction for the students.  I also started looking for
> > microprojects.  I started going through our source files alphabetically,
> > and have already found six suggestions by "bundle.c", so I don't think
> > there will be a problem finding enough tiny things to do.
> 
> Note that for projects that are either libgit2-centric or mix Core Git
> and libgit2, it would be worth it to the students to submit a pull
> request on libgit2 (or ideally, on both projects, although that's
> going to be hard) in order to make themselves familiar with the code
> base.

Yeah, that makes sense. I think if students are thinking primarily about
one of the libgit2 projects, they should focus on interacting with that
community. Interacting with the mailing list is good, too, but I don't
see a need to do a patch for both.

Can you come up with a short list of micro-projects for libgit2, similar
to what Michael did for Git?

-Peff

  reply	other threads:[~2014-02-26 11:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 15:41 Git in GSoC 2014 Jeff King
2014-02-25 16:42 ` Dmitry S. Dolzhenko
2014-02-25 17:15 ` Michael Haggerty
2014-02-26 10:23   ` Jeff King
2014-02-26 10:41     ` Michael Haggerty
2014-02-26 11:04       ` Jeff King
2014-02-26 11:25       ` Vicent Martí
2014-02-26 11:29         ` Jeff King [this message]
2014-02-26 19:48       ` Junio C Hamano
2014-02-27  7:34         ` Michael Haggerty
2014-02-27 19:19           ` Junio C Hamano
2014-02-27 20:26             ` Michael Haggerty
2014-02-27 20:32               ` Junio C Hamano
2014-04-22  1:06                 ` Andrew Ardill
2014-04-22  2:18                   ` Brian Gesiak
2014-02-26 11:16 ` Duy Nguyen
2014-02-26 11:24   ` Vicent Martí
2014-02-26 11:30     ` Jeff King
2014-02-26 16:48       ` Shawn Pearce
2014-02-26 17:15 ` Git in GSoC 2014 Suggestion: core.filemode always false for cygwin Torsten Bögershausen

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=20140226112907.GA3599@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    --cc=tanoku@gmail.com \
    /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).