git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	Karthik Nayak <karthik.188@gmail.com>,
	Jialuo She <shejialuo@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: Git in GSoC 2025
Date: Fri, 7 Feb 2025 13:02:25 +0530	[thread overview]
Message-ID: <a2a76725-5778-4b7d-a266-c3a1431316ce@gmail.com> (raw)
In-Reply-To: <CAP8UFD0GEmsJDFzVAV1bgBNeD6K3auH4paWEKE6=f0=_E6gifA@mail.gmail.com>

Hi Christian, Karthik, Patrick, Jialuo and all,

On 05/02/25 18:50, Christian Couder wrote:
> Hi Kaartic and all,
> 
> On Tue, Feb 4, 2025 at 7:33 PM Kaartic Sivaraam
> <kaartic.sivaraam@gmail.com> wrote:
> 
> I have just added myself as a possible mentor. If possible I'd like to
> just co-mentor this project and someone else to be the main mentor for
> this project.
> 
 > ...
> 
> I have just added myself as a possible mentor. If possible I'd like to
> be the main mentor for this project.
> 

Thank you for adding yourself as a potential mentor!

With this, it seems to me like we could at the max. accept 3 students

>> Note that I haven't assigned any mentors / co-mentors for each project.
>> I suppose we could assign that based on the applications we receive and
>> the ideas that we end up selecting.
>>
>> Based on Christian's inputs, we should be able to distribute
>> projects among mentors well.
> 
> Yeah, I hope it will be possible to distribute projects among mentors well.
>

Indeed. From all of your inputs I was able to come to the following
allocation of mentor / co-mentor.

-- 8< --

Consolidate ref-related functionality into git-refs

- Mentor: Patrick
- Co-mentor: Jialuo / Christian

Refactoring in order to reduce Git’s global state

- Mentor: Christian
- Co-mentor: Karthik / Jialuo

Machine-Readable Repository Information Query Tool

- Mentor: Karthik
- Co-mentor: Patrick

Implement support for reftables in “dumb” HTTP transport

- Mentor: Patrick
- Co-mentor: Karthik

-- >8 --

Let me know if this sounds fine to all of you. So, I suppose we could
pick a maximum of 3 projects but we cannot pick both "Consolidate
ref-related functionality into git-refs" and "Implement support
for reftables in “dumb” HTTP transport" at the same time as Patrick
only prefers to be mentor in one project.

Based on this, I'll tweak the ideas page to mention that we could
pick a max of 3 candidates.


BTW, I've just submitted Git's application for GSoC. We should know
by February 26 about the selection result.

--
Sivaraam

  reply	other threads:[~2025-02-07  7:32 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-19 10:13 Git in GSoC 2025 Kaartic Sivaraam
2025-01-20  7:07 ` Patrick Steinhardt
2025-01-20 13:38   ` shejialuo
2025-01-21 11:47   ` Oswald Buddenhagen
     [not found]   ` <CA+ARAtqfXo75PzzB3cQjDbvLxwytUK=xJiGG=VHZ1sNCcfyktQ@mail.gmail.com>
2025-01-27  8:06     ` Patrick Steinhardt
2025-01-27 12:43       ` shejialuo
2025-01-28 18:20       ` Kaartic Sivaraam
2025-01-28 17:30   ` Kaartic Sivaraam
2025-02-02 11:52     ` Kaartic Sivaraam
2025-02-03  8:45       ` Patrick Steinhardt
2025-02-03 11:53       ` Karthik Nayak
2025-02-04  2:29       ` shejialuo
2025-02-04 18:33       ` Kaartic Sivaraam
2025-02-05 13:20         ` Christian Couder
2025-02-07  7:32           ` Kaartic Sivaraam [this message]
2025-02-07  8:07             ` Christian Couder
2025-02-07 10:55             ` Patrick Steinhardt
2025-02-11  5:18               ` Kaartic Sivaraam
2025-02-16 12:56                 ` Ghanshyam Thakkar
2025-02-16 13:53                   ` Kaartic Sivaraam
2025-02-16 17:48                     ` Junio C Hamano
2025-02-17 15:21                     ` Ghanshyam Thakkar
2025-03-07 10:01                     ` Karthik Nayak
2025-03-20 17:50                       ` Kaartic Sivaraam
2025-03-21 21:02                         ` Karthik Nayak
2025-02-08 15:34             ` shejialuo
2025-02-10 17:00             ` Karthik Nayak
2025-01-20  8:19 ` Christian Couder
2025-01-20 11:09   ` Patrick Steinhardt
2025-01-21 20:35     ` Junio C Hamano
2025-01-30  5:44       ` Kaartic Sivaraam
2025-01-30  7:32         ` Patrick Steinhardt
2025-01-30  8:37           ` Christian Couder
2025-01-30 10:56             ` Patrick Steinhardt
2025-01-30 19:18           ` Junio C Hamano
2025-01-30 21:00             ` Junio C Hamano
2025-01-31  4:51               ` Patrick Steinhardt
2025-01-31 16:09                 ` Junio C Hamano
2025-02-03  8:49                   ` Patrick Steinhardt
2025-01-31  4:48             ` Patrick Steinhardt
2025-02-03 13:21     ` Junio C Hamano
2025-02-04 18:36       ` Kaartic Sivaraam
2025-01-30  5:39   ` Kaartic Sivaraam
2025-01-20 10:12 ` Karthik Nayak
2025-01-20 13:27 ` shejialuo
2025-02-28  3:03 ` Kaartic Sivaraam
2025-02-28  5:06   ` shejialuo
2025-02-28  6:16   ` Patrick Steinhardt
2025-02-28  7:56   ` Christian Couder
2025-02-28 10:12   ` Ghanshyam Thakkar
2025-03-01  0:47   ` Kaartic Sivaraam
2025-03-03 10:00   ` Karthik Nayak

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=a2a76725-5778-4b7d-a266-c3a1431316ce@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=karthik.188@gmail.com \
    --cc=ps@pks.im \
    --cc=shejialuo@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).