Re: A starter task

From: sia kc <siavosh(dot)kasravi(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tomas Vondra <tomas(at)vondra(dot)me>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A starter task
Date: 2024-09-15 21:15:31
Message-ID: CABrJ=6TNTAd-KmMQyri4nyApRWPR0MC40Rux9KLQEeCu0HBq+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

So isn't there something like Jira backlog to manage the tasks?

My plan is to do some really small tasks like adding an option to a command
but aim for harder ones like optimizer stuff.

On Mon, Sep 16, 2024, 00:14 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Tomas Vondra <tomas(at)vondra(dot)me> writes:
> > I think you can take a look at https://wiki.postgresql.org/wiki/Todo and
> > see if there's a patch/topic you would be interested in. It's really
> > difficult to "assign" a task based on a single sentence, with no info
> > about the person (experience with other projects, etc.).
>
> Beware that that TODO list is poorly maintained, so items may be out
> of date. Worse, most of what's there got there because it's hard,
> or there's not consensus about what the feature should look like,
> or both. So IMO it's not a great place for a beginner to start.
>
> > FWIW, maybe it'd be better to start by looking at existing patches and
> > do a bit of a review, learn how to apply/test those and learn from them.
>
> Yeah, this is a good way to get some exposure to our code base and
> development practices.
>
> regards, tom lane
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2024-09-15 21:22:41 Re: how to speed up 002_pg_upgrade.pl and 025_stream_regress.pl under valgrind
Previous Message Tomas Vondra 2024-09-15 20:53:36 Re: A starter task