Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2C8C89FB9B8 for ; Tue, 27 Feb 2007 01:47:56 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 15448-01 for ; Tue, 27 Feb 2007 01:47:53 -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 05BA29FB804 for ; Tue, 27 Feb 2007 01:47:52 -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 l1R5lEjE012560; Tue, 27 Feb 2007 00:47:14 -0500 (EST) To: "Jim C. Nasby" cc: Andrew Dunstan , pgsql-hackers@postgresql.org Subject: Re: Seeking Google SoC Mentors In-reply-to: <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> <20070227044345.GI29041@nasby.net> Comments: In-reply-to "Jim C. Nasby" message dated "Mon, 26 Feb 2007 22:43:46 -0600" Date: Tue, 27 Feb 2007 00:47:14 -0500 Message-ID: <12559.1172555234@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/1661 X-Sequence-Number: 99214 "Jim C. Nasby" writes: > 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. Agreed, except that in most cases a one-liner description of an idea isn't enough to get a meaningful reading on whether people think it's sane or not. To take our current example: do you think a one-liner description of full disjunctions would have gotten any feedback, except for requests for more detail? I'm not sure how we fix that --- laying out every acceptable project in great detail in advance won't happen for lack of manpower, and wouldn't be a good idea even if we could do it, because that sounds like a great way to stifle creativity. At the same time we can hardly promise to accept every wild-west idea that someone manages to turn into some kind of code. What can we tell the students other than "get as much feedback as you can, as early as you can"? regards, tom lane