All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Schneider <larsxschneider@gmail.com>
To: Moritz Neeb <lists@moritzneeb.de>
Cc: git@vger.kernel.org
Subject: Re: Starting on a microproject for GSoC
Date: Thu, 28 Jan 2016 09:51:48 +0100	[thread overview]
Message-ID: <1FEDCA48-FE77-44C3-8C4A-65B4C435E6B3@gmail.com> (raw)
In-Reply-To: <56A96380.3020308@moritzneeb.de>


On 28 Jan 2016, at 01:40, Moritz Neeb <lists@moritzneeb.de> wrote:

> As the list of available microprojects 2016 is still to be created, I
> might need your help in finding a project to work on.

As Stefan already pointed out, working on something that scratches your (Git) itch is probably the best way to find a project.
My recent itch was that I broke a test on Linux which I did not realize as I primarily work on OSX. As a solution for myself I suggested a TravisCI patch to the mailing list and it was accepted:
https://travis-ci.org/git/git/branches 

I see a number of ways to improve the Git TravisCI integration:

* install CVS on the build machines to run t94?? and t96?? tests
* install SVN on the build machines to run t91?? tests
* install Apache Web Server to run 5539, 5550, and 5561
* investigate if it is possible to run t1509 root worktree test
* investigate if it is possible to add jgit to run t5310
* investigate why GIT_TEST_LONG=YesPlease does not work on TravisCI
* investigate if we can use pylint to analyze the git-p4 Python code
* investigate if we can trigger Coverity static code analysis for the Git master
  branch (hint: Stefan Beller already looked into this)
  https://scan.coverity.com/travis_ci

I think all of these tasks can be done without deep Git knowledge. However, working with the tests is quite a good way to learn more about a complex project like Git.

Cheers,
Lars

  parent reply	other threads:[~2016-01-28  8:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28  0:40 Starting on a microproject for GSoC Moritz Neeb
2016-01-28  1:18 ` Stefan Beller
2016-01-28 10:37   ` Moritz Neeb
2016-01-28  6:17 ` Andrew Ardill
2016-01-28  8:22   ` Johannes Schindelin
2016-01-28  8:51 ` Lars Schneider [this message]
2016-01-28 19:45 ` Junio C Hamano

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=1FEDCA48-FE77-44C3-8C4A-65B4C435E6B3@gmail.com \
    --to=larsxschneider@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lists@moritzneeb.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.