Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 8A3EF2E0096 for ; Mon, 2 Jun 2008 12:47:08 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 95133-01 for ; Mon, 2 Jun 2008 12:47:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by developer.postgresql.org (Postfix) with ESMTP id 5CEEB2E007B for ; Mon, 2 Jun 2008 12:46:58 -0300 (ADT) Received: by yx-out-2324.google.com with SMTP id 8so73656yxb.73 for ; Mon, 02 Jun 2008 08:46:57 -0700 (PDT) Received: by 10.151.106.4 with SMTP id i4mr6581182ybm.119.1212421617821; Mon, 02 Jun 2008 08:46:57 -0700 (PDT) Received: by 10.150.144.11 with HTTP; Mon, 2 Jun 2008 08:46:57 -0700 (PDT) Message-ID: <937d27e10806020846i5e4263d9sf521e74614049018@mail.gmail.com> Date: Mon, 2 Jun 2008 16:46:57 +0100 From: "Dave Page" To: "Joshua D. Drake" Subject: Re: RFC: Product directory Cc: "David Fetter" , w^3 In-Reply-To: <484411B4.4020801@commandprompt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <937d27e10806020130l418d1730o84de8773f1f182f5@mail.gmail.com> <20080602113349.GA8921@fetter.org> <937d27e10806020458o68717cd7sb7e0424338ff5d19@mail.gmail.com> <484411B4.4020801@commandprompt.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/7 X-Sequence-Number: 15234 On Mon, Jun 2, 2008 at 4:28 PM, Joshua D. Drake wrote: >> Agreed but a) we already display that data and b) it's useful to give >> users a ballpark figure, even if something like "$99.99US as at >> 15/12/2007" > > I have to go with fetter here. Pricing is not our concern. I actually feel quite strongly about that one - it's not *our* concern, but it is the concern of the users. There's nothing worse than researching a product, and eventually finding out after trawling the website for half an hour that it's way too expensive. As an end-user I always wanted to see a ballpark figure up front. >> Possibly. Makes the coding & management a little more tricky though. >> If we were to do that perhaps it should be part of a larger project to >> have a directory of vendors/publishers etc for news, events, services >> and products. > > Yeah I mentioned this in my previous post. Publisher really needs to be > pushed out. There is entirely too much redundant information that can be > accumulated. OK so the difficulty here/previously is that you are essentially saying I need to write a publisher management system and a product management system, and update sponsors, news, events, services etc to use that data as well. Nice in theory, but not something I have time to do. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com