From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jaydeep Das <jaydeepjd.8914@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [Newcomer] Suggestions for microprojects
Date: Fri, 21 Jan 2022 23:37:23 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2201212330280.2121@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <e176d1b3-482b-899b-af24-ac03c65d103d@gmail.com>
Hi Jaydeep,
welcome to the project!
On Mon, 17 Jan 2022, Jaydeep Das wrote:
> I want to starting contributing to the git project but can't decide
> where to start.
In general, I would recommend to pick a project that is of personal
interest to you. If you have used Git for more than a week, I am _certain_
that you found things you wish Git did better. That would be the kind of
project that I'd think would be ideal.
> I have read the coding-style and contributing guidelines stuff from the
> website and am eager to start writing code. Is there any small patches
> that I can make in the codebase that could help me get started with it?
There are two public bug trackers for the Git project, although I must
make clear that neither has been officially accepted by the Git project as
authoritative. The official bug tracker is the Git mailing list (which
lacks any tooling, of course, to find all reported and still unfixed
bugs). The two aforementioned bug trackers can be found here:
https://github.com/gitgitgadget/git/issues
and
https://crbug.com/git
If you want some easy project, I would suggest to look at the first bug
tracker because some tickets in there are labeled with "good first issue",
e.g. this one:
https://github.com/gitgitgadget/git/issues/636
Ciao,
Johannes
next prev parent reply other threads:[~2022-01-21 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 7:17 [Newcomer] Suggestions for microprojects Jaydeep Das
2022-01-18 8:40 ` Christian Couder
2022-01-21 22:37 ` Johannes Schindelin [this message]
2022-01-22 5:01 ` jaydeepjd.8914
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=nycvar.QRO.7.76.6.2201212330280.2121@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jaydeepjd.8914@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.
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).