Postgres Pro
Downloads
Home   >   mailing lists

Re: Contributing with code - Mailing list pgsql-hackers

From Antonio Belloni
Subject Re: Contributing with code
Date
Msg-id CADACt1roaYjgMLC6_mkdooF_qEUNd3bUB4n8=CGG2XtZxWPz8A@mail.gmail.com
Whole thread Raw
In response to Re: Contributing with code  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Contributing with code
List pgsql-hackers
Tree view
Sorry, but I did not want to start a flaming war against the TODO list with my first message. In all the other open source projects I have contributed code, the TODO list is always a start point to newcomers. There's no explicit message in the Postgresql TODO list saying that the projects there are hard, stuck or undesirable. So it's very confusing to a newbie who just want to help and try to learn something in the process.

And now I don't know If I should continue to work on the issue on my first message and post my ideas on the list, or if I should find other ways to contribute, for example, fixing bugs from the bug list.

Regards,
Antonio Belloni


Atenciosamente,
Antonio Belloni
abelloni@rioservice.com
+55 21 3083-1939
+55 21 99327-0200 
RIO SERVICE | Tecnologia em Movimento
Av. Pastor Martin Luther King Jr. 126 - Grupo 465
Centro Empresarial Shopping Nova América
http://www.rioservice.com


2018-01-03 0:47 GMT-02:00 Stephen Frost <sfrost@snowman.net>:
Noah, all,

* Noah Misch (noah@leadboat.com) wrote:
> On Tue, Jan 02, 2018 at 05:52:37PM -0500, Peter Eisentraut wrote:
> > On 12/31/17 22:43, Craig Ringer wrote:
> > > I'd rather rename it the "stuck, hard and abandoned projects list" ;) 
> >
> > That might actually be useful.
>
> +1.  When I do refer to a TODO entry, it's usually because the entry bears a
> list of threads illustrating the difficulty of a problem.  I like the project
> having such lists, but "TODO" is a bad heading for them.

Renaming the list is certainly an idea that I could get behind, though I
agree with Chris that we could keep it a bit more positive.  I also
agree that the TODO list tends towards projects that are stuck and hard,
which is why I actually think it wouldn't be that hard to go through and
mark the really hard things as really hard or even create an independent
page for them as I suggested elsewhere on this thread, because (at least
from my perception of it- which could be wrong) the overall list
doesn't actually change that much (see above wrt "stuck, hard and
abandoned" comment).  If we could see our way forward to really making
it clear that these things are stuck, hard or abandoned then maybe we
can make room for new projects to go on the list that are of reasonable
size for newcomers to the project.

Thanks!

Stephen

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [Patch] Make block and file size for WAL and relations defined atcluster creation
Next
From: Robert Haas
Date:
Subject: Re: pgsql: Implement channel binding tls-server-end-point for SCRAM