public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Ankush Mondal <[email protected]>
Cc: Amogh Dambal <[email protected]>
Cc: [email protected]
Subject: Re: Begin contribution journey to postgres
Date: Sat, 11 Apr 2026 15:38:41 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEw80_1i64eYaEbqh-RKcCPwWrZTVWND6sEBzDzeeiZg2JSSnw@mail.gmail.com>
References: <CAEw80_1QTstdxQCGQ+aAP7T7Q103YZviC40Ca65Af9XOYYbR4A@mail.gmail.com>
	<CADpxVfBJGTd=hCtgzn3EwFefgy73rDOxCTwF0gWCDD3Dq=kbnQ@mail.gmail.com>
	<CAEw80_1i64eYaEbqh-RKcCPwWrZTVWND6sEBzDzeeiZg2JSSnw@mail.gmail.com>

Ankush Mondal <[email protected]> writes:
> I was wondering if it would be possible for me to start working on some
> beginner-friendly issues or tasks. I’d really appreciate any pointers on
> where to find such issues or how to get started with contributing.

Well, there is a TODO list on our wiki, but sadly it's been nearly
unmaintained for a long time.  I wouldn't trust it as a guide to
things that should be done.  Moreover, most of the stuff that got onto
that list got there because it was too hard to get done quickly
and/or there wasn't consensus.

The best thing I can think of for a new developer to get started
is to help review some in-progress patches.  Even simple things
like "does it pass tests" or "is the documentation intelligible"
are helpful.  But your main goal should be to read the patches
and start learning your way around the Postgres code base that way.
We keep track of unapplied patches in our "commit fest" app:

https://commitfest.postgresql.org

Look through the list, select some that fit your interests,
start reading the associated mailing list threads.

BTW, pretty nearly all discussion about PG development happens on
pgsql-hackers.  The pgsql-novice list is meant for novice users'
questions, not so much novice developers.

Welcome!

			regards, tom lane

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Begin contribution journey to postgres
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox