From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Pablo Sabater <pabloosabaterr@gmail.com>,
git <git@vger.kernel.org>, Git at SFC <git@sfconservancy.org>,
Usman Akinyemi <usmanakinyemi202@gmail.com>,
Tian Yuchen <cat@malon.dev>
Subject: Re: Participating in Outreachy's December 2026 cohort
Date: Thu, 17 Sep 2026 16:37:33 +0530 [thread overview]
Message-ID: <fbed7a60-57ab-439b-a550-2d2b76ff24c0@gmail.com> (raw)
In-Reply-To: <CAP8UFD3kd=6QHp2oB+t+g-2D8bY-Oe5+_Vk+RJeaCa_xhxGrsA@mail.gmail.com>
On 9/17/26 02:28, Christian Couder wrote:
> On Mon, Sep 14, 2026 at 11:41 AM Kaartic Sivaraam
>>> I've applied as co-mentor for the libification one, this way we have at
>>> least one mentor for each project.
>>>
>>
>> Cool, Pablo. I've approved your application and also Usman's. Right now
>> we appear to have 2 mentors per project:
>>
>> - Reduce Git’s global state to enable Git's libification
>>
>> - Usman Akinyemi
>> - Pablo Sabater
>>
>> - Improve how command arguments and options are scanned and parsed
>>
>> - Christian Couder
>> - Siddarth Asthana
>
> Great, thanks!
>
Just for clarity, this is tentative mentor allocation. We may need to
shuffle it a little bit based on the applications we receive. We'll see
how it goes.
>> Given that we already have enough mentors for both the projects and I
>> have some bandwidth, I wonder if it would make sense to also propose the
>> projects that we proposed for GSoC but were not actually taken up by
>> anyone. The following are the projects:
>>
>> - Implement promisor remote fetch ordering
>
> I think it's indeed a good idea to propose this project, even if it
> seems more difficult than the other projects we already propose.
>
Thank you, Christian! I have proposed the project. Kindly check and
approve it at your convenience. We have until Oct. 5, 2026 at 4pm UTC to
approve it.
If anyone is willing to co-mentor it, please chime in.
>> - Enhance promisor-remote protocol for better-connected remotes
>
> This one seems even more risky and difficult to me. I would suggest
> only proposing the previous one.
>
Cool. I've skipped it for now.
> Anyway as you will mentor it, feel free to propose the project you prefer.
>
I will mentor it but may need some help / guidance from you as you have
a more experience with this area of the code. I hope that's fine.
--
Sivaraam
next prev parent reply other threads:[~2026-09-17 11:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 10:55 Participating in Outreachy's December 2026 cohort Christian Couder
2026-08-26 11:39 ` Usman Akinyemi
2026-09-02 13:20 ` Kaartic Sivaraam
2026-09-03 10:24 ` Pablo Sabater
2026-09-05 8:26 ` Christian Couder
2026-09-09 9:12 ` Christian Couder
2026-09-14 6:38 ` Siddharth Asthana
2026-09-14 8:24 ` Kaartic Sivaraam
2026-09-14 8:37 ` Pablo Sabater
2026-09-14 9:41 ` Kaartic Sivaraam
2026-09-16 20:58 ` Christian Couder
2026-09-17 11:07 ` Kaartic Sivaraam [this message]
2026-09-19 13:43 ` Christian Couder
2026-10-05 18:19 ` Pablo Sabater
2026-10-08 13:20 ` Kaartic Sivaraam
2026-10-08 14:05 ` Usman Akinyemi
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=fbed7a60-57ab-439b-a550-2d2b76ff24c0@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=cat@malon.dev \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=pabloosabaterr@gmail.com \
--cc=usmanakinyemi202@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.