From: Patrick Steinhardt <ps@pks.im>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
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: Thu, 1 Feb 2024 10:38:42 +0100 [thread overview]
Message-ID: <Zbtmoo8qTmj-yt99@tanuki> (raw)
In-Reply-To: <c61322de-8cd9-42b8-a04b-a8ae47b25c5e@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2796 bytes --]
On Wed, Jan 31, 2024 at 11:27:13PM +0530, Kaartic Sivaraam wrote:
> 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'll have a the beginning of next week and will think about topics
meanwhile.
> > 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
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!
Patrick
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-01 9:38 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 [this message]
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=Zbtmoo8qTmj-yt99@tanuki \
--to=ps@pks.im \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=karthik.188@gmail.com \
--cc=me@ttaylorr.com \
--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).