Re: Seeking Google SoC Mentors - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Seeking Google SoC Mentors
Date
Msg-id 9533.1172542238@sss.pgh.pa.us
Whole thread Raw
In response to Re: Seeking Google SoC Mentors  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Seeking Google SoC Mentors  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: Seeking Google SoC Mentors  ("Jim C. Nasby" <jim@nasby.net>)
Re: Seeking Google SoC Mentors  (Dave Page <dpage@postgresql.org>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> Well, here's a question. Given the recent discussion re full 
> disjunction, I'd like to know what sort of commitment we are going to 
> give people who work on proposed projects.

Um, if you mean are we going to promise to accept a patch in advance of
seeing it, the answer is certainly not.  Still, a SoC author can improve
his chances in all the usual ways, primarily by getting discussion and
rough consensus on a spec and then on an implementation sketch before
he starts to do much code.  Lots of showstopper problems can be caught
at that stage.

I think the main problems with the FD patch were (1) much of the
community was never actually sold on it being a useful feature,
and (2) the implementation was not something anyone wanted to accept
into core, because of its klugy API.  Both of these points could have
been dealt with before a line of code had been written, but they were
not :-(
        regards, tom lane


pgsql-hackers by date:

Previous
From: ITAGAKI Takahiro
Date:
Subject: Re: Load distributed checkpoint
Next
From: "Matthew T. O'Connor"
Date:
Subject: Re: autovacuum next steps, take 2