Re: [GSoC] Microproject help

From: Eric Sunshine <sunshine@sunshineco.com>
Date: Mar 25, 2024, 21:37 UTC
Message-ID: <CAPig+cQAoK1UkgADFrnJfY4xw0kP6BypPAPe3aLoeFFGT_r2fQ@mail.gmail.com>
In-Reply-To: <xmqq1q7yhupa.fsf@gitster.g>

On Mon, Mar 25, 2024 at 5:23 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 17 quoted lines

> Eric Sunshine <sunshine@sunshineco.com> writes:
> > On Mon, Mar 25, 2024 at 11:40 AM vk <g@vkabc.me> wrote:
> >> If there is any low hanging fruits that you can suggest to me for the
> >> microproject, that will be great. I will also be searching throughout
> >> the mailing list to see if there are any potential microproject to work
> >> on.
> >
> > Searching the mailing list for "#leftoverbits"[1] can be a good way to
> > discover little tasks which may be suitable for a GSoC microproject.
>
> True, but with a caveat that they may range from "low hanging fruit"
> to "too hard, let's punt".  After seeing the anonymous questioners'
> question, I did go to that query page (actually I qualified the
> query further to list only the ones I gave the mark) and decided not
> to suggest it because I found that many recent ones are harder than
> "trivial changes suitable for a practice material to go through the
> review cycles" X-<.

Since the purpose of a GSoC microproject is to familiarize the candidate with the project's mailing-list workflow and to give the GSoC mentors a feel for how the candidate interacts, perhaps the easiest suggestion would be the old fallback of having the candidate look for a single test script which still uses `test -f` or `test -e` or such, and converting that to use one of the test_path_foo() functions from t/test-lib-functions.sh.