git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Breanna Devore-McDonald <Breanna.S.Devore-McDonald.1@nd.edu>,
	git <git@vger.kernel.org>
Subject: Re: Developing- Where to Start
Date: Mon, 14 Sep 2015 15:15:59 -0700	[thread overview]
Message-ID: <CAGZ79kbiFvm-C3MdED5Jja3b_S+WY1CR3iNQJ7MYcKjnZG4Nxg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD1NSAKsJDrav6dBF=92Ba9KY-MVtEydQPqfpSNrReSArw@mail.gmail.com>

On Mon, Sep 14, 2015 at 2:30 PM, Christian Couder
<christian.couder@gmail.com> wrote:
> Hi,
>
> On Mon, Sep 14, 2015 at 10:42 PM, Breanna Devore-McDonald
> <Breanna.S.Devore-McDonald.1@nd.edu> wrote:
>> Hello all,
>>
>> I'm a third year Computer Science student at the University of Notre
>> Dame, and for the final project of my Data Structures class, my group
>> and I have to find a way to contribute our (hopefully) newly-found
>> data structures and optimization knowledge to a well-known open source
>> project. We thought Git would be a great project to work on, but we
>> have no idea where to start. Can anyone offer ideas or parts of the
>> code that we could possibly help with? (a problem that is data
>> structures-related would be extremely helpful!)

One problem focused around data structures may be rewriting
the git bisect internal algorithm. Currently git bisect uses an O(n^2),
but there are better algorithms available such as [1]

[1] https://docs.google.com/document/d/1hzF8fZbsQtKwUPH60dsEwVZM2wmESFq713SeAsg_hkc/edit?usp=sharing
  The algorithm presented in that doc came up in a discussion
  between some Git developers, I just wrote it down. Maybe it's
  understandable.

That said, usually the tests in git bisect take the most time,
so it is an internal optimization related to data structures, whose
impact is estimated to matter only a bit.
Also I would estimate the project to rewrite git bisect to be quite a
lot of effort.

>
> The Git project often participate in the Google Summer of Code.
>
> This year we used the following resources to help potential GSoC
> students get involved in developing Git and find a project to work on:
>
> http://git.github.io/SoC-2015-Microprojects.html
> http://git.github.io/SoC-2015-Ideas.html

Yeah the microprojects are awesome to get into Git development!
Also look at http://git-blame.blogspot.com/p/leftover-bits.html
for smaller projects.

>
> A GSoC wrap up has been written recently in Git Rev News edition 7:
>
> http://git.github.io/rev_news/2015/09/09/edition-7/
>
> Earlier this year students from Ensimag (Grenoble, France) also
> contributed to Git and a small wrap up is available in Git Rev News
> edition 5:
>
> http://git.github.io/rev_news/2015/07/08/edition-5/
>
> I hope this will help you get started in your Git development journey.
>
> Best,
> Christian.
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-09-14 22:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-14 20:42 Developing- Where to Start Breanna Devore-McDonald
2015-09-14 21:30 ` Christian Couder
2015-09-14 22:15   ` Stefan Beller [this message]
2015-09-15  8:31 ` Matthieu Moy

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=CAGZ79kbiFvm-C3MdED5Jja3b_S+WY1CR3iNQJ7MYcKjnZG4Nxg@mail.gmail.com \
    --to=sbeller@google.com \
    --cc=Breanna.S.Devore-McDonald.1@nd.edu \
    --cc=christian.couder@gmail.com \
    --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).