git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Patrick Steinhardt <ps@pks.im>,
	Christian Couder <christian.couder@gmail.com>,
	Karthik Nayak <karthik.188@gmail.com>,
	Jialuo She <shejialuo@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: Git in GSoC 2025
Date: Tue, 28 Jan 2025 23:00:40 +0530	[thread overview]
Message-ID: <c39c5424-71d0-4b6d-90b1-a6a70f2ee61b@gmail.com> (raw)
In-Reply-To: <Z432QXJb_TfzNBa2@pks.im>

(Apologies for the delayed re-send. I just noticed that this one
  got dropped by the mailing list. I'll respond to existing replies
  in that thread)

Hi Patrick, Christian, Karthik and Jialuo,

Thank you very much for your interest in volunteering as a mentor!

On Mon, Jan 20, 2025 at 12:37 PM Patrick Steinhardt <ps@pks.im> wrote:

 > I'd be happy to mentor this year again. A couple of ideas:


Thank you for suggesting these ideas, Patrick! I've incorporated them 
into a draft ideas page for now. You can see them here:

https://git.github.io/SoC-2025-Ideas/

Kindly suggest any corrections to the description, project size /
difficulty as necessary. I've mentioned potential mentors based on what
I'm aware of so far.

Patrick, Christian and Karthik, kindly mention the ideas that you're
interested to mentor.

While I have not included them as of yet, I wonder if the following
ideas which we had last year[1] could still be retained this year:

- Implement consistency checks for refs. The idea could be about
   implementing further ref checks which Jialuo appears to be helping
   out with. We could leave it if Jialuo prefers to continue working on
   the same in a flow.

- Refactor git-bisect(1) to make its state self-contained

- Implement support for reftables in "dumb" HTTP transport

Would these be interesting ones to consider? Is anyone willing to
mentor these this time around?


 > I'll keep on thinking about potential topics.


Sure. That would be great! Others could also chime in with your
potential ideas. Also, do not hesitate to let us know if you're
interested in mentoring.

-- 
Sivaraam

  parent reply	other threads:[~2025-01-28 17:31 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 [this message]
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
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=c39c5424-71d0-4b6d-90b1-a6a70f2ee61b@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).