Re: Projects for the next Outreachy round

From: Christian Couder <christian.couder@gmail.com>
Date: Sep 27, 2023, 06:14 UTC
Message-ID: <CAP8UFD1gdLG2VMH2fkPQAajw17qz-FuVatiKrguh70e2VYEWAQ@mail.gmail.com>
In-Reply-To: <CAJoAoZmC-Ku80aSp5xkxfirJitoi_ai6ryK3cJ7Jkx_2fUjENw@mail.gmail.com>

Hi Emily,

On Wed, Sep 27, 2023 at 12:23 AM Emily Shaffer <nasamuffin@google.com> wrote:

Show 20 quoted lines

>
> On Tue, Sep 26, 2023 at 7:48 AM Christian Couder
> <christian.couder@gmail.com> wrote:
> >
> > Hi everyone, especially Shuqi and Kousik,
> >
> > September 29 is the deadline for proposing Outreachy projects. As we
> > have at least one mentor for now (me), we should propose at least one
> > project though.
> >
> > All ideas for projects are welcome, don't hesitate to suggest one!
>
> It is probably premature for this cycle. But once we have unit testing
> framework[1] in, I expect that moving tests from t/helper/test-foo.c +
> a sh test to invoke test-foo over to using the unit testing framework
> could be a tidy project for GSOC/Outreachy. Especially if we can have
> an example migration to refer to, which Siddharth from Google is
> working on in his 20% time just now :)
>
> 1: https://lore.kernel.org/git/cover.1692297001.git.steadmon@google.com/

Thanks for the great idea! I am going to propose this as the coding part of Outreachy should start only in December and I think there are good chances that the unit test framework will be merged by then. In case everything is not ready when Outreachy starts, I think we will probably find other unit tests or libification related work that the intern can do.

For example, I recently thought about converting commands that store config info in global variables and use old config functions like git_config_(int|bool|string|...) to instead use the git_config_get_*() functions and no more global variables. I wanted to ask about it today, but I think your suggestion would be better.

Thanks, Christian.