From: Siddharth Asthana <siddharthasthana31@gmail.com>
To: Christian Couder <christian.couder@gmail.com>, git <git@vger.kernel.org>
Cc: Git at SFC <git@sfconservancy.org>,
Kaartic Sivaraam <kaartic.sivaraam@gmail.com>,
Pablo <pabloosabaterr@gmail.com>,
Usman Akinyemi <usmanakinyemi202@gmail.com>,
Tian Yuchen <cat@malon.dev>
Subject: Re: Participating in Outreachy's December 2026 cohort
Date: Mon, 14 Sep 2026 12:08:54 +0530 [thread overview]
Message-ID: <080f0485-3cf7-481a-8c39-c69afc81fbd8@gmail.com> (raw)
In-Reply-To: <CAP8UFD1hAjtPuWL8asZ2LzEMJKHGh2oO73n_tsUSADtEHh9b-g@mail.gmail.com>
On 09/09/26 14:42, Christian Couder wrote:
> On Sat, Sep 5, 2026 at 10:26 AM Christian Couder
> <christian.couder@gmail.com> wrote:
>
>> Thank you Usman, Kaartic and Pablo for volunteering to co-mentor!
>>
>> As no one objected to Git participating in Outreachy, I will submit a
>> Community Application for Git very soon.
>
> I have submitted a Community Application for Git, see:
>
> https://www.outreachy.org/communities/cfp/git/
>
> It says that we are willing to mentor and sponsor 2 interns. Hopefully
> we can have two (co-)mentors for each intern.
>
>> We will still have to sign up as mentors and find and submit projects
>> for interns to work on soon. We have until September 11, 2026, at 4 pm
>> UTC, which is less than one week from now.
>>
>> I have been thinking about the following projects:
>>
>> 1. Continue removing global state (and perhaps start libifying some
>> parts of the code base).
>>
>> I think Tian Yuchen said there is not much work left related to
>> "environment.{c,h}". So maybe we need to adjust the project compared
>> to its previous description or maybe make it about actually libifying
>> some parts of the code base.
>>
>> 2. Improve how command arguments and options are scanned and parsed.
>>
>> There are still a number of places in the code base where command
>> arguments are scanned or parsed using ad hoc hand-rolled code instead
>> of an existing API like the parse-options API or the early-scan API I
>> recently proposed in
>> https://lore.kernel.org/git/20260902161047.476753-1-christian.couder@gmail.com/.
>> Those pieces of ad hoc parsing or scanning code are often buggy and
>> difficult to maintain. I think porting them to an API while improving
>> that API if necessary can be an interesting project and bring a lot of
>> long term benefits to the project. As the parse-options API is already
>> quite feature-full, there are likely some areas where porting the
>> parsing code to it should be relatively easy which is newcomer
>> friendly.
>>
>> Let me know your opinion about these and if you have other project ideas.
>
> As no other project ideas were suggested, I submitted the project
> ideas I mentioned above. You can see them in the "Approved Projects
> for Git" section of the above mentioned page
> (https://www.outreachy.org/communities/cfp/git/) as:
>
> - Improve how command arguments and options are scanned and parsed
> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#improve-how-command-arguments-and-options-are-scan)
> - Reduce Git’s global state to enable Git's libification
> (https://www.outreachy.org/outreachy-dec-2026-internship-cohort/communities/git/#reduce-gits-global-state-to-enable-gits-libificati)
>
> The links to these projects are currently only available to approved
> mentors and coordinators. I applied to mentor both of these projects
> as this was required to submit the projects, but I am very much
> willing to remove myself from mentoring one of these projects.
>
> So please apply to (co-)mentor one of these projects, or submit other
> projects you are willing to mentor if you prefer.
Applied as co-mentor on the parse-options / early-scan one.
Thanks,
Siddharth
>
> Also let me know if you see things that could be improved in these
> projects or the Community Application for Git.
>
>>> Last year the Git community mentored a single intern. For a long time
>>> GitHub or GitLab used to sponsor Outreachy interns working on Git, but
>>> last year both declined to do it, so the intern was sponsored by the
>>> Git project itself.
>>
>> I will start poking people at GitLab about this, but it would be nice
>> if we could get some kind of help with this regarding other companies
>> too.
>
> I have mentioned GitLab, GitHub and OpenAI as organizations that could
> potentially sponsor Outreachy interns. I have also proposed an
> "Outreachy sponsoring" topic to be discussed at the Git Contributor's
> Summit 2026 next week.
>
> Thanks.
next prev parent reply other threads:[~2026-09-14 6:39 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 [this message]
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
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=080f0485-3cf7-481a-8c39-c69afc81fbd8@gmail.com \
--to=siddharthasthana31@gmail.com \
--cc=cat@malon.dev \
--cc=christian.couder@gmail.com \
--cc=git@sfconservancy.org \
--cc=git@vger.kernel.org \
--cc=kaartic.sivaraam@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox