From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Divyanshu Agrawal <agrawal-d@outlook.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: How to find places where I can contribute?
Date: Mon, 20 Feb 2023 13:31:44 -0800 [thread overview]
Message-ID: <xmqqzg98gh1b.fsf@gitster.g> (raw)
In-Reply-To: <CAP8UFD2gtdeaJ=9_DSC4knHiyZk2TeVEq8H_XWA4sdNVEqdhUw@mail.gmail.com> (Christian Couder's message of "Mon, 20 Feb 2023 10:59:13 +0100")
Christian Couder <christian.couder@gmail.com> writes:
>> 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/
While these are good for GSoC applicants before they do a real
project, I didn't read the "where I can contribute?" as such---it
asks for something more real, not a toy "dip my toes" practice.
Perhaps looking for #leftoverbits in the list archive may be another
approach that would give readers a problem with real upsides?
Thanks.
next prev parent reply other threads:[~2023-02-20 21:31 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
2023-02-20 13:47 ` Divyanshu Agrawal
2023-02-20 21:31 ` Junio C Hamano [this message]
[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=xmqqzg98gh1b.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=agrawal-d@outlook.com \
--cc=christian.couder@gmail.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 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.