git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Abhradeep Chakraborty <chakrabortyabhradeep79@gmail.com>
Cc: Git <git@vger.kernel.org>, Taylor Blau <me@ttaylorr.com>
Subject: Re: [GSoC][RFC][PROPOSAL] Reachability bitmap improvements
Date: Fri, 15 Apr 2022 01:59:38 +0530	[thread overview]
Message-ID: <0179a76a-182a-0501-a4ae-800ddb53b8cd@gmail.com> (raw)
In-Reply-To: <20220414082010.14217-1-chakrabortyabhradeep79@gmail.com>

On 14-04-2022 13:50, Abhradeep Chakraborty wrote:
> Kaartic Sivaraam <kaartic.sivaraam@gmail.com> wrote:
> 
>> That's good to know. Do let us know if you have any experience with C
>> and shell programming outside of your contributions to Git.
> 
> Thank you for reviewing my proposal. I used C language in my B.tech
> classes. I never used C in practical/real world projects before. So,
> putting altogether, no, I didn't use C and shell in real world projects
> before.
>

That's good to know. Thanks.

>> Taylor has shared feedback on the proposal and timeline which I hope are
>> helpful to you. Specifically, Taylor said:
>>
>>>
>>> So I think it makes sense to try and find a way you can dip your toes
>>> into 2-3 of the sub-projects and get a sense for what feels most doable
>>> and interesting, then focus on that before allocating time for more
>>> projects in the future.
>>   >
>>
>> I agree with this. It's better to be practical than ambituous when
>> planning the proposal.
> 
> Okay, I am willing to work on first sub-project then. Should I remove the
> other subprojects then?
> 

Rather than deciding the plan in haste, I would recommend that you put 
some more thought into deciding the plan for your proposal. Take some 
time to reflect on the different parts required for the project, 
potential things that might interfere with the project etc. This would 
help you come up with a more refined plan.

This might need some deeper understanding of the project that you would 
be working on. Do feel to ask us in case you face any issues with this.

Also, you could use Taylor's suggestion as a possible starting point for
the plan:

 > If you end up working on this, I would suggest budgeting a week or so
 > to try out a couple of different sub-projects, and then decide where
 > to spend your time from there.

Hope this helps,
Sivaraam

  reply	other threads:[~2022-04-14 20:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 20:09 [GSoC][RFC][PROPOSAL] Reachability bitmap improvements Abhradeep Chakraborty
2022-04-13 20:03 ` Kaartic Sivaraam
2022-04-14  8:20   ` Abhradeep Chakraborty
2022-04-14 20:29     ` Kaartic Sivaraam [this message]
2022-04-15  5:23       ` Abhradeep Chakraborty
  -- strict thread matches above, loose matches on Subject: below --
2022-04-19  0:10 [GSoC][RFC][Proposal] " Plato Kiorpelidis
2022-04-06 20:46 [GSoC][RFC][PROPOSAL] " Abhradeep Chakraborty
2022-04-06 20:04 Abhradeep Chakraborty
2022-04-13 19:29 ` Taylor Blau
2022-04-14  7:58   ` Abhradeep Chakraborty
2022-04-14 14:24   ` Philip Oakley
2022-04-15  5:28     ` Abhradeep Chakraborty

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=0179a76a-182a-0501-a4ae-800ddb53b8cd@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=chakrabortyabhradeep79@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=me@ttaylorr.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).