git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Divyanshu Agrawal <agrawal-d@outlook.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: How to find places where I can contribute?
Date: Mon, 20 Feb 2023 10:59:13 +0100	[thread overview]
Message-ID: <CAP8UFD2gtdeaJ=9_DSC4knHiyZk2TeVEq8H_XWA4sdNVEqdhUw@mail.gmail.com> (raw)
In-Reply-To: <BM1PR01MB3139C97DD4B99D3024847874FEA79@BM1PR01MB3139.INDPRD01.PROD.OUTLOOK.COM>

Hi,

On Sun, Feb 19, 2023 at 3:39 PM Divyanshu Agrawal <agrawal-d@outlook.com> wrote:
>
> Hi!
> I want to contribute to the Git project. However, I'm not sure what I can
> contribute to.
>
> I'm used to the GitHub workflow, where I would look at the "Issues" section of
> a GitHub repository, and try to tackle bugs / features I think I will be able
> to work on.

Git was started before GitHub (and many such platforms) existed, and
we still use a mostly email based workflow, even if we do use GitHub
and other platforms for some things like code hosting and CI.

> 1. What is the equivalent for the Git project? How can I find issues/features
> that I can work on?
>
> 2. Is there a way I can find bugs/issues that are likely easy for a new
> contributor to pick up? Similar to a "good-first-issue" label on GitHub?

We have the following documentation:

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

There is also the microproject idea page from last year's GSoC:

https://git.github.io/SoC-2022-Microprojects/

We haven't updated it for this year yet, so some ideas might be
outdated. It might be a good idea anyway to discuss a bit your
micro-project idea on the list when you have found one before starting
to work on it.

> Based on your responses, I can also update the documentation, so that others
> like me can get started quickly!

We do use GitHub (at https://github.com/git/git.github.io/) for our
Developer Pages (at https://git.github.io/) where we have a lot of
useful docs for developers.

We also use GitHub (at https://github.com/git/git-scm.com) for our
main web site at https://git-scm.com/.

If you want to contribute as part of the Google Summer of Code 2023,
it's best to say so and to add "[GSoC]" at the start of your email
subjects.

Thanks and welcome to the Git community,
Christian.

  reply	other threads:[~2023-02-20  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 14:13 How to find places where I can contribute? Divyanshu Agrawal
2023-02-20  9:59 ` Christian Couder [this message]
2023-02-20 13:47   ` Divyanshu Agrawal
2023-02-20 21:31   ` Junio C Hamano
     [not found] ` <9DDB074D-2966-4096-B256-4035AB8EA778@gmail.com>
2023-02-20 13:48   ` Divyanshu Agrawal

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='CAP8UFD2gtdeaJ=9_DSC4knHiyZk2TeVEq8H_XWA4sdNVEqdhUw@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=agrawal-d@outlook.com \
    --cc=git@vger.kernel.org \
    /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).