git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	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: [PATCH] Add ideas for GSoC 2024
Date: Fri, 9 Feb 2024 09:36:02 +0100	[thread overview]
Message-ID: <CAP8UFD2nc=p5DKyfAWEKUsSCWWWbNvBHS=a8=7TAAq_WoQNGRw@mail.gmail.com> (raw)
In-Reply-To: <F2684AB9-C4F3-43C3-91F2-A6D7D71F4927@gmail.com>

Hi Kaartic,

On Thu, Feb 8, 2024 at 3:02 PM Kaartic Sivaraam
<kaartic.sivaraam@gmail.com> wrote:
> On 6 February 2024 1:43:02 pm IST, Christian Couder <christian.couder@gmail.com> wrote:
> >On Tue, Feb 6, 2024 at 6:51 AM Patrick Steinhardt <ps@pks.im> wrote:
> >
> >> I don't quite mind either way. I think overall we have enough tests that
> >> can be converted even if both projects got picked up separately. And the
> >> reftable unit tests are a bit more involved than the other tests given
> >> that their coding style doesn't fit at all into the Git project. So it's
> >> not like they can just be copied over, they definitely need some special
> >> care.
> >>
> >> Also, the technical complexity of the "reftable" backend is rather high,
> >> which is another hurdle to take.
> >>
> >> Which overall makes me lean more towards keeping this as a separate
> >> project now that I think about it.
>
> Makes sense.  I suppose we need to capture the distinction more clearly in the ideas page.
>
> I've tweaked the doc for the same. Do check it out and feel free to suggest any corrections.
>
> Ideas page: https://git.github.io/SoC-2024-Ideas/

Thanks! It looks good to me too.

> >Ok, for me. If we have a contributor working on each of these 2
> >projects, we just need to be clear that the contributors should not
> >work together on the 2 projects as I think the GSoC forbids that.
>
> Indeed. We must make sure to communicate this to selected contributors if we end up choosing two of them for the unit test migration projects.
>
> On a related note, I think I could help as a co-mentor the non-reftable unit tests migration project if we don't find any other willing volunteer. :-)
>
> I'm hoping I should be of some help on guiding the contributor as a co-mentor. Feel free to let me correct me if I might potentially lack required knowledge.

Thanks a lot for volunteering to co-mentor with me! I think you don't
need any special knowledge and you will be very helpful as usual.

> >> > That said, how helpful would it be to link the following doc in the unit
> >> > testing related ideas?
> >> >
> >> > https://github.com/git/git/blob/master/Documentation/technical/unit-tests.txt
> >>
> >> Makes sense to me.
> >
> >To me too.
> >
> >> > Would it worth linking the reftable technical doc for the above ideas?
> >> >
> >> > https://git-scm.com/docs/reftable
> >> >
> >> > I could see it goes into a lot of detail. I'm just wondering if link to it
> >> > would help someone who's looking to learn about reftable.
> >>
> >> Definitely doesn't hurt.
> >
> >I agree.
>
> Thanks for the feedback. Included both of these links in relevant ideas too. Feel free to cross-check them!

Great, thanks!

  parent reply	other threads:[~2024-02-09  8:36 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
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 [this message]
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='CAP8UFD2nc=p5DKyfAWEKUsSCWWWbNvBHS=a8=7TAAq_WoQNGRw@mail.gmail.com' \
    --to=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=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).