git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ayush Chandekar <ayu.chandekar@gmail.com>
To: Eric Frederickson <ericfrederickson68@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: A Question from a Hopeful Future Contributor
Date: Sat, 19 Jul 2025 05:01:28 +0530	[thread overview]
Message-ID: <CAE7as+Zf=ASEpz0YgAsMys3akbztFr+Z31jY6S2QXux3mxNBjg@mail.gmail.com> (raw)
In-Reply-To: <87y0slp23s.fsf@arch.mail-host-address-is-not-set>

Hi Eric,

On Sat, Jul 19, 2025 at 3:58 AM Eric Frederickson
<ericfrederickson68@gmail.com> wrote:
>
> Hello everyone,
>
> I hope that this message finds you well! I'm a software developer and passionate
> git user, and I'd like to try my hand at contributing to the project. I'm
> sending this message in order to ask Junio and the team if there's anything that
> would be particularly useful / appropriate for me to start looking into on that
> front. (Reading through the last few "What's cooking" messages, I didn't see
> anything that jumped out at me as needing a new contributor, which is why I'm
> asking in a separate message instead of replying to one of those.)
>

Welcome!

It's nice to see you excited about contributing to Git. To clear
things up, there isn't any team defined as such for Git, however ,
there are people working on it as volunteers or are employed by a
company (eg: GitHub, GitLab, etc) to work on Git.

If you want to know more about Git development and contribution
process, you can check it out here: [1]

> (Some notes on my skills: working on docs or tests is always a favorite for me,
> so things in those areas would be a great time. Also comfortable with low-level
> code, and any kind of scripting. Note too that academic background centers
> around programming language design and parsing related stuff, so I've got some
> fluency in those areas that I could hopefully apply well to the project if ever
> needed.)
>

Git has something called as a 'microproject'[2], which is a small and
a relatively simple patch meant to help new contributors get familiar
with the project. While microprojects are often done by students
applying for mentorship programs, they're a great way to get your
hands on Git development. They help you understand the codebase, and
the development and contribution workflow.

And as you mentioned that you like working on documentation or tests,
you'll find that most of the microproject ideas are based on these.

That said, you're more than encouraged to scratch your own itch as Junio said.

Thanks,
Ayush:)

[1]: https://git.github.io/Hacking-Git/
[2]: https://git.github.io/General-Microproject-Information/

  parent reply	other threads:[~2025-07-18 23:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-18 22:26 A Question from a Hopeful Future Contributor Eric Frederickson
2025-07-18 23:15 ` Junio C Hamano
2025-07-19 19:57   ` Eric Frederickson
2025-07-26 14:21   ` D. Ben Knoble
2025-07-28 15:02     ` Junio C Hamano
2025-07-28 16:54       ` D. Ben Knoble
2025-07-18 23:31 ` Ayush Chandekar [this message]
2025-07-19 22:06 ` Lucas Seiki Oshiro
2025-07-20  1:02   ` Eric Frederickson
2025-07-19 22:16 ` brian m. carlson
2025-07-20  1:22   ` Eric Frederickson

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='CAE7as+Zf=ASEpz0YgAsMys3akbztFr+Z31jY6S2QXux3mxNBjg@mail.gmail.com' \
    --to=ayu.chandekar@gmail.com \
    --cc=ericfrederickson68@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).