Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 1A0FA9FB82C for ; Mon, 26 Feb 2007 22:11:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 58749-09 for ; Mon, 26 Feb 2007 22:11:13 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id DB69A9FB7E2 for ; Mon, 26 Feb 2007 22:11:18 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l1R2AcHg009534; Mon, 26 Feb 2007 21:10:38 -0500 (EST) To: Andrew Dunstan cc: pgsql-hackers@postgresql.org Subject: Re: Seeking Google SoC Mentors In-reply-to: <45E36722.1080703@dunslane.net> References: <200702261311.39684.josh@agliodbs.com> <45E34F9F.7090002@dunslane.net> <200702261550.14414.wt@penguintechs.org> <45E36722.1080703@dunslane.net> Comments: In-reply-to Andrew Dunstan message dated "Mon, 26 Feb 2007 18:02:58 -0500" Date: Mon, 26 Feb 2007 21:10:38 -0500 Message-ID: <9533.1172542238@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/1618 X-Sequence-Number: 99171 Andrew Dunstan 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