git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Victoria Dye <vdye@github.com>
To: Christian Couder <christian.couder@gmail.com>,
	git <git@vger.kernel.org>,
	Kousik Sanagavarapu <five231003@gmail.com>,
	Shuqi Liang <cheskaqiqi@gmail.com>
Cc: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
	Hariom verma <hariom18599@gmail.com>
Subject: Re: Projects for the next Outreachy round
Date: Tue, 26 Sep 2023 10:18:24 -0700	[thread overview]
Message-ID: <1c12ac0a-5e45-bb27-c452-250ffd4b9320@github.com> (raw)
In-Reply-To: <CAP8UFD1bsez-eMis5yH7Esds+LkhMnj0qTUMFPL1tRuDv2fiPw@mail.gmail.com>

Christian Couder wrote:
> About the "More Sparse Index Integrations" Shuqi worked on, mentored
> by Victoria, I am likely not the best person to mentor it, but I think
> I could manage. It would be nice though if I got an idea about what
> should be done next and how much work is left in general in this area.
> (Shuqi's GSoC final report at
> https://cheskaqiqi.github.io/2023/08/22/Final/ doesn't talk much about
> this.) Perhaps even if Shuqi is continuing to work on the project,
> there is still work that could be done in parallel on other commands
> than the ones he is working on.

To be honest, I'd recommend against using "More Sparse Index Integrations"
as a project again - I was actually going to suggest "retiring" the project
after this past GSoC term. The remaining commands are all fairly complex, to
the point that they'd be challenging even for someone that's done a lot of
sparse index work.

All that said, if someone is *really* interested in this project, you might
be able to get it to work. You'll probably want to limit the scope to one
command and make sure there's a strong emphasis placed on testing. Sparse
index integrations can introduce a lot of subtle bugs (e.g. the one Shuqi
found in 'diff' [1]), and a buggy command is worse for users than lacking
sparse index compatibility.

I hope that helps!
- Victoria

[1] https://lore.kernel.org/git/20230811142211.4547-3-cheskaqiqi@gmail.com/

> 
> Sorry for the late request, but please let me know soon about this.
> 
> Thanks,
> Christian.


  parent reply	other threads:[~2023-09-26 17:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 14:48 Projects for the next Outreachy round Christian Couder
2023-09-26 16:39 ` Kousik Sanagavarapu
2023-09-27  6:26   ` Christian Couder
2023-09-26 17:18 ` Victoria Dye [this message]
2023-09-27  6:18   ` Christian Couder
2023-09-26 22:23 ` Emily Shaffer
2023-09-27  6:14   ` Christian Couder
2023-09-27  3:30 ` Shuqi Liang
2023-09-27  6:33   ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1c12ac0a-5e45-bb27-c452-250ffd4b9320@github.com \
    --to=vdye@github.com \
    --cc=cheskaqiqi@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=five231003@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hariom18599@gmail.com \
    --cc=kaartic.sivaraam@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).