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>
Subject: Re: Git in GSoC 2024
Date: Wed, 31 Jan 2024 23:27:13 +0530 [thread overview]
Message-ID: <c61322de-8cd9-42b8-a04b-a8ae47b25c5e@gmail.com> (raw)
In-Reply-To: <ZbpGzAd6FGEeTdrh@tanuki>
Hi Patrick,
On 31 January 2024 6:40:36 pm IST, Patrick Steinhardt <ps@pks.im> wrote:
>On Tue, Jan 30, 2024 at 10:08:53AM +0100, Patrick Steinhardt wrote:
>> On Tue, Jan 30, 2024 at 09:38:48AM +0100, Christian Couder wrote:
>>
>> Yes, the tests in t0032-reftable-unittest.sh should be ported over to
>> the new unit test framework eventually, and I think that this might be a
>> good GSoC project indeed.
>>
Nice. Good to hear that.
>> If there is interest I'd also be happy to draft up some more topics in
>> the context of refs and the reftable backend. I'm sure there should be
>> some topics here that would be a good fit for the GSoC project, and I'd
>> be happy to mentor any such project in this context.
>
Great. Thanks for your interest in willing to mentor!
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 noticed that the starting period falls right into my honeymoon from
>June 17th until July 19th. This unfortunately makes it quite a lot
>harder for me to mentor projects alone. Still, I'd be happy to co-mentor
>or help out in other ways.
>
I too don't believe your vacation is going to be a deal breaker for you
being a mentor. It should be totally fine given that we get a backup
mentor who is also willing to mentor the candidate. (side note: I myself
have no knowledge about refs backends. So, I suppose I might not be able
to help co-mentor this one).
Reg. the timline [1] Jun 17th won't be much of the start. The community
bonding period starts May 1. Many contributors typically start dipping
their toes into their project right away. So, you would have ample time
before the start of the vacation to set the contributor up and going
with the project.
[1]: https://developers.google.com/open-source/gsoc/timeline
--
Sivaraam
next prev parent reply other threads:[~2024-01-31 17:57 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c61322de-8cd9-42b8-a04b-a8ae47b25c5e@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).