Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 5D2D99FB43E; Tue, 27 Feb 2007 05:37:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 65961-04-2; Tue, 27 Feb 2007 05:37:39 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id 770669FB4BE; Tue, 27 Feb 2007 05:37:39 -0400 (AST) Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by svr2.hagander.net (Postfix) with ESMTP id EE10ADCC60C; Tue, 27 Feb 2007 10:37:37 +0100 (CET) Received: by svr2.hagander.net (Postfix, from userid 1000) id E8D5EDCC60E; Tue, 27 Feb 2007 10:37:37 +0100 (CET) Date: Tue, 27 Feb 2007 10:37:37 +0100 From: Magnus Hagander To: Dave Page Cc: Tom Lane , Andrew Dunstan , pgsql-hackers@postgresql.org Subject: Re: Seeking Google SoC Mentors Message-ID: <20070227093737.GH12721@svr2.hagander.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> <45E3F826.3080003@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45E3F826.3080003@postgresql.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/1680 X-Sequence-Number: 99233 On Tue, Feb 27, 2007 at 09:21:42AM +0000, Dave Page wrote: > 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. > > We cannot necessarily expect the students to work this way without > guidance if they are not familiar with our processes before they start. > The mentors should be there to guide not just with the technical aspects > of the project, but the procedural as well imho. IIRC, last time we had a pgsql-students (or similar) mailinglist for the SoC people. That was closed. Perhaps that's a bit counterproductive - it's better to get introduced to the "normal way of doing things" right away? With the help of the mentor, of course. //Magnus