Re: The naming question (Postgres vs PostgreSQL)

Hi,

I don't agree on some things people opposing the name change
continue saying.

Stefan, you just mentioned two of them, and I can't
resist... ;)


> it might be a better name(or not) but a switch like that involves much
> more than simply saying "oh this is our new name" - I'm fairly convinced
> that playing games with our name will hurt us (and the active community
> at a large) for a while in a period where postgresql is gaining insight
> into a lot of places that it had not before and I'm not sure that
> changing names after years of years of having another will give
> confidence to (management style) people.

This would be a good argument against changing name to something
completeley different - say - "SushiDB".

Going from PostgreSQL -> Postgres, you wouldn't loose any brand
recognization, would you?

What about "Oracle9i" -> "Oracle Database 10g" then?


> well those people invested a lot of personal time and money into all
> that stuff (and I'm sure all that attended say pgday.it will fully
> agree) and either way you phrase it it will cost them money and time to
> come up with replacement merchandising.
> This is time and money invested from people on there own pocket not
> employed or supported by one of the dedicated postgresql companies or
> being payed to work on postgresql full time so you are actually asking a
> lot for here.

Replacement merchandising?
There's no sense *throwing away* PostgreSQL T-shirts and stuff if the
name changes. 90% of people who get them do it in support of the project and
will get them anyway.

I will personally buy 10 T-Shirts from Gabriele if the name changes ;)


Bye,
Chris.