git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Chandra Pratap <chandrapratap3519@gmail.com>
Cc: Patrick Steinhardt <ps@pks.im>,
	Christian Couder <chriscool@tuxfamily.org>,
	git@vger.kernel.org
Subject: Re: [GSoC] Blog: move and improve reftable tests in the unit testing framework
Date: Sun, 7 Jul 2024 20:34:46 +0530	[thread overview]
Message-ID: <12ce5c39-a7c5-4abd-a558-a789bde4de22@gmail.com> (raw)
In-Reply-To: <CA+J6zkTyVDJcOoZC-thRAOYNudVWB1wgye0Ezj3o1AO_5HOS6A@mail.gmail.com>

Hi Chandra,

On 7 July 2024 12:45:53 pm IST, Chandra Pratap 
<chandrapratap3519@gmail.com> wrote:>Hello everyone, here is my blog 
post for the sixth week of GSoC's
 >official Coding period:
 >https://chand-ra.github.io/2024/07/07/Coding-Period-Week-6.html
Thank you for consistently writing up these blog posts!

It gives a good overview of the progress of your GSoC project. That 
said, it would be even more helpful and interesting if you could also 
elaborate on the technical aspects in your blog. For instance, you mention:

 > I did face some roadblocks but was able to get over them due to the
 > experience I accumulated from the work I performed in the last few 
weeks.

You could possibly elaborate on what the challenge was and how you
tackled the same.

To add to this, Patrick gave a helpful overview elsewhere on what could 
be covered in these blogs. I'm sharing it here just in case:

 > The intent of the blog posts is to document what you have been doing
 > in the past week. So questions like the following:
 >
 >  - Did you learn something new?
 >  - Did you read through particular parts of Git?
 >  - Do you have questions and/or blockers that keep you from advancing?
 >  - Did you manage to remove any blockers that you had before?
 >  - Did you make progress on the implementation?
 >
 > Communication is of huge importance in GSoC as it helps the mentors,
 > but also others to evaluate your progress overall. It helps us to find
 > out early in case there's anything that you need help with and makes sure
 > that you're on track overall. Overall, it ensures that you get the help
 > that you need to make the project go as smooth as possible.You may want
 > to search through the Git mailing list. Past students in GSoC always
 > announced their new blog posts to the community, so you should be able
 > to find some inspiration when reading through their blogs 
:slightly_smiling_face:

Hope that helps!

--
Sivaraam

PS: I hope Patrick will excuse me for posting this here without his 
consent :-)

  reply	other threads:[~2024-07-07 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02  7:05 [GSoC] Blog: move and improve reftable tests in the unit testing framework Chandra Pratap
2024-06-10  6:01 ` Chandra Pratap
2024-06-16 13:21   ` Chandra Pratap
2024-06-23  6:27     ` Chandra Pratap
2024-07-01  5:42       ` Chandra Pratap
2024-07-07  7:15         ` Chandra Pratap
2024-07-07 15:04           ` Kaartic Sivaraam [this message]
2024-07-15  5:18           ` Chandra Pratap
2024-07-23  6:02             ` Chandra Pratap
2024-08-03 14:21               ` Chandra Pratap
2024-08-12 14:58                 ` Chandra Pratap

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=12ce5c39-a7c5-4abd-a558-a789bde4de22@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=chandrapratap3519@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --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).