Re: Change the name - Mailing list pgsql-advocacy

Greg Sabino Mullane wrote:
>
> I made a
> quick wiki page. Pleae let Neil or myself know if anyone needs editing privs:
>
> http://developer.postgresql.org/index.php/Postgres

I'm happy to add them myself if you wanted to add naming privs; or
I can just email them here if you guys want to choose which ones to add.


Some more pros and cons for that page .. mostly from earlier in the thread.

[More] Pros for changing the name to "Postgres" * Some friendly companies already using this term would benefit.

[More] Cons for changing the name to "Postgres" * Some friendly companies using PostgreSQL term would lose benefits
orhave to rephrase their taglines or other references to PostgreSQL. 

Perhaps also add a section

"Things that may need to be changed if the name is not changed"* Make "Postgre" an officially acceptable short form
becauseit's the  obvious short form of PostgreSQL; which will prevent some of the  abuse of new members, users, and
customersof the product.* or, Fund a marketing campaign to educate the world that  we're not Postgre.* Rename paths and
filenamesand processes from postgres to postgresql.* Update paths on website that use "pgsql" instead of "PostgreSQL".*
Producenew swag as the old inventory is used up.* Make links use PostgreSQL.org instead of postgresql.org to
re-enforcethe brand.* Update the mailing list names from "pgsql-advocacy"  to "postgresql-advocacy" 
Obviously some of these  don't have to change here any more
than they would have to with the name Postgres; but if people
add them to the list of work for the new name, seems they should
be there for the old name too.

Perhaps also add a section

"Alternatives to changing to Postgres"
* Moving to PostgresQL - which keeps domain names, etc but  encourages the preferred short form.* Approving of
"Postgre".*A marketing campaign to educate the world against "Postgre" 

Add to external links:
* http://svr5.postgresql.org/pgsql-novice/2006-07/msg00063.php  Which has the interesting quote:  "Arguably, the 1996
decisionto call it PostgreSQL instead  of reverting to plain Postgres was the single worst mistake  this project ever
made."


I also think it'd be worth adding an example that illustrates
why PostgreSQL is so awkward to people who haven't gotten years
getting numb to the term.   Perhaps comparing to EnterpriSQL
would help illustrate this; or perhaps a sentence like"PerhapSQL Josh BerkuSQL iSQL going to say yeSQL and blesSQL this
projectif he seeSQL how new userSQL parse wordSQL with mixed case." 
would server better.