Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 1522C9FB962 for ; Tue, 27 Feb 2007 00:43:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 83112-04 for ; Tue, 27 Feb 2007 00:43:49 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id EDCE39FB8E3 for ; Tue, 27 Feb 2007 00:43:49 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id 0725A5644A; Mon, 26 Feb 2007 22:43:49 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Mon, 26 Feb 2007 22:43:46 -0600 Date: Mon, 26 Feb 2007 22:43:46 -0600 From: "Jim C. Nasby" To: Tom Lane Cc: Andrew Dunstan , pgsql-hackers@postgresql.org Subject: Re: Seeking Google SoC Mentors Message-ID: <20070227044345.GI29041@nasby.net> References: <200702261311.39684.josh@agliodbs.com> <45E34F9F.7090002@dunslane.net> <200702261550.14414.wt@penguintechs.org> <45E36722.1080703@dunslane.net> <9533.1172542238@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9533.1172542238@sss.pgh.pa.us> X-Operating-System: FreeBSD 6.1-RELEASE-p10 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.13 (2006-08-11) X-Hashcash: 1:20:070227:tgl@sss.pgh.pa.us::/2iHN0u2dLoEKlse:00000000000000000000 00000000000000000000000057iC X-Hashcash: 1:20:070227:andrew@dunslane.net::FypFslQ3sx7XsrJx:000000000000000000 0000000000000000000000005LyP X-Hashcash: 1:20:070227:pgsql-hackers@postgresql.org::dI+YGFb1vrXlGdcy:000000000 0000000000000000000000002pqv X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/1650 X-Sequence-Number: 99203 On Mon, Feb 26, 2007 at 09:10:38PM -0500, Tom Lane wrote: > 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 :-( Yes, but the list being discussed is SoC projects that the community would like to see done, which means most people would assume that #1 isn't an issue. We need to make sure that every project on the list of SoC ideas is supported by the community. -- Jim Nasby jim@nasby.net EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)