Git development
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: git <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	karthik nayak <karthik.188@gmail.com>,
	Siddharth Asthana <siddharthasthana31@gmail.com>,
	Ayush Chandekar <ayu.chandekar@gmail.com>,
	Chandra Pratap <chandrapratap3519@gmail.com>,
	Patrick Steinhardt <ps@pks.im>,
	Justin Tobler <jltobler@gmail.com>,
	Lucas Seiki Oshiro <lucasseikioshiro@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: [GSoC] Call for Mentors - Help Us Welcome More Contributors to Git
Date: Fri, 10 Apr 2026 08:31:22 +0530	[thread overview]
Message-ID: <7207a7f0-3806-4ff3-a3d2-2cdcc23f913a@gmail.com> (raw)

Hi all,

We have great news and a small challenge — and we need your help.

This year, Git received 19 GSoC proposals, which speaks to the growing 
interest in contributing to our project. We have 5 strong project ideas 
[1] and are working to select as much candidates as possible (at the 
moment we're capped at 3-4). We're constrained not by the quality of 
proposals, but by mentor availability. Right now, we have only 6 mentors 
(3 primary, 3 co-mentors), and that limits how many promising 
contributors we can take on.

That's where you come in.

If you have experience contributing to Git and can spare some time this 
summer, we'd love to have you on board as a mentor or co-mentor. 
Mentoring is one of the most direct ways to grow our community — many of 
today's long-term contributors got their start through exactly this kind 
of guidance. Karthik, Ayush and Chandra are examples of GSoC 
contributors now turned into community members contributing outside GSoC.

Even stepping up as a co-mentor makes a real difference.

We also have one self-proposed project from a candidate this year [2]. 
If anyone is willing to mentor them specifically, that would be very 
welcome.

If you're interested or have questions, please reply to this thread. 
Every additional mentor means one more contributor we can nurture into a 
long-term member of the Git community.

Thank you!

[[ References ]]

[1]: https://git.github.io/SoC-2026-Ideas/
[2]: 
https://public-inbox.org/git/CAOAgETPhYra3XrevHptFu0x-se8D9ovRtgfomwFbhq9rSTXu6A@mail.gmail.com/

--
Sivaraam


             reply	other threads:[~2026-04-10  3:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  3:01 Kaartic Sivaraam [this message]
2026-04-10 11:04 ` [GSoC] Call for Mentors - Help Us Welcome More Contributors to Git 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=7207a7f0-3806-4ff3-a3d2-2cdcc23f913a@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=ayu.chandekar@gmail.com \
    --cc=chandrapratap3519@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jltobler@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=lucasseikioshiro@gmail.com \
    --cc=ps@pks.im \
    --cc=siddharthasthana31@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