Re: Change the name

Ron,

> The total amount of _OPTIONAL_ and downright
> unnecessary work is immense:
<snip>
> But none of those need to happen so long as everyone
> agrees PostgreSQL is still accepted.  And arguably
> none of these should ever happen.

This puts us in the worst of all possible worlds: one in which some things
are labelled "Postgres" and somethings are labelled "PostgreSQL" and
nobody can count on, from release to release, what is what.  If you think
we have project name problems *now*, that's nothing compared to the kind
of total branding chaos you're proposing.

Issues not addressed above:
path names
file names
package names
server strings (which all have to be translated into 11 languages)
re-designing marketing materials
links from external sites
contacting packagers, commercial distributors and downstream projects so
they all know about the name change
graphics redesign

I agree with the idea that Postgres and Postgre ought to be officially
blessed "abbreviations" or "nicknames".  I don't agree that the project
should have different names depending on which page of the web site you're
looking at.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco