On 28 Jan 2016, at 01:40, Moritz Neeb <lists@xxxxxxxxxxxxx> 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-- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html