Re: Seeking Google SoC Mentors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Seeking Google SoC Mentors
Date: 2007-02-27 02:10:38
Message-ID: 9533.1172542238@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-students

Andrew Dunstan <andrew(at)dunslane(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew T. O'Connor 2007-02-27 02:12:20 Re: autovacuum next steps, take 2
Previous Message ITAGAKI Takahiro 2007-02-27 02:10:01 Re: [HACKERS] Load distributed checkpoint

Browse pgsql-students by date

  From Date Subject
Next Message Joshua D. Drake 2007-02-27 02:25:51 Re: Seeking Google SoC Mentors
Previous Message Josh Berkus 2007-02-26 23:46:39 Re: Seeking Google SoC Mentors