Re: PostgreSQL mission statement?

Mark kirkwood <markir(at)slingshot(dot)co(dot)nz> writes:

> On Fri, 2002-05-03 at 04:25, mlw wrote:
>
> >
> > IMHO, if we can come up with a strong, positive statement, it
> > would help MBA trained CIOs and CTOs choose PostgreSQL. To them,
> > it will show a professional minded development group, it will be
> > recognizable to them.
>
> I am not so sure about that -
>
> In my experience the things that those guys use to decide on
> products are :
>
> 1) reference sites
> 2) official support
>
> (and they like to pay for a product 'cause they are used to doing
> it...but lets not go there...)
>
> Personally I find the lack of "business-speak" things (like mission
> statements) refeshing, and I see it as part of the "values" that
> differentiate open source / community based products from commercial
> ones.
>
> just my NZ4c (=US2c)
>
> Mark

As a developer and systems administrator my favorite thing about
PostgreSQL is the fact that I can get the straight dope on what works
and what doesn't. The PostgreSQL developers are quite candid, and are
more than willing to tell you which bits of PostgreSQL are dicey.
That's a huge bonus to someone creating and maintaining an
application.

However, it's not exactly the sort of salesmanship that my boss is
looking for.

Jason