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
Cc: Junio C Hamano <gitster@pobox.com>,
	Andrew Ardill <andrew.ardill@gmail.com>,
	Eduardo D'Avila <erdavila@gmail.com>
Subject: Re: Helping on Git development
Date: Wed, 14 Sep 2011 19:14:27 -0400	[thread overview]
Message-ID: <20110914231427.GA5611@sigill.intra.peff.net> (raw)
In-Reply-To: <7vehzjugdz.fsf@alter.siamese.dyndns.org>

On Wed, Sep 14, 2011 at 11:29:28AM -0700, Junio C Hamano wrote:

> As to contributing to the project, right now, I think we have enough
> people who want to write code and documentation for Git, but what we lack
> are bandwidth to (this is not meant to be an exhaustive list):

Is there such a thing as enough coders? :)

Two things that got me started on git, and that I think are still
relevant today:

  1. Scratch your own itch. Surely git doesn't do something that you
     wish it did. Or did it faster. Or whatever. Try to dig up past
     discussions on the list to make sure you're not doing something
     that has already been tried and rejected, and then start hacking.
     Your patches may be terrible at first, but I think there are people
     willing to guide you if you actually have running code.

  2. Read the list. People will report bugs. Try reproducing them,
     bisecting them, creating minimal test cases, narrowing the issues
     down to certain configurations or a certain bit of code, etc.
     Sometimes that will lead you to propose a solution. Sometimes
     you'll just add to the discussion, and then somebody with more
     familiarity can pick up the topic from there. But you'll have
     helped them by doing some of the work, and you'll have learned more
     about how git works.

-Peff

  parent reply	other threads:[~2011-09-14 23:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOz-D1JW8RSR8kVWhT7v-DCbWayU8KhbePJwWrWvJwbmueRezQ@mail.gmail.com>
2011-09-14  3:05 ` Helping on Git development Eduardo D'Avila
2011-09-14  5:16   ` Andrew Ardill
2011-09-14 18:29     ` Junio C Hamano
2011-09-14 21:32       ` Jonathan Nieder
2011-09-14 23:14       ` Jeff King [this message]
2011-09-14 23:34         ` Junio C Hamano
2011-09-15  0:08           ` Jeff King
2011-09-15  6:24             ` Andrew Ardill
2011-09-15 15:50               ` Junio C Hamano
2011-09-15 17:21               ` 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

  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=20110914231427.GA5611@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=andrew.ardill@gmail.com \
    --cc=erdavila@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
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).