git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Patrick Steinhardt <ps@pks.im>,
	Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>, Taylor Blau <me@ttaylorr.com>,
	Junio C Hamano <gitster@pobox.com>,
	Victoria Dye <vdye@github.com>,
	Karthik Nayak <karthik.188@gmail.com>
Subject: Re: Git in GSoC 2024
Date: Sat, 3 Feb 2024 17:11:28 +0530	[thread overview]
Message-ID: <d4797f27-825b-4e2b-85a6-cc30f33934e3@gmail.com> (raw)
In-Reply-To: <Zbtmoo8qTmj-yt99@tanuki>

Hi Patrick, Karthik and Christian,

For the note, other project ideas and volunteer are always welcome. So, 
feel free to chime in if you have any ideas or wish to volunteer as a 
mentor to guide potential future contributors of the community. :-)

On 01/02/24 15:08, Patrick Steinhardt wrote:
> On Wed, Jan 31, 2024 at 11:27:13PM +0530, Kaartic Sivaraam wrote:
>>
>> I created a fairly rough SoC ideas page for now including a barebones
>> information about the unit test migration idea:
>>
>> https://git.github.io/SoC-2024-Ideas/
>>
>> Note well that the existing idea's description is far from complete and I
>> mostly just cooked it up to serve as a template for how the idea entry could
>> look like. Kindly contribute towards elaborating the same :-)
>>
>> Also, feel free to suggest ideas you have around refs and reftable backed,
>> Patrick. Those would be helpful.
> 
> I'll have a the beginning of next week and will think about topics
> meanwhile.
>

Thanks, Patrick! It would be great if you could share the same as soon 
as possible. The deadline for applying to GSoC is Feb 6 (18:00 UTC) and 
we need the ideas page to be decent enough before we go ahead with 
applying for this year.

If the elaborate project description could take time, feel free to share 
a paragraph or two that are supplemented with a few references. That 
should be sufficient for applying to GSoC.

Christian,

It would be great if you could look into and improve the detail for the 
unit test migration idea. I just added a very terse description based on 
what I could get my hands on. If you think the description we used for 
the Outreachy round would do, kindly update the page with the same or 
kindly share it here so that I could update the same in the ideas page :-)

> 
> Yeah, as long as there is a co-mentor that can take over during my
> absence I'm happy to do it. Karthik said that he'd be willing to cover
> me, which I think would be a good fit given that he's already got quite
> a bit of exposure to the reftable backend internally at GitLab. Thanks!
> 

Sounds good. Thank you for volunteering to co-mentor, Karthik!

-- 
Sivaraam


  reply	other threads:[~2024-02-03 11:41 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 18:16 Git in GSoC 2024 Kaartic Sivaraam
2024-01-30  8:38 ` Christian Couder
2024-01-30  9:08   ` Patrick Steinhardt
2024-01-31 13:10     ` Patrick Steinhardt
2024-01-31 17:57       ` Kaartic Sivaraam
2024-01-31 18:03         ` Kaartic Sivaraam
2024-02-01  9:00         ` Karthik Nayak
2024-02-01  9:38         ` Patrick Steinhardt
2024-02-03 11:41           ` Kaartic Sivaraam [this message]
2024-02-04 14:29             ` Kaartic Sivaraam
2024-02-05  8:39             ` [PATCH] Add ideas for " Patrick Steinhardt
2024-02-05 16:43               ` Christian Couder
2024-02-05 18:55                 ` Kaartic Sivaraam
2024-02-06  5:51                   ` Patrick Steinhardt
2024-02-06  8:13                     ` Christian Couder
2024-02-08 14:02                       ` Kaartic Sivaraam
2024-02-09  6:27                         ` Patrick Steinhardt
2024-02-09  8:36                         ` Christian Couder
2024-02-06  5:47                 ` Patrick Steinhardt
2024-02-06  8:26                   ` Christian Couder
2024-02-05 17:07             ` Git in " Christian Couder
2024-02-05 18:39               ` Kaartic Sivaraam
2024-02-21  5:02                 ` Kaartic Sivaraam
2024-02-21  6:19                   ` Patrick Steinhardt
2024-02-21  8:43                   ` Christian Couder
2024-02-21  8:59                   ` Karthik Nayak
2024-02-22  4:31                   ` Kaartic Sivaraam
2024-02-22  7:49                     ` Patrick Steinhardt
2024-02-22  8:57                       ` Karthik Nayak
2024-02-22 12:02                         ` Christian Couder
2024-02-22 14:05                       ` Kaartic Sivaraam
2024-02-22 15:52                         ` Patrick Steinhardt
2024-02-24 17:34                           ` Kaartic Sivaraam

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d4797f27-825b-4e2b-85a6-cc30f33934e3@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=me@ttaylorr.com \
    --cc=ps@pks.im \
    --cc=vdye@github.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).