Tomas Vondra <tomas@vondra.me> writes:
> Presumably a new contributor will start by discussing the patch first,
> and won't waste too much time on it.
Yeah, that is a really critical piece of advice for a newbie: no
matter what size of patch you are thinking about, a big part of the
job will be to sell it to the rest of the community. It helps a lot
to solicit advice while you're still at the design stage, before you
spend a lot of time writing code you might have to throw away.
Stuff that is on the TODO list has a bit of an advantage here, because
that indicates there's been at least some interest and previous
discussion. But that doesn't go very far, particularly if there
was not consensus about how to do the item. Job 1 is to build that
consensus.
regards, tom lane
