Re: My first contribution. Outreachy

[Jeff King <peff@peff.net>]

[Note that your email didn't make it to the mailing list because it
 was formatted as HTML. You may want to tweak your gmail settings to
 send plain text. Those of us on the to/cc did get it, though].

On Tue, Sep 19, 2017 at 03:45:18PM +0300, Оля Тележная wrote:

> If you could help me with choosing my first task and give some
> thoughts about where to look to solve the problem - that would be
> great.

Here are a few possibilities:

  - The task mentioned in:

       https://public-inbox.org/git/20170912172839.GB144745@aiede.mtv.corp.google.com/

    to convert the ad-hoc doubly-linked list implementation used in
    mru.c and mru.h to use the implementation from list.h.

    Note that I've pointed a few other people at this task, so you may
    find other candidates working on it, too (and it's possible if we
    get multiple good versions submitted yours might not get applied; I
    still think it's a good simple task that will help get you familiar
    with writing and submitting a patch).

  - We've been working with some leak-checking tools lately to try to
    find memory leaks in Git by running the test suite. You can see some
    example patches:

      https://public-inbox.org/git/1505936846-2195-1-git-send-email-martin.agren@gmail.com/

      https://public-inbox.org/git/1505936846-2195-2-git-send-email-martin.agren@gmail.com/

      https://public-inbox.org/git/1505936846-2195-3-git-send-email-martin.agren@gmail.com/

    You can find more instances by building with the leak-checker
    (you'll need to have a recent version of gcc or clang as your
    compiler):

      make SANITIZE=leak

    and then running individual test scripts, seeing what fails, and
    investigating the leak-checker output. There's a bit more discussion
    in the cover letter here:

      https://public-inbox.org/git/20170905130149.agc3zp3s6i6e5aki@sigill.intra.peff.net/

    Even though the patches are relatively small, there are a lot of
    things to learn here about building Git and running the tests. Don't
    hesitate to ask if you get stuck.

  - We've started marking small unfinished tasks with the
    "#leftoverbits" tag in emails, which can then be searched in the
    mailing list archive:

       https://public-inbox.org/git/?q=leftoverbits

    We don't use a formal bug-tracker, so this is a good way of seeing
    which discussions people feel newcomers may be able to jump in on.
    You may need to read the surrounding thread to get context, but
    again, don't hesitate to ask if you need help figuring out exactly
    what the task is or how it should be done.

-Peff