Message-ID: <408FF587.7040501@pixar.com>
Date: Wed, 28 Apr 2004 11:18:47 -0700
From: Mark Harrison <mh@pixar.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040316
MIME-Version: 1.0
To: Alexey Borzov <borz_off@cs.msu.su>
Cc: Tim Conrad <tim@timconrad.org>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>,
	PostgreSQL advocacy <pgsql-advocacy@postgresql.org>
Subject: Re: [HACKERS] What can we learn from MySQL?
References: <200404262213.44601.jm@poure.com>
	<200404262041.i3QKfZs28845@candle.pha.pa.us>
	<20040427152753.GA34713@external.timconrad.org>
	<408E825C.10209@cs.msu.su>
	<20040427160711.GA67934@external.timconrad.org>
	<408E9DC1.9030105@cs.msu.su>
In-Reply-To: <408E9DC1.9030105@cs.msu.su>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Alexey Borzov wrote:
>> I realize this.  I also realize that having a nicely defined roadmap 
>> would
>> give Postgres a hands up in this category. 
> 
> 
> A hands up in *what* category? In bragging?

In telling your boss, "I think we should use Postgresql."

It's likely he's not stupid, and it's reasonable for him
to say "since I'm tying my own success to this software, I want
to have some indication as to where this software is going to
go."

Something like Josh Berkus' table of features would be very nice.

(I've worked with sales teams at my various former employers, and
the best things you can provide them are documents (feature descriptions,
competitive analyses, white papers, etc) that your customer contact can
use as the basis for his own justification to buy your product.
All of this can be summarized as "make it easy for people to help you.")

Cheers,
Mark

-- 
Mark Harrison
Pixar Animation Studios