Re: Git in Outreachy?

[Christian Couder <christian.couder@gmail.com>]

Hi Dscho and Kaartic,

On Mon, Sep 7, 2020 at 8:55 PM Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:

> On Mon, 7 Sep 2020, Kaartic Sivaraam wrote:
>
> > On 28-08-2020 12:26, Jeff King wrote:
> > > Are we interested in participating in the December 2020 round of
> > > Outreachy? The community application period is now open.
> > >
> > > I can look into lining up funding, but we'd also need:
> > >
> > >   - volunteers to act as mentors
> > >
> >
> > I'm willing to co-mentor a project for this term. I don't have any
> > particular preference of projects, though.

Thanks!

> > > I would appreciate help to find project ideas though. Are there still
> > > scripts that are worth converting to C (excluding git-bisect.sh and
> > > git-submodule.sh that are still worked on)?
> >
> > I think Dscho's e-mail linked below gives a nice overview of the various
> > scripts and their likely status as of Jan2020:
> >
> > https://lore.kernel.org/git/nycvar.QRO.7.76.6.2001301154170.46@tvgsbejvaqbjf.bet/
> >
> > I'm guessing only the status of submodule has changed as it's being
> > worked on now.
>
> No, not quite. The `git-merge-*.sh` ones I called "trivial" are already
> being worked on by Alban Gruin:
> https://lore.kernel.org/git/20200901105705.6059-1-alban.gruin@gmail.com/
>
> And `git-legacy-stash.sh` is no more, as of v2.27.0~180^2.
>
> But yes, other than that, my summary still holds.

To summarize more, it seems to me that only the following scripts
could be worth converting:

git-difftool--helper.sh
git-mergetool--lib.sh
git-mergetool.sh

I wonder if they are really worth converting though, as they should
probably all be converted together and we would likely also need to
convert the scripts in mergetools/ at the same time. And then there
should be a way to still easily configure things for users. So perhaps
a better way to approach this would be first to convert the scripts in
mergetools/ into config files.

Best,
Christian.