X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 3009330DEFA; Fri, 13 Jun 2003 21:06:22 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 03849-01; Fri, 13 Jun 2003 18:06:11 -0300 (ADT) Received: from mobile.hub.org (u153n214.eastlink.ca [24.224.153.214]) by svr1.postgresql.org (Postfix) with ESMTP id 82D4630DDBF; Fri, 13 Jun 2003 18:06:11 -0300 (ADT) Received: by mobile.hub.org (Postfix, from userid 1001) id 712AE44D3; Fri, 13 Jun 2003 18:06:10 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mobile.hub.org (Postfix) with ESMTP id 6B8D244BD; Fri, 13 Jun 2003 18:06:10 -0300 (ADT) Date: Fri, 13 Jun 2003 18:06:10 -0300 (ADT) From: The Hermit Hacker X-X-Sender: scrappy@hub.org To: Robert Treat Cc: Tom Lane , Lamar Owen , Justin Clift , Bruce Momjian , jim@nasby.net, "pgsql-general@postgresql.org" Subject: Re: [HACKERS] SAP and MySQL ... [and Benchmark] In-Reply-To: <1055514791.7070.461.camel@camel> Message-ID: <20030613180420.G27289@hub.org> References: <200306111624.h5BGOHe06484@candle.pha.pa.us> <200306121149.07785.lamar.owen@wgcr.org> <3EE8B881.5070001@postgresql.org> <200306122253.36207.lamar.owen@wgcr.org> <28061.1055480935@sss.pgh.pa.us> <1055514791.7070.461.camel@camel> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200306/777 X-Sequence-Number: 43707 On Fri, 13 Jun 2003, Robert Treat wrote: > But we do need core's approval to add legitimacy to our efforts, > especially with some of the "marketing is bad" folks that live on > -hackers. We also need core's approval to get infrastructure changes > put into place to help our efforts. Huh? What infrastructure changes have ever gone through -core? > This overlooks the fact that you can't earn credibility with some of our > community unless you hack on the back-end. The uproar over the 7.3 press > release was a fine example of what happens when the "advocacy" guys try > to make a change to something non-technical that the "technical" guys > don't approve of. Actually, I thought at that time we had agreed to have two seperate press releases (assuming that that is what you are talking about?) ... one 'marketing driven', and one 'technically driven'?