git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: AbdAlRahman Gad <abdobngad@gmail.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, karthik.188@gmail.com
Subject: Re: [Newcomer] Introducing myself and expressing interest in `Implement support for reftables in “dumb” HTTP transport` project
Date: Mon, 12 Aug 2024 17:33:08 +0300	[thread overview]
Message-ID: <2553ac83-70b2-4019-b6fb-0c0562e887c8@gmail.com> (raw)
In-Reply-To: <ZroQ8-7SUmli2SOC@tanuki>



On 8/12/24 16:41, Patrick Steinhardt wrote:
> On Sat, Aug 10, 2024 at 11:11:30PM +0300, AbdAlRahman Gad wrote:
>> Hi,
>>
>> My name is AbdAlRahman, I'm a senior computer science student.
>> I'm interested in working on the `Implement support for reftables in “dumb”
>> HTTP transport` project with the help of a mentor, I'm aware that the
>> project is not being worked on in GSOC but I was wondering if the project is
>> still not taken in general, and whether I can work on it outside of GSOC?
> 
> The project wasn't picked up by any of the students, so it certainly is
> fair game to be implemented for any interested party. But...
> 
>> If the project is not taken, what should I do next?
>>
>> I'm also aware that the mentors are busy with GSOC and might not have time
>> now.
>> I'm OK with starting whenever mentors are available, but hopefully, guide me
>> on what to do until then.
> 
> ... that being said, I probably do not have the capacity to mentor you
> on it until the next GSoC. So you would ultimately have to figure out
> most of the parts yourself, unless you are willing to wait until next
> year's GSoC (or somebody else wants to mentor).
> 
> Of course, you are free to send specific questions to the Git mailing
> list, and we try to do our best to answer such questions and help folks
> get their work landed. But the interaction would likely be way more
> limited compared to how mentoring looks like during the GSoC.
> 
>> Steps I've taken so far:
>>
>> For git:
>>
>> I worked on one of the micro-projects, modernizing a test script, The patch
>> series is now merged in the `next` branch, there are still a few
>> modernizations left in the file which I will work on after the first series
>> is merged.
>>
>> This taught me git contribution workflow and to expect to do multiple
>> iterations of the patch.
> 
> This is a good first step indeed.
> 
>> For the project:
>>
>> I've read the resources provided in the project description for GSOC [1] in
>> addition to a video [2] and an article [3] by one of the possible mentors.
>>
>> This gave me a high-level overview of the ref-table backend.
> 
> I'd point you into the direction of git-update-server-info(1). It
> updates auxiliary info for the dumb transport helper for the object
> and ref databases such that plain HTTP clients can figure out which
> files they need to fetch.
> 
> The realization to have is that this is not required for the reftable
> backend anymore because the information is already encoded as part of
> the "tables.list" file. You will have to think about how to figure out
> the ref storage format of a remote and then fetch the correct set of
> files.
> 
> So understanding that code as well as how the dumb HTTP transport is
> working will be the most important first steps.
> 
> Patrick

Thanks for your time! I'll begin by doing what you've suggested.


  reply	other threads:[~2024-08-12 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-10 20:11 [Newcomer] Introducing myself and expressing interest in `Implement support for reftables in “dumb” HTTP transport` project AbdAlRahman Gad
2024-08-12 13:41 ` Patrick Steinhardt
2024-08-12 14:33   ` AbdAlRahman Gad [this message]
2024-08-13 12:56 ` karthik nayak
2024-08-13 14:33   ` AbdAlRahman Gad

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=2553ac83-70b2-4019-b6fb-0c0562e887c8@gmail.com \
    --to=abdobngad@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=karthik.188@gmail.com \
    --cc=ps@pks.im \
    /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).