git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Isoken Ibizugbe <isokenjune@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Outreachy] Introduction and Interest in Contributing to the Git Community
Date: Wed, 4 Oct 2023 12:20:48 +0200	[thread overview]
Message-ID: <CAP8UFD0mMi2JkvqMdf2mfUw2gA0Sog42ks3umMgsG5k_+W75xg@mail.gmail.com> (raw)
In-Reply-To: <CAJHH8bHBA4emP2DkDEzcXncT4K5zEN-pCS+7jjer4R1_kkCkFA@mail.gmail.com>

Hi Isoken,

On Tue, Oct 3, 2023 at 12:21 PM Isoken Ibizugbe <isokenjune@gmail.com> wrote:
>
> Dear Git Community,
>
> I hope this email finds you well. My name is Isoken Ibizugbe, and I am
> writing to express my strong interest in joining the Git community as
> a contributor to the FOSS project. I recently came across the project
> description regarding "Moving existing tests to a unit testing
> framework" and was particularly intrigued by the opportunity to be
> part of this exciting endeavor.

Great, welcome to the Git community!

> As an aspiring software engineer, I have always admired the incredible
> work done by the Git community in developing and maintaining this
> widely-used version control system. The project's commitment to
> fostering collaboration and innovation aligns perfectly with my values
> and aspirations as a developer.
>
> I understand that Christian Couder is the mentor for this project, and
> I would be honored to have the opportunity to work under his guidance
> and expertise. I would greatly appreciate any advice or direction he
> can provide to help me get started on this journey.
>
> I am eager to learn, collaborate with the community, and contribute
> meaningfully to this project. Please let me know how I can formally
> start my journey as a Git contributor and if there are any specific
> guidelines or resources that you recommend for newcomers, as it was a
> bit confusing process for me to join this mailing list.

Sure, please take a look at the documentation we have on
https://git.github.io/, especially the pages and sections I mention
below.

First, we require that applicants make a small code contribution (we
call that a micro-project) to the Git project. This is explained here:

https://git.github.io/General-Microproject-Information/

If I have time, I will perhaps prepare a small list of possible
micro-project. For example we prepared this one for the Outreachy
Winter 2021-2022 round:

https://git.github.io/Outreachy-23-Microprojects/

but no promise. The "General-Microproject-Information" page has
information about how to find micro-project ideas anyway.

Now we have recently added a "Thoroughly check your eligibility in the
program" sub-section to that page. Please read it, check your
eligibility and confirm that you meet all the requirements soon.

Then there are links to tutorials and a number of other useful link
for Git developers on this page:

https://git.github.io/Hacking-Git/

Also the following page is useful as it contains more general
information about how to apply:

https://git.github.io/General-Application-Information/

> Once again, thank you for your time and for providing an opportunity
> for individuals like me to contribute to this remarkable project. I am
> enthusiastic about the potential of this project and the journey
> ahead.

Thanks for your enthusiasm,
Christian.

  reply	other threads:[~2023-10-04 10:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 10:19 [Outreachy] Introduction and Interest in Contributing to the Git Community Isoken Ibizugbe
2023-10-04 10:20 ` Christian Couder [this message]
2023-10-07 10:25   ` Isoken Ibizugbe
2023-10-08 10:50     ` Christian Couder
2023-10-09 13:31       ` Isoken Ibizugbe
2023-10-09 13:38         ` Christian Couder
2023-10-11  5:46           ` Isoken Ibizugbe
2023-10-11  8:47             ` Christian Couder
  -- strict thread matches above, loose matches on Subject: below --
2023-10-09 18:31 Doreen Wanyama
2023-10-11  6:06 ` Naomi Ibe
2023-10-11 14:48   ` Doreen Wanyama

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=CAP8UFD0mMi2JkvqMdf2mfUw2gA0Sog42ks3umMgsG5k_+W75xg@mail.gmail.com \
    --to=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=isokenjune@gmail.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).