All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Atharva Raykar <raykar.ath@gmail.com>
Cc: "Christian Couder" <christian.couder@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Emily Shaffer" <emilyshaffer@google.com>,
	"Eric Sunshine" <sunshine@sunshineco.com>,
	"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
	"Rafael Silva" <rafaeloliveira.cs@gmail.com>,
	"Philippe Blain" <levraiphilippeblain@gmail.com>,
	"Phillip Wood" <phillip.wood123@gmail.com>,
	"Johannes Sixt" <j6t@kdbg.org>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"ZheNing Hu" <adlternative@gmail.com>,
	"Jeff King" <peff@peff.net>,
	git@vger.kernel.org, "Shourya Shukla" <periperidip@gmail.com>
Subject: Re: [GSoC] The Final Git Dev Blog(s)
Date: Sun, 22 Aug 2021 17:45:57 +0530	[thread overview]
Message-ID: <b6ba6b44-c5f5-63f4-7fd1-19a1acd34770@gmail.com> (raw)
In-Reply-To: <m2lf4wys5o.fsf@gmail.com>

On 20/08/21 8:05 pm, Atharva Raykar wrote:
> 
> 2. Reflections on Working With the Git Community:
>     https://atharvaraykar.me/gitnotes/final-reflection
> 
>     This is a blog post that I wrote mostly for myself, and other people
>     interested in contributing to Git. It covers my personal experience
>     with my time here with the many ups and downs. I also wanted to thank
>     all the people who helped and collaborated with me in these 14 weeks.
> 

Good idea on trying to separate the reflection part of the blog from the
actual final report blog. This way, you didn't have to worry about the
report getting too long due to the reflections ;-)

You could consider linking each of these to the other ones, though. That
would help tie things up.

Some other thoughts:

> This mild dogfooding went a long way into making my work feel far more
> enjoyable and meaningful (if working on a project used my millions was
> already not meaningful enough).

Dogfooding is one of those thing that's surprisingly effective at all times :-)

BTW, s/my millions/by millions/

> CoViD.

Good to know that all are well. I resonate with what Zheing Hu says. Let's
hope we get through COVID-19 smoothly.

> This blog will continue, with a renewed purpose. I will be writing down
> important things I learnt in my time and bugs that new contributors
> could work on. I believe that writing guides and making contributions
> easier has some of the best effort-to-impact characteristics that
> I am looking for.

Very true. They are always helpful. I believe MyFirstContribution is
a testimony for this. It's glad to know you would like to help
contributors in that way :-)

> This won't be the last time you will see me on the list, of course. I
> still have patches waiting to make it to the list, and other work
> undergoing review—the only difference now is that it won't be under the
> GSoC banner anymore.
> 

Great!

> Have a great weekend!
>

Thanks and hope you have a good weekend too! Also, thanks for all
your contributions so far! Hoping to see more patches from you on
the list :-)

-- 
Sivaraam

  parent reply	other threads:[~2021-08-22 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 14:35 [GSoC] The Final Git Dev Blog(s) Atharva Raykar
2021-08-20 18:00 ` Junio C Hamano
2021-08-21  2:51 ` ZheNing Hu
2021-08-22 11:36 ` Kaartic Sivaraam
2021-08-24  9:53   ` Atharva Raykar
2021-08-22 12:15 ` Kaartic Sivaraam [this message]
2021-08-22 17:04   ` Kaartic Sivaraam
2021-08-24 10:00   ` Atharva Raykar
2021-08-23 15:42 ` Christian Couder
2021-08-24 10:22 ` Ævar Arnfjörð Bjarmason

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=b6ba6b44-c5f5-63f4-7fd1-19a1acd34770@gmail.com \
    --to=kaartic.sivaraam@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=adlternative@gmail.com \
    --cc=avarab@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=congdanhqx@gmail.com \
    --cc=emilyshaffer@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=levraiphilippeblain@gmail.com \
    --cc=peff@peff.net \
    --cc=periperidip@gmail.com \
    --cc=phillip.wood123@gmail.com \
    --cc=rafaeloliveira.cs@gmail.com \
    --cc=raykar.ath@gmail.com \
    --cc=sunshine@sunshineco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.