From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Tyler John Baxter <tybaxter@calpoly.edu>,
"git@vger.kernel.org" <git@vger.kernel.org>,
"christian.couder@gmail.com" <christian.couder@gmail.com>
Subject: Re: GSoC with Git - Tyler Baxter
Date: Thu, 14 Mar 2024 09:39:06 +0530 [thread overview]
Message-ID: <ADE61890-8237-4D5C-897D-B407726414D6@gmail.com> (raw)
In-Reply-To: <SN7PR08MB8441D40CF11CE1F143447287D12B2@SN7PR08MB8441.namprd08.prod.outlook.com>
Hi Tyler,
Thank you for your interest in contributing to Git.
On 12 March 2024 8:30:47 am IST, Tyler John Baxter <tybaxter@calpoly.edu> wrote:
>
>I had a look at the proposal idea list for this year’s Google Summer of Code with Git and found a lot of interest in the “Move existing tests to a unit testing framework”. I would really like to work on this project as part of GSoC 2024. Throughout my years as a programming student, I have time and time again set up unit testing for my programming projects and have become extremely familiar with the formatting and expectations of unit tests. After reading the specifics git laid out online, it is my understanding that I am to complete a microproject, review other’s contributions, and finally submit a proposal/application.
>
Indeed. You've got that part right.
>I was wondering if there was anything else you could suggest that would be helpful to me in this process.
>
I suppose what you've already noted is a good way to start contributing to Git. So, feel free to get startedwith it right away. Looking frward towards your contributions.
Feel free to reach out if you need any clarifications. :-)
--
Sivaraam
Sent from my Android device with K-9 Mail. Please excuse my brevity.
parent reply other threads:[~2024-03-14 13:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <SN7PR08MB8441D40CF11CE1F143447287D12B2@SN7PR08MB8441.namprd08.prod.outlook.com>]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ADE61890-8237-4D5C-897D-B407726414D6@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=tybaxter@calpoly.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).