Re: PostgreSQL mission statement?

From: mlw <markw(at)mohawksoft(dot)com>
To: Jim Mercer <jim(at)reptiles(dot)org>
Cc: jm(dot)poure(at)freesurf(dot)fr, David Terrell <dbt(at)meat(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PostgreSQL mission statement?
Date: 2002-05-02 12:43:04
Message-ID: 3CD13458.14BEF912@mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Mercer wrote:
>
> On Thu, May 02, 2002 at 08:15:15AM -0400, mlw wrote:
> > Jean-Michel POURE wrote:
> > > Le Jeudi 2 Mai 2002 01:59, David Terrell a écrit :
> > > > "Provide a really good database and have fun doing it"
> > >
> > > PostgreSQL Community is commited to providing Humanity with the best
> > > multi-purpose, reliable, open-source and free database system.
> >
> >
> > The PostgreSQL community is committed to creating and maintaining the best,
> > most reliable, open-source multi-purpose standards based database, and with
> > it, promote free and open source software world wide.
> >
> > Who's that? Anyone disagree?
>
> why does it have to be THE BEST ? that is insulting to the other projects
> like MySQL which while "competitors" are also a valid and useful benchmark
> for features, performance and keeping the postgresql community on its
> collective toes.

This is interesting, a mission statement isn't necessarily about "what is" but
about what we "want to do," what it is that we "intend to do," i.e. "our
mission." It is vital that a mission statement contain the superlatives.
Mediocrity has no place here.

I don't know about you, but I want PostgreSQL to be the best, be THE most
reliable. Omitting "best" or "most" from the statement means that we should all
just give up now, because PostgreSQL is pretty damn good already.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nigel J. Andrews 2002-05-02 12:43:39 Re: PostgreSQL mission statement?
Previous Message Louis-David Mitterrand 2002-05-02 12:38:32 DROP TABLE hangs because of same table foreign key