public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Joshua D. Drake <[email protected]>
Cc: David Fetter <[email protected]>
Cc: w^3 <[email protected]>
Subject: Re: RFC: Product directory
Date: Mon, 2 Jun 2008 16:46:57 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Mon, Jun 2, 2008 at 4:28 PM, Joshua D. Drake <[email protected]> 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

view thread (16+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: RFC: Product directory
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox