Re: Git in GSoC 2022?

From: Christian Couder <christian.couder@gmail.com>
Date: Jan 27, 2022, 09:44 UTC
Message-ID: <CAP8UFD38WDwMKf3tMKGt6hMxmsuZk2JkDRJaOZsXFqHvbVLRLQ@mail.gmail.com>
In-Reply-To: <9d2e58ab-2d8f-0797-84ed-0c1e8941edaa@gmail.com>

On Thu, Jan 27, 2022 at 4:55 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:

Show 11 quoted lines

>
> On 27/01/22 01.29, Kaartic Sivaraam wrote:
> >    - Project ideas: There are two mentioned in SoC-2021-Ideas[3]
> >      but both were picked by GSoC students the previous year. So,
> >      we would need new ones this year.
>
> I have several project ideas:
>
>    - Document the "binary diff" format. Right now we have documentation
>      for all diff formats used in Git, except for binary diff. Hint:
>      read `diff.c`

It seems a bit small as a project idea. Also we usually propose code related projects. It might be a good one for Google Season of Docs though:

https://developers.google.com/season-of-docs/

But I don't think we have ever participated in it.

Show 6 quoted lines

>    - Rewrite `git-request-pull.sh` in C. Currently the shell script
>      implementation hard-codes message template and only outputs to
>      stdout (though can be redirected to a file using shell means).
>      In the C version, message template can be configured (with the
>      default is same as current version) and introduces new
>      `-o/--output` option to specify output file.

In https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/ Dscho put this script in the "Probably better to leave them as shell scripts" category, so you might want to explain a bit more what would be the benefits of converting it. Also would you be interested in mentoring or co-mentoring a GSoC student working on this?

Thanks!