Re: Change the name

> ------- Original Message -------
> From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
> To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
> Sent: 02/09/07, 16:18:47
> Subject: Re: [pgsql-advocacy] The naming question (Postgres vs PostgreSQL)
>
> So my question really is, is everyone out there who does not want to
> change to Postgres now willing to officially accept Postgre as well?
>

Isn't that akin to you declaring that Jan with a hard J is an acceptable way for people to refer to you, despite the fact that you're a 6' 3" European bloke, and not a woman call Janet?

I think we should change to Postgres or do nothing. Postgre is absolutely horrendous imho.

/D

Dave Page wrote:
>
> Isn't that akin to you declaring that Jan with a hard J is an acceptable way for people to refer to you, despite the fact that you're a 6' 3" European bloke, and not a woman call Janet?
>
> I think we should change to Postgres or do nothing. Postgre is absolutely horrendous imho.

Although I don't want to change the name. I agree that Postre is pretty
horrendous.

Sincerely,

Joshua D. Drake

>
> /D
>

On 9/2/2007 11:33 AM, Dave Page wrote:
>
>> ------- Original Message -------
>> From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
>> To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
>> Sent: 02/09/07, 16:18:47
>> Subject: Re: [pgsql-advocacy] The naming question (Postgres vs PostgreSQL)
>>
>> So my question really is, is everyone out there who does not want to
>> change to Postgres now willing to officially accept Postgre as well?
>>
>
> Isn't that akin to you declaring that Jan with a hard J is an acceptable way for people to refer to you, despite the fact that you're a 6' 3" European bloke, and not a woman call Janet?

Nah, that is just laziness on my side. And I'm only a 6'1'' european
bloke. Maybe I should change the spelling to Yann when I apply for
citizenship?

>
> I think we should change to Postgres or do nothing. Postgre is absolutely horrendous imho.

The point is that we already DID change the name to Postgre. We just
didn't realize it back then and some don't want to realize it even now.

Look at the IRC channels, the mailing lists and all sorts of blogs and
articles published. If you're confident about your stomach, google for
"Postgre SQL" (with the double quotes). There are tons and tons of
references to "Postgre-SQL" and "Postgre SQL". You even see Marc using
"Postgre SQL" on the first result page (okay, it was a forwarded email
and he might not have noticed - but precious as an example anyway).

People back then might not, but today most of them do recognize SQL as
the abbreviation for Structured Query Language. Or at least it is
something they do recognize and interpret separate from the rest of the
word. They remove the acronym and logically come to Postgre as the base
name of our project. We will never be able to stop that unless we remove
the root cause of it, the letters SQL attached to the name Postgre.

We don't have the choice of doing nothing, because not changing back to
Postgres means you have to accept Postgre. And that's not exactly
"nothing" to me. It turns my guts upside down, but it is what seems
logically our name, so it has every right to be officially accepted.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

Jan Wieck wrote:
> We don't have the choice of doing nothing, because not changing back to
> Postgres means you have to accept Postgre. And that's not exactly
> "nothing" to me. It turns my guts upside down, but it is what seems
> logically our name, so it has every right to be officially accepted.

If we do nothing and "Postgre" continues to become a defacto standard
name, people could add a QL feature so "Postgre's QL" could justify
the current pronunciation and domain names. :-)

Jan Wieck wrote:
> We don't have the choice of doing nothing, because not changing back to
> Postgres means you have to accept Postgre. And that's not exactly
> "nothing" to me. It turns my guts upside down, but it is what seems
> logically our name, so it has every right to be officially accepted.

If we do nothing and "Postgre" continues to become a defacto standard
name, people could add a QL feature so "Postgre's QL" could justify
the current pronunciation and domain names. :-)

Jan Wieck wrote:
> Nah, that is just laziness on my side. And I'm only a 6'1'' european
> bloke.

Oh? you look taller in real life. Or maybe I'm shrinking.

> Maybe I should change the spelling to Yann when I apply for
> citizenship?

:-)

> We don't have the choice of doing nothing, because not changing back to
> Postgres means you have to accept Postgre. And that's not exactly
> "nothing" to me. It turns my guts upside down, but it is what seems
> logically our name, so it has every right to be officially accepted.

Damn you and your logic!! You're right of course, but it doesn't mean I
have to like it :-)

/D

Joshua D. Drake wrote:
> Dave Page wrote:
> >
> > Isn't that akin to you declaring that Jan with a hard J is an acceptable way for people to refer to you, despite the fact that you're a 6' 3" European bloke, and not a woman call Janet?
> >
> > I think we should change to Postgres or do nothing. Postgre is absolutely horrendous imho.
>
> Although I don't want to change the name. I agree that Postre is pretty
> horrendous.

Oh, and that e needs an accent, Postgre' (Post-gray)

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Oh, one more thing. I think it is illustrative to look at the areas we
_didn't_ change when we went from "Postgres95" to "PostgreSQL": the
super-user name and the backend binary name. Those were kept as
"postgres", and I remember no questions about why those are "postgres".

What that means to me is that "Postgres" was easily associates with
"PostgreSQL", and if we change our name to "Postgres", "PostgreSQL" will
still be easily associates with the project, so perhaps we don't need to
change the name of the download binaries or postgresql.conf.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Bruce Momjian escribió:
> Oh, one more thing. I think it is illustrative to look at the areas we
> _didn't_ change when we went from "Postgres95" to "PostgreSQL": the
> super-user name and the backend binary name. Those were kept as
> "postgres", and I remember no questions about why those are "postgres".

Well, that's easy: those correspond to "postgresql" truncated to 8 chars ;-)

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

I have downloaded the Advocacy email archive for August and September
and looked at all emails with the subject "naming". I read each email
and totalled the opinions of all the posters. Of course, this is not
scientific but it does represent everyone on advocacy who felt the need
to comment on the thread.

The totals are 15 for no change and 30 for a change to "Postgres". The
number who favored "PostgresQL" were minimal. If you have additions or
corrections, please email me privately and I will repost the list.

---------------------------------------------------------------------------

PostgreSQL (15 total)
----------
Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Brian Hurt <bhurt(at)janestcapital(dot)com>
Dawid Kuroczko <qnex42(at)gmail(dot)com>
Gevik Babakhani <pgdev(at)xs4all(dot)nl>
Gevik Babakhani <pgdev(at)xs4all(dot)nl>
Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Josh Berkus <josh(at)agliodbs(dot)com>
Joshua D. Drake <jd(at)commandprompt(dot)com>
Magnus Hagander <magnus(at)hagander(dot)net>
Marc G. Fournier <scrappy(at)hub(dot)org>
Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Tatsuo Ishii <ishii(at)postgresql(dot)org>

Postgres (30 total)
--------
Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Andy Astor <andy(dot)astor(at)enterprisedb(dot)com>
Bob Zurek <bob(dot)zurek(at)enterprisedb(dot)com>
Bruce Momjian <bruce(at)momjian(dot)us>
Chris Mair <chris(at)1006(dot)org>
Christopher Petrilli <petrilli(at)gmail(dot)com>
Dave Page <dpage(at)postgresql(dot)org>
Derek Rodner <derek(dot)rodner(at)enterprisedb(dot)com>
Federico <rotellaro(at)gmail(dot)com>
Gabriele Bartolini <gabriele(dot)bartolini(at)gmail(dot)com>
Gavin M. Roy <gmr(at)myyearbook(dot)com>
Greg Sabino Mullane <greg(at)turnstep(dot)com>
Greg Sabino Mullane <greg(at)turnstep(dot)com>
Greg Smith <gsmith(at)gregsmith(dot)com>
Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>
Jan Wieck <JanWieck(at)Yahoo(dot)com>
Jim Nasby (Decibel!) <decibel(at)decibel(dot)org>
Joe Conway <mail(at)joeconway(dot)com>
Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com>
Liam O'Duibhir <liamod(at)fast(dot)fujitsu(dot)com(dot)au>
Luke Lonergan <LLonergan(at)greenplum(dot)com>
Ned Lilly <ned(at)nedscape(dot)com>
Neil Conway <neilc(at)samurai(dot)com>
Peter Eisentraut <peter_e(at)gmx(dot)net>
Raymond O'Donnell <rod(at)iol(dot)ie>
Robert Bernier <robert(dot)bernier5(at)sympatico(dot)ca>
Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Roth, Gabrielle <gabrielle(dot)roth(at)xo(dot)com>
Shane Ambler <pgsql(at)Sheeky(dot)Biz>

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Mon, Sep 03, 2007 at 01:20:38PM -0400, Bruce Momjian wrote:
> I have downloaded the Advocacy email archive for August and September
> and looked at all emails with the subject "naming". I read each email
> and totalled the opinions of all the posters. Of course, this is not
> scientific but it does represent everyone on advocacy who felt the need
> to comment on the thread.
>
> The totals are 15 for no change and 30 for a change to "Postgres". The
> number who favored "PostgresQL" were minimal. If you have additions or
> corrections, please email me privately and I will repost the list.

+1 for changing to Postgres, and including mine, that's 12 unique
opinions for keeping PostgreSQL, 29 for changing it.

Cheers,
David.
>
> ---------------------------------------------------------------------------
>
>
> PostgreSQL (15 total)
> ----------
> Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
> Brian Hurt <bhurt(at)janestcapital(dot)com>
> Dawid Kuroczko <qnex42(at)gmail(dot)com>
> Gevik Babakhani <pgdev(at)xs4all(dot)nl>
> Gevik Babakhani <pgdev(at)xs4all(dot)nl>
> Guillaume Lelarge <guillaume(at)lelarge(dot)info>
> Josh Berkus <josh(at)agliodbs(dot)com>
> Joshua D. Drake <jd(at)commandprompt(dot)com>
> Magnus Hagander <magnus(at)hagander(dot)net>
> Marc G. Fournier <scrappy(at)hub(dot)org>
> Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
> Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
> Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
> Tatsuo Ishii <ishii(at)postgresql(dot)org>
>
>
> Postgres (30 total)
> --------
> Alvaro Herrera <alvherre(at)commandprompt(dot)com>
> Andy Astor <andy(dot)astor(at)enterprisedb(dot)com>
> Bob Zurek <bob(dot)zurek(at)enterprisedb(dot)com>
> Bruce Momjian <bruce(at)momjian(dot)us>
> Chris Mair <chris(at)1006(dot)org>
> Christopher Petrilli <petrilli(at)gmail(dot)com>
> Dave Page <dpage(at)postgresql(dot)org>
> Derek Rodner <derek(dot)rodner(at)enterprisedb(dot)com>
> Federico <rotellaro(at)gmail(dot)com>
> Gabriele Bartolini <gabriele(dot)bartolini(at)gmail(dot)com>
> Gavin M. Roy <gmr(at)myyearbook(dot)com>
> Greg Sabino Mullane <greg(at)turnstep(dot)com>
> Greg Sabino Mullane <greg(at)turnstep(dot)com>
> Greg Smith <gsmith(at)gregsmith(dot)com>
> Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>
> Jan Wieck <JanWieck(at)Yahoo(dot)com>
> Jim Nasby (Decibel!) <decibel(at)decibel(dot)org>
> Joe Conway <mail(at)joeconway(dot)com>
> Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com>
> Liam O'Duibhir <liamod(at)fast(dot)fujitsu(dot)com(dot)au>
> Luke Lonergan <LLonergan(at)greenplum(dot)com>
> Ned Lilly <ned(at)nedscape(dot)com>
> Neil Conway <neilc(at)samurai(dot)com>
> Peter Eisentraut <peter_e(at)gmx(dot)net>
> Raymond O'Donnell <rod(at)iol(dot)ie>
> Robert Bernier <robert(dot)bernier5(at)sympatico(dot)ca>
> Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
> Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
> Roth, Gabrielle <gabrielle(dot)roth(at)xo(dot)com>
> Shane Ambler <pgsql(at)Sheeky(dot)Biz>
>
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://www.enterprisedb.com
>
> + If your life is a hard drive, Christ can be your backup. +
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter

Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate

Bruce Momjian wrote:
> I have downloaded the Advocacy email archive for August and September
> and looked at all emails with the subject "naming". I read each email
> and totalled the opinions of all the posters. Of course, this is not
> scientific but it does represent everyone on advocacy who felt the need
> to comment on the thread.
>
> The totals are 15 for no change and 30 for a change to "Postgres". The
> number who favored "PostgresQL" were minimal. If you have additions or
> corrections, please email me privately and I will repost the list.

Oops, I had a few duplicates in that list. Here is the right one.
(Seems I need to use a database with unique constraints.)

This shows 70% in favor of a change to "Postgres", so far.

Of course, this is not a vote on _how_ to implement the change.

---------------------------------------------------------------------------

PostgreSQL (12 total)
----------
Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
Brian Hurt <bhurt(at)janestcapital(dot)com>
Dawid Kuroczko <qnex42(at)gmail(dot)com>
Gevik Babakhani <pgdev(at)xs4all(dot)nl>
Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Josh Berkus <josh(at)agliodbs(dot)com>
Joshua D. Drake <jd(at)commandprompt(dot)com>
Magnus Hagander <magnus(at)hagander(dot)net>
Marc G. Fournier <scrappy(at)hub(dot)org>
Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Tatsuo Ishii <ishii(at)postgresql(dot)org>

Postgres (28 total)
--------
Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Andy Astor <andy(dot)astor(at)enterprisedb(dot)com>
Bob Zurek <bob(dot)zurek(at)enterprisedb(dot)com>
Bruce Momjian <bruce(at)momjian(dot)us>
Chris Mair <chris(at)1006(dot)org>
Christopher Petrilli <petrilli(at)gmail(dot)com>
Dave Page <dpage(at)postgresql(dot)org>
Derek Rodner <derek(dot)rodner(at)enterprisedb(dot)com>
Federico <rotellaro(at)gmail(dot)com>
Gabriele Bartolini <gabriele(dot)bartolini(at)gmail(dot)com>
Gavin M. Roy <gmr(at)myyearbook(dot)com>
Greg Sabino Mullane <greg(at)turnstep(dot)com>
Greg Smith <gsmith(at)gregsmith(dot)com>
Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>
Jan Wieck <JanWieck(at)Yahoo(dot)com>
Jim Nasby (Decibel!) <decibel(at)decibel(dot)org>
Joe Conway <mail(at)joeconway(dot)com>
Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com>
Liam O'Duibhir <liamod(at)fast(dot)fujitsu(dot)com(dot)au>
Luke Lonergan <LLonergan(at)greenplum(dot)com>
Ned Lilly <ned(at)nedscape(dot)com>
Neil Conway <neilc(at)samurai(dot)com>
Peter Eisentraut <peter_e(at)gmx(dot)net>
Raymond O'Donnell <rod(at)iol(dot)ie>
Robert Bernier <robert(dot)bernier5(at)sympatico(dot)ca>
Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Roth, Gabrielle <gabrielle(dot)roth(at)xo(dot)com>
Shane Ambler <pgsql(at)Sheeky(dot)Biz>

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Monday, September 03, 2007 12:39:28 -0400 Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:

> Bruce Momjian escribió:
>> Oh, one more thing. I think it is illustrative to look at the areas we
>> _didn't_ change when we went from "Postgres95" to "PostgreSQL": the
>> super-user name and the backend binary name. Those were kept as
>> "postgres", and I remember no questions about why those are "postgres".
>
> Well, that's easy: those correspond to "postgresql" truncated to 8 chars ;-)

Actually, on FreeBSD, super user is pgsql, not postgres ...

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFG3EmD4QvfyHIvDvMRAo/6AJ4qjK1z9y2R1wkMF4YxmsW8GJ3AEwCdEBb1
42zSH9JZkvsMo+CO+2YASzc=
=oYvH
-----END PGP SIGNATURE-----

On Mon, Sep 03, 2007 at 01:30:54PM -0400, Bruce Momjian wrote:
> Bruce Momjian wrote:
> > I have downloaded the Advocacy email archive for August and September
> > and looked at all emails with the subject "naming". I read each email
> > and totalled the opinions of all the posters. Of course, this is not
> > scientific but it does represent everyone on advocacy who felt the need
> > to comment on the thread.
> >
> > The totals are 15 for no change and 30 for a change to "Postgres". The
> > number who favored "PostgresQL" were minimal. If you have additions or
> > corrections, please email me privately and I will repost the list.
>
> Oops, I had a few duplicates in that list. Here is the right one.
> (Seems I need to use a database with unique constraints.)
>
> This shows 70% in favor of a change to "Postgres", so far.
>
> Of course, this is not a vote on _how_ to implement the change.

I'm going to go out on a limb here and ask... can we now at least agree
to change the name to Postgres, stop debating that point, and start
thinking about *how* to change the name?
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

Decibel! wrote:
-- Start of PGP signed section.
> On Mon, Sep 03, 2007 at 01:30:54PM -0400, Bruce Momjian wrote:
> > Bruce Momjian wrote:
> > > I have downloaded the Advocacy email archive for August and September
> > > and looked at all emails with the subject "naming". I read each email
> > > and totalled the opinions of all the posters. Of course, this is not
> > > scientific but it does represent everyone on advocacy who felt the need
> > > to comment on the thread.
> > >
> > > The totals are 15 for no change and 30 for a change to "Postgres". The
> > > number who favored "PostgresQL" were minimal. If you have additions or
> > > corrections, please email me privately and I will repost the list.
> >
> > Oops, I had a few duplicates in that list. Here is the right one.
> > (Seems I need to use a database with unique constraints.)
> >
> > This shows 70% in favor of a change to "Postgres", so far.
> >
> > Of course, this is not a vote on _how_ to implement the change.
>
> I'm going to go out on a limb here and ask... can we now at least agree
> to change the name to Postgres, stop debating that point, and start
> thinking about *how* to change the name?

Yea, I think that is a limb. People have thrown all sort of ideas on
why/why not to make the change, so I think we need to give more time for
that.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Mon, Sep 03, 2007 at 02:50:58PM -0300, Marc G. Fournier wrote:
> > Bruce Momjian escribi??:
> >> Oh, one more thing. I think it is illustrative to look at the areas we
> >> _didn't_ change when we went from "Postgres95" to "PostgreSQL": the
> >> super-user name and the backend binary name. Those were kept as
> >> "postgres", and I remember no questions about why those are "postgres".
> >
> > Well, that's easy: those correspond to "postgresql" truncated to 8 chars ;-)
>
> Actually, on FreeBSD, super user is pgsql, not postgres ...

Speaking of which... is the maintainer someone in our community? It's
always drove me nuts that it's pgsql in FreeBSD, because if you try and
move the dump anywhere else it's a huge PITA. And you can't do a simple
search and replace because of plpgsql.
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

On Mon, Sep 03, 2007 at 01:59:30PM -0400, Bruce Momjian wrote:
> Decibel! wrote:
> -- Start of PGP signed section.
> > On Mon, Sep 03, 2007 at 01:30:54PM -0400, Bruce Momjian wrote:
> > > Bruce Momjian wrote:
> > > > I have downloaded the Advocacy email archive for August and September
> > > > and looked at all emails with the subject "naming". I read each email
> > > > and totalled the opinions of all the posters. Of course, this is not
> > > > scientific but it does represent everyone on advocacy who felt the need
> > > > to comment on the thread.
> > > >
> > > > The totals are 15 for no change and 30 for a change to "Postgres". The
> > > > number who favored "PostgresQL" were minimal. If you have additions or
> > > > corrections, please email me privately and I will repost the list.
> > >
> > > Oops, I had a few duplicates in that list. Here is the right one.
> > > (Seems I need to use a database with unique constraints.)
> > >
> > > This shows 70% in favor of a change to "Postgres", so far.
> > >
> > > Of course, this is not a vote on _how_ to implement the change.
> >
> > I'm going to go out on a limb here and ask... can we now at least agree
> > to change the name to Postgres, stop debating that point, and start
> > thinking about *how* to change the name?
>
> Yea, I think that is a limb. People have thrown all sort of ideas on
> why/why not to make the change, so I think we need to give more time for
> that.

Ok, well, at the least then we really need to focus discussion on
"Should we change the name" and quit worrying about how we'll actually
do it.
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Monday, September 03, 2007 13:20:39 -0500 Decibel! <decibel(at)decibel(dot)org>
wrote:

> Ok, well, at the least then we really need to focus discussion on
> "Should we change the name" and quit worrying about how we'll actually
> do it.

The other option is that EDB creates a Postgres community, GPLs the code and
puts it all into Subversion, and run it in parallel to the PostgreSQL community
... then everyone that wants to keep the status quo can stick around and
continue marketing and pushing PostgreSQL, and those that "want change" can
just move over to that new project ...

Now, *that* would be an interesting experiment ...

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFG3FJL4QvfyHIvDvMRAh0AAKCiy/aKN/RtpiLJjb4l0bCtxyU4cgCght0h
8/T2YI+Gr9ad2F+iHl1DrqQ=
=KfKA
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Monday, September 03, 2007 13:19:38 -0500 Decibel! <decibel(at)decibel(dot)org>
wrote:

> Speaking of which... is the maintainer someone in our community? It's
> always drove me nuts that it's pgsql in FreeBSD, because if you try and
> move the dump anywhere else it's a huge PITA. And you can't do a simple
> search and replace because of plpgsql.

We just do a 'createuser' for postgres as superuser in those few times it
happens ... *shrug* Its a simple command, comes with all installs of
postgresql :)

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFG3FMh4QvfyHIvDvMRAuJ6AKCnAI64KceFbMFeVnEV80UgsU32AwCgwiKt
HoRs9RYGc7o24J3EUCnZm7E=
=uJl0
-----END PGP SIGNATURE-----

Hi,

On Mon, 2007-09-03 at 13:20 -0400, Bruce Momjian wrote:
> PostgreSQL (15 total)

Make it +1 for me.

Cheers,
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/

Hi,

On Mon, 2007-09-03 at 13:20 -0400, Bruce Momjian wrote:
> The totals are 15 for no change and 30 for a change to "Postgres".

So ~ 45 votes among hundreds of subscribers? Even this low number proves
that this discussion is useless, IMHO. -- let's spend our time for
better things. Will this change make PostgreSQL faster? Or will it add a
big major feature that will attract thousands of new users? I don't
think so.

Regards,
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> This shows 70% in favor of a change to "Postgres", so far.

Of course, that's 70% of -advocacy, which by nature is going to be the
subset of the community most interested in this change and least
interested in the ensuing costs.

regards, tom lane

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > This shows 70% in favor of a change to "Postgres", so far.
>
> Of course, that's 70% of -advocacy, which by nature is going to be the
> subset of the community most interested in this change and least
> interested in the ensuing costs.

It seems there were a significant number of people with swag who will
pay the cost somehow.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On 9/3/07, Devrim GÜNDÜZ <devrim(at)commandprompt(dot)com> wrote:
> So ~ 45 votes among hundreds of subscribers? Even this low number proves
> that this discussion is useless, IMHO. -- let's spend our time for
> better things. Will this change make PostgreSQL faster? Or will it add a
> big major feature that will attract thousands of new users? I don't
> think so.

On the other hand, if advocacy continues to stumble, perhaps there
will be no one to give a damn about, "big major feature X".

I agree, there is a lot of discussion here that may lead to nowhere.
Nevertheless, it's a discussion that needs to happen sooner-or-later.

--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

Tom,

With all respect, I think the -advocacy group is *very* interested in the
ensuing costs, and is willing to pitch in.

As I see it, -advocacy is the group most interested in the public face of
PostgreSQL, and is very appropriate for this kind of debate.

andy

On 9/3/07 3:43 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> This shows 70% in favor of a change to "Postgres", so far.
>
> Of course, that's 70% of -advocacy, which by nature is going to be the
> subset of the community most interested in this change and least
> interested in the ensuing costs.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

Devrim GÜNDÜZ wrote:
> Hi,
>
> On Mon, 2007-09-03 at 13:20 -0400, Bruce Momjian wrote:
>> The totals are 15 for no change and 30 for a change to "Postgres".
>
> So ~ 45 votes among hundreds of subscribers? Even this low number proves
> that this discussion is useless, IMHO. -- let's spend our time for
> better things. Will this change make PostgreSQL faster? Or will it add a
> big major feature that will attract thousands of new users? I don't
> think so.

On that basis we'd never be able to make *any* decisions.

/D

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> This shows 70% in favor of a change to "Postgres", so far.
>
> Of course, that's 70% of -advocacy, which by nature is going to be the
> subset of the community most interested in this change and least
> interested in the ensuing costs.

Eh? They're the very people who spend time raising cash and designing,
sourcing, purchasing and selling the swag that will be affected.

/D

Them who vote are them that make the decisions for them that don't. That's
how it works. The fact that <50% of the American population vote for its
president (with apologies for the US-centric view) doesn't make the vote
invalid or the group voting inappropriate.

I suggest we all just sit back and respect each others' views and opinions,
rather than trashing the very idea of the discussion.

Andy

On 9/3/07 3:39 PM, "Devrim GÜNDÜZ" <devrim(at)CommandPrompt(dot)com> wrote:

> Hi,
>
> On Mon, 2007-09-03 at 13:20 -0400, Bruce Momjian wrote:
>> The totals are 15 for no change and 30 for a change to "Postgres".
>
> So ~ 45 votes among hundreds of subscribers? Even this low number proves
> that this discussion is useless, IMHO. -- let's spend our time for
> better things. Will this change make PostgreSQL faster? Or will it add a
> big major feature that will attract thousands of new users? I don't
> think so.
>
> Regards,

On 9/3/07, Marc G. Fournier <scrappy(at)hub(dot)org> wrote:
> The other option is that EDB creates a Postgres community, GPLs the code and
> puts it all into Subversion, and run it in parallel to the PostgreSQL community
> ... then everyone that wants to keep the status quo can stick around and
> continue marketing and pushing PostgreSQL, and those that "want change" can
> just move over to that new project ...

Was that a joke or have you gone completely off the deep-end?!?

--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> Of course, that's 70% of -advocacy, which by nature is going to be the
>> subset of the community most interested in this change and least
>> interested in the ensuing costs.

> It seems there were a significant number of people with swag who will
> pay the cost somehow.

That's adopting exactly the view I thought it was, that only directly
marketing-related costs matter. Again, this seems to be considering
only advocacy-related concerns.

I'll confine my reply to one point: do you have any idea what will
happen if I try to change the default PGDATA location on Red Hat
from /var/lib/pgsql to something else?

regards, tom lane

On 9/3/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> That's adopting exactly the view I thought it was, that only directly
> marketing-related costs matter. Again, this seems to be considering
> only advocacy-related concerns.

No.

> I'll confine my reply to one point: do you have any idea what will
> happen if I try to change the default PGDATA location on Red Hat
> from /var/lib/pgsql to something else?

Um, I thought it was already briefly discussed that directories and
config file names could and should remain the same?

--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Of course, that's 70% of -advocacy, which by nature is going to be the
> >> subset of the community most interested in this change and least
> >> interested in the ensuing costs.
>
> > It seems there were a significant number of people with swag who will
> > pay the cost somehow.
>
> That's adopting exactly the view I thought it was, that only directly
> marketing-related costs matter. Again, this seems to be considering
> only advocacy-related concerns.
>
> I'll confine my reply to one point: do you have any idea what will
> happen if I try to change the default PGDATA location on Red Hat
> from /var/lib/pgsql to something else?

As I said about the username and binary name still being "postgres", I
would think PostgreSQL (pgsql) would be fine to remain unchanged in many
places.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

I don't follow your logic. Most people on here earn their living with
Postgres in one way or another, and a large percentage of the vocal
people on this list are very active in promotion. Who would see the
direct cost more than those who are spending the money and time in
pushing higher adoption rates and advocating to attract users? In
addition, who better to have this conversation than those who have an
active interest in the future marketing direction of the application?

Gavin

On 9/3/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > This shows 70% in favor of a change to "Postgres", so far.
>
> Of course, that's 70% of -advocacy, which by nature is going to be the
> subset of the community most interested in this change and least
> interested in the ensuing costs.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

This isn't an EDB push, even tough several EDB people have advocated
the change. Bringing the project up to the times, technology wise
wouldn't be a bad idea, imho. Command Prompt already maintains the
technical end of what you're proposing, though not in the interest of
carrying a parallel community, afaik.

I haven't heard anyone interested in GPL'ing the code, and EDB would
have the least to gain from a GPL fork. Your comments seem to be more
flame bait than anything else, along with the argument that FreeBSD
breaks the username standard so we shouldn't change the project name.

Gavin

On 9/3/07, Marc G. Fournier <scrappy(at)hub(dot)org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> - --On Monday, September 03, 2007 13:20:39 -0500 Decibel! <decibel(at)decibel(dot)org>
> wrote:
>
> > Ok, well, at the least then we really need to focus discussion on
> > "Should we change the name" and quit worrying about how we'll actually
> > do it.
>
> The other option is that EDB creates a Postgres community, GPLs the code and
> puts it all into Subversion, and run it in parallel to the PostgreSQL community
> ... then everyone that wants to keep the status quo can stick around and
> continue marketing and pushing PostgreSQL, and those that "want change" can
> just move over to that new project ...
>
> Now, *that* would be an interesting experiment ...
>
>
> - ----
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
> Yahoo . yscrappy Skype: hub.org ICQ . 7615664
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4 (FreeBSD)
>
> iD8DBQFG3FJL4QvfyHIvDvMRAh0AAKCiy/aKN/RtpiLJjb4l0bCtxyU4cgCght0h
> 8/T2YI+Gr9ad2F+iHl1DrqQ=
> =KfKA
> -----END PGP SIGNATURE-----
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

On 9/3/2007 11:58 AM, Bruce Momjian wrote:
> Oh, one more thing. I think it is illustrative to look at the areas we
> _didn't_ change when we went from "Postgres95" to "PostgreSQL": the
> super-user name and the backend binary name. Those were kept as
> "postgres", and I remember no questions about why those are "postgres".

More to the point, looking at our recommended upgrade strategy (use new
pg_dump against old Postmaster), wouldn't it be actually wise to somehow
encode the major version number into the installation directory? I mean
seriously, we didn't have a real problem ever, but what if some day the
new pg_dump against the old postmaster produces complete garbage ... and
the upgrade just wiped the data directory with an initdb?

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

On Mon, Sep 03, 2007 at 10:39:49PM +0300, Devrim G?ND?Z wrote:
> better things. Will this change make PostgreSQL faster? Or will it add a
> big major feature that will attract thousands of new users? I don't

Yes, it'll give us a name that's pronouncable and not confusing.
--
Decibel!, aka Jim Nasby decibel(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)

Hi,

On Mon, 2007-09-03 at 15:53 -0500, Decibel! wrote:

> On Mon, Sep 03, 2007 at 10:39:49PM +0300, Devrim G?ND?Z wrote:
> > better things. Will this change make PostgreSQL faster? Or will it
> add a
> > big major feature that will attract thousands of new users? I don't
>
> Yes, it'll give us a name that's pronouncable and not confusing.

So? :)

Cheers,
--
Devrim GÜNDÜZ
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/

I'm breaking my promise not to post in this thread, because I'm being
counted wrong.

On Mon, Sep 03, 2007 at 01:20:38PM -0400, Bruce Momjian wrote:
> PostgreSQL (15 total)
> ----------
> Andrew Sullivan <ajs(at)crankycanuck(dot)ca>

I think you have completely misunderstood my point, which is not,
"Don't change the name," but rather, "If we're going to change the
name, we need a _plan_." I don't oppose changing the name as such. I
oppose changing the name _now_, or _gradually_, or any of the other
go-small answers that have been proposed. If we want to change the
name, then we need to design the name change in the same careful way
that we would expect new features to be designed.

(This lack of nuance is why I think the poll on the EnterpriseDB web
site is a bad one: it isn't a question of a specific proposal of how
or when to change the name, but merely whether we ought to. If we're
going to do it, can we please have a poll on a serious and complete
proposal?)

A

--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
Users never remark, "Wow, this software may be buggy and hard
to use, but at least there is a lot of code underneath."
--Damien Katz

Tom Lane wrote:
>
> I'll confine my reply to one point: do you have any idea what will
> happen if I try to change the default PGDATA location on Red Hat
> from /var/lib/pgsql to something else?

This seems 100% orthogonal to the naming conversation.

Unless, perhaps Red Hat was in the middle of an
expensive migration to
/var/lib/PostgreSQL
that noone told their customers about.

If you wanted, a completely separate conversation could
be whether distros should convert various less common
short form (like pgsql) to some set of brand names - but
I think both the PostgreSQL and Postgres and even Postgre
advocates would say it's silly to rename pgsql to any
of those 3 terms.

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> This shows 70% in favor of a change to "Postgres", so far.
>
> Of course, that's 70% of -advocacy, which by nature is going to be the
> subset of the community most interested in this change and least
> interested in the ensuing costs.

I think the community that most needs to be polled are
actually external to the community. IMHO The people
most harmed by the non-intuitive name today are:

* IT Customers who have a problem with the Postgre they got
bundled with some CRM software they bought and need to
ask for help.

* Execs and sales people telling their customers that they're
selling products based on Postgre's QL.

* VC's wasting their time discussing pronunciation trivia
with startups looking for funding instead of discussing
the products and businesses of the startup.

I think -advocacy is indeed a better place than -hackers
to discuss it too. As far as I can tell, no changes
discussed would touch the actual code.
No processes renamed.
No paths renamed.
No libraries renamed.
No variables renamed.

Note also, most proposals I've seen in the discussion
include both Postgres and PostgreSQL as acceptable terms
so the only place that really really needs to change
is the FAQ, and *gradually* the web site and docs.

Andrew Sullivan wrote:
> I'm breaking my promise not to post in this thread, because I'm being
> counted wrong.
>
> On Mon, Sep 03, 2007 at 01:20:38PM -0400, Bruce Momjian wrote:
> > PostgreSQL (15 total)
> > ----------
> > Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
>
> I think you have completely misunderstood my point, which is not,
> "Don't change the name," but rather, "If we're going to change the
> name, we need a _plan_." I don't oppose changing the name as such. I
> oppose changing the name _now_, or _gradually_, or any of the other
> go-small answers that have been proposed. If we want to change the
> name, then we need to design the name change in the same careful way
> that we would expect new features to be designed.
>
> (This lack of nuance is why I think the poll on the EnterpriseDB web
> site is a bad one: it isn't a question of a specific proposal of how
> or when to change the name, but merely whether we ought to. If we're
> going to do it, can we please have a poll on a serious and complete
> proposal?)

As I understand it, the idea was to see if enough people want to
_explore_ a change, and then we can start discussing details. I will
remove you from the vote list until I hear otherwise.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

I really struggle with the idea that changing the brand name mandates the
programmers/core team to propagate the brand name back into the PostgreSQL
source code or package structure.

I would be interested in hearing why someone might think that?

Regards,

Liam
_____________________________________________
Liam O'Duibhir - Programme Manager - Open Source Software
Fujitsu Australia Software Technology
14 Rodborough Road, Frenchs Forest NSW 2086
Tel: (61-2) 9452 9068 Fax: (61-2) 9975 3779
Mob: 0423 025 852 Email: LiamOD(at)fast(dot)fujitsu(dot)com(dot)au
postgresql.fastware.com

> -----Original Message-----
> From: pgsql-advocacy-owner(at)postgresql(dot)org [mailto:pgsql-advocacy-
> owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: Tuesday, September 04, 2007 6:00 AM
> To: Bruce Momjian
> Cc: PostgreSQL advocacy
> Subject: Re: [CORE] Re: [pgsql-advocacy] The naming question (Postgres vs
> PostgreSQL)
>
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Tom Lane wrote:
> >> Of course, that's 70% of -advocacy, which by nature is going to be the
> >> subset of the community most interested in this change and least
> >> interested in the ensuing costs.
>
> > It seems there were a significant number of people with swag who will
> > pay the cost somehow.
>
> That's adopting exactly the view I thought it was, that only directly
> marketing-related costs matter. Again, this seems to be considering
> only advocacy-related concerns.
>
> I'll confine my reply to one point: do you have any idea what will
> happen if I try to change the default PGDATA location on Red Hat
> from /var/lib/pgsql to something else?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq

Andrew Sullivan wrote:
> I think you have completely misunderstood my point, which is not,
> "Don't change the name," but rather, "If we're going to change the
> name, we need a _plan_." I don't oppose changing the name as such. I
> oppose changing the name _now_, or _gradually_, or any of the other

Regardless of the intent and of the best efforts of core and
the entire community the name is changing _now_ and _gradually_.

Now - because even if it be decided in a fancy plan that the
name will change only after some date; people will begin adopt
adopting the new usage immediately after it's made official.

Gradually - because core doesn't control the world. There
are thousands of times more powerpoints in various sales
organizations in thousands companies around the world that
will be refreshed at the leisure of the sales people. Whether
core changes all of docs+web+comments-in-source in a day or
a month or a year or a decade; the real life usage of the
terms will take time to change.

Even if a plan says "burn all PostgreSQL swag", or "don't
say 'Postgres' without 'QL' until 9.2 is released" - in
reality the effect will start when a decision is made,
and be gradual.

> go-small answers that have been proposed.

I don't think "now" or "gradually" are "go-small". In contrast
I think they recognize that the change is something bigger
than what the postgresql project has direct control over.

Ron Mayer wrote:
> Regardless of the intent and of the best efforts of core and
> the entire community the name is changing _now_ and _gradually_.

Jan says our name is already being changed to Postgre`. I thought that
was pretty funny.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

2007-09-03_15:52:14-0400 Andy Astor <andy(dot)astor(at)enterprisedb(dot)com>:

> As I see it, -advocacy is the group most interested in the public face
> of PostgreSQL, and is very appropriate for this kind of debate.

Well, you could subtract me from that assessment. It doesn't take much
to simply join a maillist. I just stumbled into this list for purely
selfish reasons: I was looking for feedback on an article I was
submitting, and happened upon this discussion. (I recieved none, BTW.)
I certainly do have an opinion on the subject, but I must be honest -
I'm really the last person who should have any say in the matter. So
subtract me from the -advocacy group who should matter. Anyone else
care to abrogate their authority? Who _really_ stands to lose or gain
the most here? Not me, I'll say that.

I still think the people best qualified to say what should be done are
the people who have demonstrably already done the most; and that would
core. I'd also listen to the people who have been spending their own
time and money traveling, speaking, and otherwise hinging their
livelyhood on this project - but that's a much harder boundry to
delimit. I don't think anyone would argue with a pronouncment from
core. I think no matter what the decision, if it were made by any other
group, it would lack gravity, and lead to resentments.

I must say that it is at least funny to watch people getting frustrated
and sputtering while they try to rationalize irrational political
problems.

BTW, the best color is red. Blue is stupid.

--
Ron Peterson
https://www.yellowbank.com/

2007-09-03_15:55:09-0400 Andy Astor <andy(dot)astor(at)enterprisedb(dot)com>:

> Them who vote are them that make the decisions for them that
> don't. That's how it works. The fact that <50% of the American
> population vote for its president (with apologies for the US-centric
> view) doesn't make the vote invalid or the group voting inappropriate.

You can't vote for anarchy. ;)

> I suggest we all just sit back and respect each others' views and
> opinions, rather than trashing the very idea of the discussion.

True that.

--
Ron Peterson
https://www.yellowbank.com/

2007-09-03_20:36:44-0400 Ron Peterson <ron(dot)peterson(at)yellowbank(dot)com>:

> BTW, the best color is red. Blue is stupid.

(...in the interest of pre-emptively dousing any flames, I'd just like
to say that this comment has nothing to do with any particular
products... If it helps, reverse the colors..)

--
Ron Peterson
https://www.yellowbank.com/

2007-09-03_16:53:20-0400 Decibel! <decibel(at)decibel(dot)org>:

> Yes, it'll give us a name that's pronouncable and not confusing.

I would guess that the vast majority of communication about the product
is written, not spoken.

I think PostgreSQL looks better, and looks should matter more... ;)

--
Ron Peterson
https://www.yellowbank.com/

On Monday 03 September 2007 19:34, Bruce Momjian wrote:
> Ron Mayer wrote:
> > Regardless of the intent and of the best efforts of core and
> > the entire community the name is changing _now_ and _gradually_.
>
> Jan says our name is already being changed to Postgre`. I thought that
> was pretty funny.

Really? It's actually true. According to the google analytics report on
keywords that drive traffic to our site, the top four are:

postgresql 14%
postgres 7%
postgre 2%
postgre sql 1%

I should also bring up again the survey of postgresql community members where
we asked how people pronounced "PostgreSQL" the top four were:

post-gres-q-l 45%
postgres 30%
postgres-sequal 11%
post-gree 7%

As you can see from both cases, while the numbers are still on the lower end,
they are significant enough to show up clearly on the radar. In fact, it
wouldn't suprise me if within the next year or two, postgree actually becomes
a more popular pronounciation than postgres-sequal; a lot of non-native
english speakers (Indians for example) see an obvious split between postgre
and sql in the name. For them postgre is no more wierd than postgres, so as
thier numbers grow as users of the software, expect to see thier
pronounciation more and more.

Personally I also think it is worth noting that of the 55% of community
members who do think the SQL is significant in the name, even they don't
agree on how it should be pronounced, but that's kind of a side issue.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

scrappy(at)hub(dot)org ("Marc G. Fournier") writes:
> --On Monday, September 03, 2007 13:20:39 -0500 Decibel! <decibel(at)decibel(dot)org>
> wrote:
>
>> Ok, well, at the least then we really need to focus discussion on
>> "Should we change the name" and quit worrying about how we'll actually
>> do it.
>
> The other option is that EDB creates a Postgres community, GPLs the code and
> puts it all into Subversion, and run it in parallel to the PostgreSQL community
> ... then everyone that wants to keep the status quo can stick around and
> continue marketing and pushing PostgreSQL, and those that "want change" can
> just move over to that new project ...
>
> Now, *that* would be an interesting experiment ...

Ah, and I think that represents an interesting gedanken experiment as
to what proposal for change will get the wildest responses.

I'd sum that one up in two words:
In
and
sane.
--
(format nil "~S(at)~S" "cbbrowne" "cbbrowne.com")
http://linuxdatabases.info/info/lisp.html
"Consistency is the single most important aspect of *ideology.*
Reality is not nearly so consistent." - <cbbrowne(at)hex(dot)net>

Marc G. Fournier wrote:
>
>
> --On Monday, September 03, 2007 13:20:39 -0500 Decibel! <decibel(at)decibel(dot)org>
> wrote:
>
>> Ok, well, at the least then we really need to focus discussion on
>> "Should we change the name" and quit worrying about how we'll actually
>> do it.
>
> The other option is that EDB creates a Postgres community, GPLs the code and
> puts it all into Subversion, and run it in parallel to the PostgreSQL community
> ... then everyone that wants to keep the status quo can stick around and
> continue marketing and pushing PostgreSQL, and those that "want change" can
> just move over to that new project ...
>
> Now, *that* would be an interesting experiment ...

Won't happen - we use CVS, not Subversion.

;-)

Regards, Dave

Hi,

Bruce Momjian wrote:
> I have downloaded the Advocacy email archive for August and September
> and looked at all emails with the subject "naming". I read each email
> and totalled the opinions of all the posters. Of course, this is not
> scientific but it does represent everyone on advocacy who felt the
> need to comment on the thread.

If that poll is still running: +1 for "Postgres", because Germans simply
fail to pronounce PostgreSQL. And I really hate the sound of post-gree,
which definitely *is* how most Germans abbreviate PostgreSQL.

And.. well, yes, also because it's Postgres-R and not PostgreSQL-R. ;-)

Regards

Markus

dpage(at)postgresql(dot)org (Dave Page) writes:
> Marc G. Fournier wrote:
>>
>>
>> --On Monday, September 03, 2007 13:20:39 -0500 Decibel! <decibel(at)decibel(dot)org>
>> wrote:
>>
>>> Ok, well, at the least then we really need to focus discussion on
>>> "Should we change the name" and quit worrying about how we'll actually
>>> do it.
>>
>> The other option is that EDB creates a Postgres community, GPLs the code and
>> puts it all into Subversion, and run it in parallel to the PostgreSQL community
>> ... then everyone that wants to keep the status quo can stick around and
>> continue marketing and pushing PostgreSQL, and those that "want change" can
>> just move over to that new project ...
>>
>> Now, *that* would be an interesting experiment ...
>
> Won't happen - we use CVS, not Subversion.
>
> ;-)

There's the part that *isn't* insane.

I believe CMD already has a Subversion repository tracking CVS, so
it's possible, albeit duplicative.

There's plenty of interest in figuring out the relative merits of
other SCMs, so the idea of having an alternate repository does have
merit.

I think there would be more value in having a *different* repository,
say using Git, Mercurial, Darcs, or such, so that there would be
better opportunity to do relative comparisons between them.

The license fork, on the other hand ;-).
--
(format nil "~S(at)~S" "cbbrowne" "cbbrowne.com")
http://linuxdatabases.info/info/
Epistemology in One Lesson
Reality ruthlessly selects out creatures that embody hypotheses too
inconsistent with reality. Our only choice is whether we participate
by being selected out, or (in Popper's great phrase) by "letting our
ideas die in our stead."
-- Mark Miller

All,

From my perspective, this whole discussion ... and the EDB survey, and the
headcount on this thread, etc., is pretty much entirely moot. 40+ people are
arguing about what color to paint the bike shed, and not one person has
picked up a brush.

When someone steps forward with a concrete proposal, some market research (and
no, unscientific surveys of the existing community is not market research),
and allocations of volunteer time to do the work necessary for a name change
(something I'd peg at 150 to 250 hours combined work over the next year),
this whole discussion is pretty darned pointless.

I'll point out, for example, that despite identifying needs to work on both
the PostgreSQL "about" pages and the 8.3 press release, it's still the 5-6
old regulars doing 100% of the actual writing and development. And the old
regulars do NOT have the spare time to even think about a name change.

So Ron, Andy, others who are hot to change to Postgres: let's see a concrete
proposal, and one that comes up with new resources to do the new work.
Otherwise, let's terminate these threads and move on to some actual promoting
PostgreSQL.

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

In the various threads I've seen several people who have said they
will step up and do parts of the work. I will help on site design
issues. Heck I've even gone as far as to show how the current header
image would look. It obviously would need more work. I think the
decision has to be made as to if there will be a change to get any
farther down the road. If it's not going to happen, then any amount
of planning is a waste of time.

Is it too much, or the wrong question of Core to have a decision if
it's even possible/probable - should a good plan emerge on how to make
the change and who will do the work?

Gavin

On 9/4/07, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> All,
>
> From my perspective, this whole discussion ... and the EDB survey, and the
> headcount on this thread, etc., is pretty much entirely moot. 40+ people are
> arguing about what color to paint the bike shed, and not one person has
> picked up a brush.
>
> When someone steps forward with a concrete proposal, some market research (and
> no, unscientific surveys of the existing community is not market research),
> and allocations of volunteer time to do the work necessary for a name change
> (something I'd peg at 150 to 250 hours combined work over the next year),
> this whole discussion is pretty darned pointless.
>
> I'll point out, for example, that despite identifying needs to work on both
> the PostgreSQL "about" pages and the 8.3 press release, it's still the 5-6
> old regulars doing 100% of the actual writing and development. And the old
> regulars do NOT have the spare time to even think about a name change.
>
> So Ron, Andy, others who are hot to change to Postgres: let's see a concrete
> proposal, and one that comes up with new resources to do the new work.
> Otherwise, let's terminate these threads and move on to some actual promoting
> PostgreSQL.
>
> --
> Josh Berkus
> PostgreSQL @ Sun
> San Francisco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

Am Dienstag, 4. September 2007 18:16 schrieb Josh Berkus:
> From my perspective, this whole discussion ... and the EDB survey, and the
> headcount on this thread, etc., is pretty much entirely moot. 40+ people
> are arguing about what color to paint the bike shed, and not one person has
> picked up a brush.

Why would anyone pick up a brush if the color isn't decided yet? I think it's
reasonable to assume that once the color is decided, brushes can be located
quickly.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

On Tuesday 4 September 2007 12:16, Josh Berkus wrote:
> From my perspective, this whole discussion ... and the EDB survey, and the
> headcount on this thread, etc., is pretty much entirely moot. 40+ people are
> arguing about what color to paint the bike shed, and not one person has
> picked up a brush.

Please reread the posts. I did volunteer.

Am Dienstag, 4. September 2007 18:33 schrieb Gavin M. Roy:
> Is it too much, or the wrong question of Core to have a decision if
> it's even possible/probable

The core team appears to be about as much divided on this issue as those who
have spoken out on this mailing list. If someone wants to drive this forward
then they will have to organize a campaign from below. (Hint: This mailing
list is not quite low enough.)

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

On Tuesday 4 September 2007 12:58, Peter Eisentraut wrote:
> Am Dienstag, 4. September 2007 18:33 schrieb Gavin M. Roy:
> > Is it too much, or the wrong question of Core to have a decision if
> > it's even possible/probable
>
> The core team appears to be about as much divided on this issue as those who
> have spoken out on this mailing list. If someone wants to drive this
forward
> then they will have to organize a campaign from below. (Hint: This mailing
> list is not quite low enough.)

Which is why I suggested at the begining of this thread (which seems such as
long time ago) that we make a public announcement that we are installing a
poll on the postgresql.org website and ask for input from the general public.
The poll will help focus the community as well as increase the postgres
profile at there in the grand world too.

Well put, Peter.

Josh, we simply need to decide if we want to do it or not. Lots of people
have volunteered to help (including us), and the implementation project plan
can be a team effort of those people.

Andy

On 9/4/07 12:38 PM, "Peter Eisentraut" <peter_e(at)gmx(dot)net> wrote:

> Am Dienstag, 4. September 2007 18:16 schrieb Josh Berkus:
>> From my perspective, this whole discussion ... and the EDB survey, and the
>> headcount on this thread, etc., is pretty much entirely moot. 40+ people
>> are arguing about what color to paint the bike shed, and not one person has
>> picked up a brush.
>
> Why would anyone pick up a brush if the color isn't decided yet? I think it's
> reasonable to assume that once the color is decided, brushes can be located
> quickly.

Josh Berkus wrote:
> When someone steps forward with a concrete proposal

My concrete proposal. I want one simple statement from
the project that it's OK for people to say both "Postgres"
and "Postgre" so every customer, salesguy, and executive I
deal with doesn't get stuck in a terminology flame-war
evertime they use the obvious short form of PostgreSQL.

Here's a patch.

% diff -c faqs.FAQ.html faqs.FAQ.proposed
*** faqs.FAQ.html Tue Sep 4 10:59:34 2007
--- faqs.FAQ.proposed Tue Sep 4 10:59:01 2007
***************
*** 232,238 ****
<h3 id="item1.1">1.1) What is PostgreSQL? How is it pronounced?</h3>

<p>PostgreSQL is pronounced <i>Post-Gres-Q-L</i>, and is also sometimes
! referred to as just <i>Postgres</i>. An audio file is available in
<a href="http://www.postgresql.org/files/postgresql.mp3">MP3 format</a> for
those would like to hear the pronunciation.</p>

--- 232,242 ----
<h3 id="item1.1">1.1) What is PostgreSQL? How is it pronounced?</h3>

<p>PostgreSQL is pronounced <i>Post-Gres-Q-L</i>, and is also sometimes
! referred to as just <i>Postgres</i>.
! The unofficial pronunciations of <i>Post-gree</a> and
! <i>Post-gray</a> are also acceptable and should not be
! objected to when used by new users or customers.
! An audio file is available in
<a href="http://www.postgresql.org/files/postgresql.mp3">MP3 format</a> for
those would like to hear the pronunciation.</p>

%

Hi Josh,

I think you are absolutely right. If there would be a name change, then
there would first need to be a plan of what needs to be done. It does
not make sense to start with looking volunteers, before it is known what
needs to be done, since the people who would like to help, would also
need to be able to do it.

But I do disagree with the 150-250 hours amount of work. That would be
about 6 weeks full time. I don't think it will happen that easily. I bet
150 hours is already spent on this thread. Of course, if you meant that
you would need to use that time on it, yes, that might be true. Though I
am not sure, even if that would be enough. From marketing perspective,
changing the name is probably one of the biggest tasks around.

Let's say you would have 10 interviews about the name change. You would
use 1 hour for preparing to them and 1 hour on them. That would already
be 20 hours. Then let's say that you are in 2 public events talking
about the topic. Travelling 15 hours per event, talking 1 hour each.
Together that would be already over 50 hours of your time, and I think
that you would need to do something else too.

Rgs,

Jussi

Josh Berkus wrote:
> All,
>
> >From my perspective, this whole discussion ... and the EDB survey, and the
> headcount on this thread, etc., is pretty much entirely moot. 40+ people are
> arguing about what color to paint the bike shed, and not one person has
> picked up a brush.
>
> When someone steps forward with a concrete proposal, some market research (and
> no, unscientific surveys of the existing community is not market research),
> and allocations of volunteer time to do the work necessary for a name change
> (something I'd peg at 150 to 250 hours combined work over the next year),
> this whole discussion is pretty darned pointless.
>
> I'll point out, for example, that despite identifying needs to work on both
> the PostgreSQL "about" pages and the 8.3 press release, it's still the 5-6
> old regulars doing 100% of the actual writing and development. And the old
> regulars do NOT have the spare time to even think about a name change.
>
> So Ron, Andy, others who are hot to change to Postgres: let's see a concrete
> proposal, and one that comes up with new resources to do the new work.
> Otherwise, let's terminate these threads and move on to some actual promoting
> PostgreSQL.
>
>

Andy, Ron, Peter, etc.:

> Josh, we simply need to decide if we want to do it or not. Lots of
> people have volunteered to help (including us), and the implementation
> project plan can be a team effort of those people.

Ok, that didn't come out right.

To restate:

The next step of this process is NOT a poll. The next step of "should we
do it or not" is a rough draft of a plan which shows all of the "costs" of
changing the name and how we're going to meet them, as well as the Pros
and Cons of changing vs. not changing.

There is no point in even talking further about changing the name of the
project if we don't have the resources to do the change. There's
particularly no point in doing a survey of people's uninformed opinions
about the issue; community members need to see a cost-benefit analysis
*first,* not after a vote.

In other words, before we take a vote on whether the bike shed should be
red, we should first check to see if we can afford red paint.

Such a proposal should also include other options like Ron Mayer's very
sensible 20-minute solution (e.g. "Postgres and Postgre are acceptable
alternate names").

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

2007-09-04_12:16:42-0400 Josh Berkus <josh(at)agliodbs(dot)com>:

> So Ron, Andy, others who are hot to change to Postgres

Umm, you've got me on the wrong side of the issue. I've also said I
don't think my opinion should really count anyway..

--
Ron Peterson
https://www.yellowbank.com/

Ron Mayer wrote:
> Josh Berkus wrote:
> > When someone steps forward with a concrete proposal
>
> My concrete proposal. I want one simple statement from
> the project that it's OK for people to say both "Postgres"
> and "Postgre" so every customer, salesguy, and executive I
> deal with doesn't get stuck in a terminology flame-war
> evertime they use the obvious short form of PostgreSQL.

> --- 232,242 ----
> <h3 id="item1.1">1.1) What is PostgreSQL? How is it pronounced?</h3>
>
> <p>PostgreSQL is pronounced <i>Post-Gres-Q-L</i>, and is also sometimes
> ! referred to as just <i>Postgres</i>.
> ! The unofficial pronunciations of <i>Post-gree</a> and
> ! <i>Post-gray</a> are also acceptable and should not be
> ! objected to when used by new users or customers.
> ! An audio file is available in
> <a href="http://www.postgresql.org/files/postgresql.mp3">MP3 format</a> for
> those would like to hear the pronunciation.</p>

You gotta be kidding. I would reword this as

What is Postgres? How is it pronounced?

Postgres is pronounced Post-Gres, and is sometimes referred to in
written form as PostgreSQL (which is not normally said out aloud).

--
Alvaro Herrera http://www.flickr.com/photos/alvherre/
"La naturaleza, tan frágil, tan expuesta a la muerte... y tan viva"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

<p>PostgreSQL is pronounced <i>Post-Gres-Q-L</i>, and is also sometimes
! referred to as just <i>Postgres</i>.
! The unofficial pronunciations of <i>Post-gree</a> and
! <i>Post-gray</a> are also acceptable and should not be
! objected to when used by new users or customers.
! An audio file is available in
<a href="http://www.postgresql.org/files/postgresql.mp3">MP3 format</a> for
those would like to hear the pronunciation.</p>

Uh, no, the idea is to simplify things, not make them worse. We don't need
four different ways to refer to the project. For the record, I've never heard
"Post-gray" and "Post-gree" used in the wild. "Postgres" is simple,
unambiguous, easy to remember, and is already used quite widely verbally.
The other alternatives will simply remind people of the original ill-fated
decision. I've already put forth my own FAQ patch earlier in this thread.

> But I do disagree with the 150-250 hours amount of work.

As do I. I think it would be about 4 hours of 'work'. We change the FAQ,
write a press release stating the name is changing, stop scolding people
in various forums for using Postgres instead of PostgreSQL, and slowly
start moving things over. If the domain name stays at postgresql.org for
six years, or more, that's okay. People can use the name PostgreSQL for
as long as they want, and nobody in the community should yell at them.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200709041503
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFG3a0JvJuQZxSWSsgRA0jXAKCtFCFR4n297l5jVEVBDiLpHTLWQgCgtSls
DFlkSnLOHCKIyPiBlev/tGE=
=5fzB
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

> The next step of this process is NOT a poll. The next step of "should we
> do it or not" is a rough draft of a plan which shows all of the "costs" of
> changing the name and how we're going to meet them, as well as the Pros
> and Cons of changing vs. not changing.

Excellent point, Josh, I think we've outgrown a mailing list. I made a
quick wiki page. Pleae let Neil or myself know if anyone needs editing privs:

http://developer.postgresql.org/index.php/Postgres

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200709041537
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFG3bQLvJuQZxSWSsgRAy4mAJwMNTqbcFou2LdMuoJ5XP2qZNn3TwCfeEfM
UHp5rrEF0qGLkMJuJ69pyPA=
=/gHX
-----END PGP SIGNATURE-----

Greg Sabino Mullane wrote:
>> But I do disagree with the 150-250 hours amount of work.
>
> As do I. I think it would be about 4 hours of 'work'.

The total amount of _OPTIONAL_ and downright
unnecessary work is immense:
* Salespeople using the product across the
world "having" to update all their powerpoints.
* Renaming Josh D's company (to "Command PromptSQL" so
people don't forget they do SQL?).
* Sending out recall notices so everyone who received
swag with the old names.
* Scouring the source code to remove "pgsql" and
replacing it with "pgs".
* Tracking down all the instances of PostgreSQL on
the web site.
But none of those need to happen so long as everyone
agrees PostgreSQL is still accepted. And arguably
none of these should ever happen.

The minimal required amount of work is much less than even
the 4 hours. It's about 30 seconds. A simple email
to the lists from core saying:
"We will move to Postgres in the future.
We welcome patches.
For those new to submitting patches, here's where to
submit patches to web and docs"
is, IMHO, enough. Yes, reviewing and accepting the
patches is more work, but that can happen at the leisure
of the committers over the next dozen years.

The only way I see it actually being a lot of required
work is if someone proposes banning PostgreSQL -- but
I've not ever seen any proposal that includes that.

On 9/4/2007 3:02 PM, Josh Berkus wrote:
> There is no point in even talking further about changing the name of the
> project if we don't have the resources to do the change. There's
> particularly no point in doing a survey of people's uninformed opinions
> about the issue; community members need to see a cost-benefit analysis
> *first,* not after a vote.

While I 100% agree that further discussion or polls or votes or anything
are pointless until we have a reasonably detailed plan, I totally doubt
that it can contain something even remotely resembling a cost-benefit
analysis. Sure, one can estimate the cost and outline the "expected"
benefits, but cost is expressed in man hours while the benefits of a
name change are speculative expressed in name branding, recognition, all
the things associated with a nice name. And you can't really put a price
tag on that, so that analysis would be apples to elephants comparison.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

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

greg(at)turnstep(dot)com ("Greg Sabino Mullane") writes:
>> The next step of this process is NOT a poll. The next step of "should we
>> do it or not" is a rough draft of a plan which shows all of the "costs" of
>> changing the name and how we're going to meet them, as well as the Pros
>> and Cons of changing vs. not changing.
>
> Excellent point, Josh, I think we've outgrown a mailing list. 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 added a section to it documenting "Tasks in the Upgrading The Name
Project."

It may make sense to start by populating that with some set of
"brainstormed" items.

It might then make sense to classify those between:
- Tasks that are Certainly Necessary
- Tasks that are Certainly Unnecessary

I put in a few things that I thought of, but haven't attempted
classification, as that seems premature.
--
output = ("cbbrowne" "@" "linuxfinances.info")
http://www3.sympatico.ca/cbbrowne/lisp.html
Rules of the Evil Overlord #173. "Although it would provide amusement,
I will not confess to the hero's rival that I was the one who
committed the heinous act for which he blames the hero."
<http://www.eviloverlord.com/>

On Tuesday 04 September 2007 16:47, Josh Berkus wrote:

I think you're inflating this a bit.

> Issues not addressed above:
> path names

path names are the purview of the packagers. We don't have a consistent path
setup now, and the closest thing to one is pgsql, which need not change.

> file names

I think general agreement is that the filenames need not change. Personally
the only file I can think of that matters is the postgresql.conf, which I do
think we should change, but probably would not matter if we didnt. We already
have lived with our primary binary being callled the postmaster for many
years (which thankfully is now just postgres).

> package names

this one is tricker, but i dont think it is all that hard. I'd suspect that in
8.4, packagers would rename thier packages to postgres, with dependencies
pointing to postgresql packages. Yeah, it's probably trickier than this, but
it really depends on the packaging system. (Perhaps a packager wants to wiegh
in on this point?)

> server strings (which all have to be translated into 11 languages)

I feel confident that I can translate PostgreSQL to Postgres in the majority
of languages that are involved.

> re-designing marketing materials

Generally things probably wont have to be redesigned, just updated. Those that
want to redesign are welcome to do it, but if you but the scope of the name
change toward an 8.4 time frame, you realize that most marketing material
will have to be changed by then anyway.

> links from external sites

We control all of the postgresql domains, and I see no reason we would
relinquish them, so we only need a bit of redirection to preserve links.

> contacting packagers, commercial distributors and downstream projects so
> they all know about the name change

again, if you push this to a 8.4 timeframe, this unlikely to be a problem.
Certainly we have ways to contact the majority of packagers very quickly to
let them know what is happening.

> graphics redesign
>

I have a little bit of concern for this one, because we mave have some
graphics that say postgresql in fonts / sources we can't easily update. So
this one might be an issue (let people not forget a number of the powered by
postgresql buttons would need updating).

So of your list, I see very few items that are actually significant work. I
think the next step for anyone who seriously wants to push this forward needs
to do is see about how available the various domain names we need to aquire
are, and also to contact a good number of packagers to get thier input on how
much effort this will involve for them. Those two things could be show
stoppers, but nothing on your list looks like one to me.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

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
or have 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 because it's the
obvious short form of PostgreSQL; which will prevent some of the
abuse of new members, users, and customers of the product.
* or, Fund a marketing campaign to educate the world that
we're not Postgre.
* Rename paths and filenames and processes from postgres to postgresql.
* Update paths on website that use "pgsql" instead of "PostgreSQL".
* Produce new swag as the old inventory is used up.
* Make links use PostgreSQL.org instead of postgresql.org to
re-enforce the 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 decision to 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 project if he seeSQL how new userSQL
parse wordSQL with mixed case."
would server better.

Hello,

new to this list but long term postgres user.

David Fetter mentioned the discussion in his weekly update that gets
posted to the german list and he called it civilized. That made me
reading certainly some hundred posts from the archive, maybe half
of the thread and finally joining the list to participate in this
discussion. I came to the conclusion that it is not friendly at all.

Can there really be people who search for misspelled semicolons in
their source files as a day job, blaming others to make a lot of hot
air out of nothing when arguing about pronounciation of the project
name? I can hardly believe.

Pronounciation might be only one single argument compared to so
many arguments against a name change. And it is a soft point com-
pared to a missing semicolon that inevitably stops your query.
But that doesnt make it be a weak argument. For me, there can
hardly be anything more striking.

Working code is of utmost importance, but all the bruhaha around
doesnt count less I believe. And if marketing oriented people have
a strong opinion about that issue, constantly neglecting the im-
portance of their input feels rather destructive. Some day, they
will leave you coders alone and the project might decline.

I personally like to pronounce the RDBMS as Postgres-Qu-El but am
too lazy to write the whole thing, so actually I do just the opposite
of what seems to be common use. But when reminded of the problems with
the two names I can recall the hurdles that they exposed in the be-
ginning. And that was long before I asked anybody about it in a face
to face talk on a fair.
It was really disturbing when googling for a solution on an issue
I had, never to know exactly whether the results referring to postgres
would really apply to the postgresql thing I was using as well.

Name confusion is not a minor thing and having postfix and postgres
running on the same machine (postfix is the default MTA under MacOS X)
caused confusion with the postmaster process showing in top and ps
when I expected it not to run, only to find out that it was not what
it seemed to be. And finally, you took action, great.

The strangest solution to the problem I found in this thread was
renaming to PostgresQL. Sorry, but there is no such thing as a
separate Postgres Query Language, incompatible with Standard SQL
as implied by this name. This would certainly bring confusion to
a new level. And please, do not install a committee to decide on
that - these are kind of solutions that come from such circles.

For me the discussion seems to be the type of thing where you keep
to say "no" until the day where you finally say yes. Its in the air.
I dont like postgres much better or better at all, but it is obvious
that it will be the official name sooner or later. It needs to happen
some day. The sooner the better.

From my point of view, the marketing name move should not be tied to
the next major release. Doing so puts pressure on the decision what
might be worth a major number and when it should happen (ASAP). This
is not appropriate for a project, where quality standards should
drive the decision for final release dates.

On the other hand, I share the doubts with package renaming. I use
the macports project for updating my system and in this package
management system the port to be installed is called postgresql8.
Renaming this to postgres8 would break all ports depending on it.
Most ports will continue to use an old version that does not receive
security fixes any more. But with the advent of postgres 9, there
will be a separate package named postgersql9 or postgres9 anyway,
because some other package maintainer might decide to stay with
the older release. Nobody will mind the name change then.
I guess this is the same with freebsd ports, debian apt-get,
redhat rpm, gentoo and myriad of other package management repos.

Under these circumstances, a big bang solution does not seem feasable.
The big bang type of name change usually happens only with companies
that have the bang to do so. But even they sometimes decide for a
incremental change. Rebranding the german mobile carrier Mannesmann D2
to vodafone was an example for this strategy and renaming the electric
power company HEW to Vattenfall also took more then a year and several
big sports events to make sure the transition works smoothly and people
dont refuse to pay to a company they never contracted with.

But, this does not mean necessarily that we need to switch silently.
I tend to use the elephants trunk and trumpet it out, but I have to
admit that it does not fit perfectly with an incremental strategy.

As with the all the work that needs to be done on the marketing side,
I dont understand these objections completely, because they should be
mentioned by those who would have to deal with it and not by the coders
who are opposed to a change. I bet, that people who do care for a good
name will take care for a good visual appearance as well. I guess that
the artwork stuff will be done in no time by people who are happy to
contribute. FreeBSD ran such a thing for their website relaunch as
their first Google Summer of Code project some years ago IIRC - just
a proposal.

Regarding printed paper, it was already mentioned that it usually
grows old before a year is over. T-Shirts are certainly different,
but they get a pale stripe across the breast when exposed to the sun
and dont look good after a while as well. Everybody who buys marketing
stuff for more then a year in advance will regret this decision some
day, whether the name changes or not, because of the cash drain, the
waste of storage and all this. And if somebody comes moaning to a
booth on a fair, complaining that the name on the booth and the website
are different, what better time to ask for some money to change this?

The only thing that I saw that is a real obstacle besides dullness were
the legal issues raised by the fact that a company holds rights to the
name but is not willing to explain what they intend to do with it. This
could become a complete showstopper. But I am not a lawyer and there
will be others who might find a way to deal with that.

This was more then two cents I admit, but spending hours reading,
I could not resist and keep my mouth shut.

Bye, Christian

All,

I've updated the wiki with my task list and the suggestions/comments from
others on this mailing list. You can now see where my estimate of 150-250
hours comes from, which I now think is probably rather low.
http://developer.postgresql.org/index.php/Postgres

Now, that's as much time as I'm planning to spend on that until after 8.3 is
out.

--
Josh Berkus
PostgreSQL @ Sun
San Francisco

Josh Berkus wrote:
> All,
>
> I've updated the wiki with my task list and the suggestions/comments from
> others on this mailing list. You can now see where my estimate of 150-250
> hours comes from, which I now think is probably rather low.
> http://developer.postgresql.org/index.php/Postgres

It seems most of those tasks are just as required with
the current state of PostgreSQL as official and Postgres
as an accepted alternative -- i.e. all
the "pgsql -> [official_name]" changes in the list;
and clarification between postgres and progress and ingress.

Or are you suggesting that you see those as unnecessary
because there's so much confusion today (pgfoundry even
mentions PostgresSQL with 2 ss's) that there's no hope,
but you see it as achievable with the new name?

Some of the "Cons" seem quite artificial too - "Some corporate
supporters may be unhappy about renaming materials/marketing/packaging".
Of course - we know Josh D is. On the other hand, some corporate
sponsors may be unhappy with the current name too.

> Now, that's as much time as I'm planning to spend on that until after 8.3 is
> out.

Yeah - This is tiring; but I'm just taking comfort in the fact that
over the years Postgres usage is consistently gaining on PostgreSQL
(as is Postgre) so the change will come sooner or later anyway.

If it seems the current name'll stick around at least for the months
your "Further Information Needed" section will take, would you like
patches to convert some of the "pgsql"'s and "postgres"'s in the code
and website to "PostgreSQL"'s?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --On Wednesday, September 05, 2007 11:05:07 -0700 Ron Mayer
<rm_pg(at)cheapcomplexdevices(dot)com> wrote:

> It seems most of those tasks are just as required with
> the current state of PostgreSQL as official and Postgres
> as an accepted alternative -- i.e. all
> the "pgsql -> [official_name]" changes in the list;

Nope, pgsql is, and always has been, an accepted and logical short form of
PostgreSQL ... pg is as close as you get if you try and shorten Postgres ...

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)

iD8DBQFG3vDp4QvfyHIvDvMRAvo4AJ4mQEYqcEpUiD25Ob7GjiU3PCIfpwCg1dGk
oBeW0tAPBaWidOE/ebBuqNc=
=BRQo
-----END PGP SIGNATURE-----

On Mon, 2007-09-03 at 19:34 -0400, Bruce Momjian wrote:
> Ron Mayer wrote:
> > Regardless of the intent and of the best efforts of core and
> > the entire community the name is changing _now_ and _gradually_.
>
> Jan says our name is already being changed to Postgre`. I thought that
> was pretty funny.

The correct original pronunciation of the name Ingres does not sound the
trailing "s". Most language students attempting to say the name
correctly will do this, whether we call it Postgres or PostgreSQL.

I vote "Postgres". However much we advertise differently, most *users*
read what they see when they type "ps", and they see "postgres".

My suggested plan would be to just start using the name Postgres. Don't
make a broad industry announcement, just start using it and let the
older name tail away slowly. If asked, we just say we clarified the name
to avoid confusion between the two versions PostgreSQL and Postgres.
PostgreSQL need not be "wrong" its just the less preferred version now;
if people know the name PostgreSQL they can continue using it without
feeling stupid for getting it "wrong". Roughly the same as we would do
when we deprecate any commonly used feature.

My perspective is that the only incorrect spelling of Postgres is
"MySQL", etc.

--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com

Marc G. Fournier wrote:
> Nope, pgsql is, and always has been, an accepted and logical short form of
> PostgreSQL ... pg is as close as you get if you try and shorten Postgres ...

Indeed - but "ps" seems like the most logical short form of PostgreSQL.
Or when pronounced out loud "Postgres Q L", "pq" would be. Perhaps
that's where libpq came from?

On 9/5/07, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> wrote:
> Indeed - but "ps" seems like the most logical short form of PostgreSQL.
> Or when pronounced out loud "Postgres Q L", "pq" would be. Perhaps
> that's where libpq came from?

Actually, libpq is a throwback to Ingres.

Ingres has libq (otherwise known as the EQUEL runtime library) and
Postgres got libpq (the Postgres front-end library).

--
Jonah H. Harris, Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
33 Wood Ave S, 3rd Floor | jharris(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/

On 9/5/2007 5:51 PM, Jonah H. Harris wrote:
> On 9/5/07, Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> wrote:
>> Indeed - but "ps" seems like the most logical short form of PostgreSQL.
>> Or when pronounced out loud "Postgres Q L", "pq" would be. Perhaps
>> that's where libpq came from?
>
> Actually, libpq is a throwback to Ingres.
>
> Ingres has libq (otherwise known as the EQUEL runtime library) and
> Postgres got libpq (the Postgres front-end library).

Close.

Postgres' original query language was PostQUEL, an extended version of
University Ingres' QUEL. You can still see some of the original verbiage
in the query rule rewriter ... things like fireRIRrules() and the like.
RIR is short for "retrieve instead retrieve", and RETRIEVE was the
command replaced today by SELECT. An RIR rule is what implements a view.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

Hi,

Simon Riggs wrote:
> My suggested plan would be to just start using the name Postgres. Don't
> make a broad industry announcement, just start using it and let the
> older name tail away slowly.

*nod*

Let's simply start a slow migration, where everyone can participate and
help make it happen. That's much more in the spirit of OSS.

Regards

Markus

Agree with Postgres as the name and the just use it with a slow fade of
the old.

-----Original Message-----
From: pgsql-advocacy-owner(at)postgresql(dot)org
[mailto:pgsql-advocacy-owner(at)postgresql(dot)org] On Behalf Of Markus
Schiltknecht
Sent: Thursday, September 06, 2007 3:18 AM
To: Simon Riggs
Cc: Bruce Momjian; Ron Mayer; Andrew Sullivan;
pgsql-advocacy(at)postgresql(dot)org
Subject: Re: [pgsql-advocacy] The naming question (Postgres vs
PostgreSQL)

Hi,

Simon Riggs wrote:
> My suggested plan would be to just start using the name Postgres.
Don't
> make a broad industry announcement, just start using it and let the
> older name tail away slowly.

*nod*

Let's simply start a slow migration, where everyone can participate and
help make it happen. That's much more in the spirit of OSS.

Regards

Markus

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Josh Berkus wrote:
> Andy, Ron, Peter, etc.:
>
> > Josh, we simply need to decide if we want to do it or not. Lots of
> > people have volunteered to help (including us), and the implementation
> > project plan can be a team effort of those people.
>
> Ok, that didn't come out right.
>
> To restate:
>
> The next step of this process is NOT a poll. The next step of "should we
> do it or not" is a rough draft of a plan which shows all of the "costs" of
> changing the name and how we're going to meet them, as well as the Pros
> and Cons of changing vs. not changing.
>
> There is no point in even talking further about changing the name of the
> project if we don't have the resources to do the change. There's
> particularly no point in doing a survey of people's uninformed opinions
> about the issue; community members need to see a cost-benefit analysis
> *first,* not after a vote.
>
> In other words, before we take a vote on whether the bike shed should be
> red, we should first check to see if we can afford red paint.
>
> Such a proposal should also include other options like Ron Mayer's very
> sensible 20-minute solution (e.g. "Postgres and Postgre are acceptable
> alternate names").

OK, looks like we now have a list of items to address _if_ we change the
name:

http://developer.postgresql.org/index.php/Postgres

I believe the next step we discussed was to get feedback from the
'general' email list. Correct?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Friday 14 September 2007 11:00, Bruce Momjian wrote:
> Josh Berkus wrote:
> > Andy, Ron, Peter, etc.:
> > > Josh, we simply need to decide if we want to do it or not. Lots of
> > > people have volunteered to help (including us), and the implementation
> > > project plan can be a team effort of those people.
> >
> > Ok, that didn't come out right.
> >
> > To restate:
> >
> > The next step of this process is NOT a poll. The next step of "should we
> > do it or not" is a rough draft of a plan which shows all of the "costs"
> > of changing the name and how we're going to meet them, as well as the
> > Pros and Cons of changing vs. not changing.
> >
> > There is no point in even talking further about changing the name of the
> > project if we don't have the resources to do the change. There's
> > particularly no point in doing a survey of people's uninformed opinions
> > about the issue; community members need to see a cost-benefit analysis
> > *first,* not after a vote.
> >
> > In other words, before we take a vote on whether the bike shed should be
> > red, we should first check to see if we can afford red paint.
> >
> > Such a proposal should also include other options like Ron Mayer's very
> > sensible 20-minute solution (e.g. "Postgres and Postgre are acceptable
> > alternate names").
>
> OK, looks like we now have a list of items to address _if_ we change the
> name:
>
> http://developer.postgresql.org/index.php/Postgres
>
> I believe the next step we discussed was to get feedback from the
> 'general' email list. Correct?

I'd say no. Someone should talk to the packagers to asses viability, and
someone should review domain names, to asses viability. If those seem viable,
then open it up. If not, people need to know before they decide.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

Robert Treat wrote:
> > > In other words, before we take a vote on whether the bike shed should be
> > > red, we should first check to see if we can afford red paint.
> > >
> > > Such a proposal should also include other options like Ron Mayer's very
> > > sensible 20-minute solution (e.g. "Postgres and Postgre are acceptable
> > > alternate names").
> >
> > OK, looks like we now have a list of items to address _if_ we change the
> > name:
> >
> > http://developer.postgresql.org/index.php/Postgres
> >
> > I believe the next step we discussed was to get feedback from the
> > 'general' email list. Correct?
>
> I'd say no. Someone should talk to the packagers to asses viability, and
> someone should review domain names, to asses viability. If those seem viable,
> then open it up. If not, people need to know before they decide.

Are you saying we should ask the packagers email list? I don't see any
other way to ask them.

I heard we were OK with domain names.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Bruce,

>>> I believe the next step we discussed was to get feedback from the
>>> 'general' email list. Correct?

Wrong. Competely and totally wrong.

Look at the amount of stuff on that page which is listed as "more
information needed":

===========
Need an inventory of graphics containing "PostgreSQL"
Poll non-users to find out if name has any effect on adoption
Poll corporate supporters
Check with press contacts / analysis on likely press reaction
Poll downstream projects on reaction to name change
Poll regional/language groups & packagers
Check for legal issues
Detailed listing of all materials which need changing.
===========

While some of this could wait until after we decide to change, some of
it absolutely cannot. We could easily discover that most of our
corporate supporters oppose the change, the distros will hate us, press
reaction would be bad, and that there are numerous legal issues ... in
which case the name-changing idea is dead no matter what the folks on
-general think.

Please stop thinking of the name change as something to be done over an
idle weekend, and start thinking of it as a major feature like WAL,
Schema or HOT. It's going to require just as much work, if not more.

I'll also point out that not one of the people who said they'd "do
whatever it takes" has yet stepped forward to research any of these topics.

--Josh Berkus

Josh Berkus wrote:
> Bruce,
>
> >>> I believe the next step we discussed was to get feedback from the
> >>> 'general' email list. Correct?
>
> Wrong. Completely and totally wrong.

Are you trying to throw up roadblocks? That is my analysis. I was just
suggesting we ask the general list. Now maybe if you said I was "100%
wrong" I would think twice, but for "completely and totally wrong" I
think I will just barrel ahead. ;-)

You stated:

> There's particularly no point in doing a survey of people's uninformed
> opinions about the issue; community members need to see a cost-benefit
> analysis *first,* not after a vote.

Seems we have cost/benefit list already. Based on your list below I
think asking 'general' should be done before "Poll non-users to find out
if name has any effect on adoption" because unless we are more serious
about the change no one wants to do more work.

I realize some people are trying to minimize the work involved, but some
are trying to maximize it too.

---------------------------------------------------------------------------

> Look at the amount of stuff on that page which is listed as "more
> information needed":
>
> ===========
> Need an inventory of graphics containing "PostgreSQL"
> Poll non-users to find out if name has any effect on adoption
> Poll corporate supporters
> Check with press contacts / analysis on likely press reaction
> Poll downstream projects on reaction to name change
> Poll regional/language groups & packagers
> Check for legal issues
> Detailed listing of all materials which need changing.
> ===========
>
> While some of this could wait until after we decide to change, some of
> it absolutely cannot. We could easily discover that most of our
> corporate supporters oppose the change, the distros will hate us, press
> reaction would be bad, and that there are numerous legal issues ... in
> which case the name-changing idea is dead no matter what the folks on
> -general think.
>
> Please stop thinking of the name change as something to be done over an
> idle weekend, and start thinking of it as a major feature like WAL,
> Schema or HOT. It's going to require just as much work, if not more.
>
> I'll also point out that not one of the people who said they'd "do
> whatever it takes" has yet stepped forward to research any of these topics.
>
>
> --Josh Berkus
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Josh Berkus wrote:
>> Bruce,
>>
>>>>> I believe the next step we discussed was to get feedback from the
>>>>> 'general' email list. Correct?
>> Wrong. Completely and totally wrong.
>
> Are you trying to throw up roadblocks?

Now he is trying to make you realize what level of job this really is. A
great many people on this list have already proven excessively ignorant
to the scope of work the name change proposal is.

> That is my analysis. I was just
> suggesting we ask the general list. Now maybe if you said I was "100%

Bruce... consider the length of this thread on advocacy. Now you want to
take it to general? Don't we currently have better things to do? Like,
say getting 8.3 out the door?

> You stated:
>
>> There's particularly no point in doing a survey of people's uninformed
>> opinions about the issue; community members need to see a cost-benefit
>> analysis *first,* not after a vote.
>
> Seems we have cost/benefit list already. Based on your list below I
> think asking 'general' should be done before "Poll non-users to find out

Are you also going to communicate with the hundreds of thousands of
users that having nothing to do with the PostgreSQL lists? If so.. how?

>
> I realize some people are trying to minimize the work involved, but some
> are trying to maximize it too.

No, they are trying to make sure it is done right, without barreling
ahead and ignoring the requirements of others. A *lot* of people have
put a huge vested interest in PostgreSQL and you in your arrogance are
completely ignoring that.

Our largest community has said "no". Our budding communities in Italy
and France have said, "no. The only people that seem to really be
wanting the name change are those whom it won't effect, like you Bruce.

It won't effect you. You don't have to do anything but possibly change a
couple of words in FAQ. Let's be realistic and look at the things and
people this is going to effect, in a severe way.

Sincerely,

Joshua D. Drake
- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6ruRATb/zqfZUUQRAre+AJ9/OLcFW/xoGtRdmd+pxprUSOEODACgjybX
pe3u+NwVYi4r4fCXQovmcBo=
=KVbV
-----END PGP SIGNATURE-----

Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Bruce Momjian wrote:
> > Josh Berkus wrote:
> >> Bruce,
> >>
> >>>>> I believe the next step we discussed was to get feedback from the
> >>>>> 'general' email list. Correct?
> >> Wrong. Completely and totally wrong.
> >
> > Are you trying to throw up roadblocks?
>
> Now he is trying to make you realize what level of job this really is. A
> great many people on this list have already proven excessively ignorant
> to the scope of work the name change proposal is.
>
> > That is my analysis. I was just
> > suggesting we ask the general list. Now maybe if you said I was "100%
>
> Bruce... consider the length of this thread on advocacy. Now you want to
> take it to general? Don't we currently have better things to do? Like,
> say getting 8.3 out the door?

I think we have to decide if we really want to do this, and I don't see
how we can do that without asking general. I can ask people to email me
directly and put up a web page with comments, or just set up a web page
wiki to add comments.

> > You stated:
> >
> >> There's particularly no point in doing a survey of people's uninformed
> >> opinions about the issue; community members need to see a cost-benefit
> >> analysis *first,* not after a vote.
> >
> > Seems we have cost/benefit list already. Based on your list below I
> > think asking 'general' should be done before "Poll non-users to find out
>
> Are you also going to communicate with the hundreds of thousands of
> users that having nothing to do with the PostgreSQL lists? If so.. how?

Well, we change things in every major release without asking
_everybody_. I have seen few complaints about that processes.

> > I realize some people are trying to minimize the work involved, but some
> > are trying to maximize it too.
>
> No, they are trying to make sure it is done right, without barreling
> ahead and ignoring the requirements of others. A *lot* of people have
> put a huge vested interest in PostgreSQL and you in your arrogance are
> completely ignoring that.

Arrogance is one of my strong points. You should see my weakness list. :-)

> Our largest community has said "no". Our budding communities in Italy
> and France have said, "no. The only people that seem to really be
> wanting the name change are those whom it won't effect, like you Bruce.
>
> It won't effect you. You don't have to do anything but possibly change a
> couple of words in FAQ. Let's be realistic and look at the things and
> people this is going to effect, in a severe way.

Using your own measurements, you didn't ask everyone in those
communities either.

My basic issue is we can't use "asking for more details" to forever
block this change. That's how organizations stop growing.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Joshua D. Drake wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1

> My basic issue is we can't use "asking for more details" to forever
> block this change. That's how organizations stop growing.
>

5000 bucks and a case of whatever you drink says, that if we drop this
topic, PostgreSQL won't stop growing.

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6r6SATb/zqfZUUQRAozCAJ9E2mCGj68K37Xt1kwrsaN+DpZmmgCglGfV
Dm8+oQTjcj093XotOiI58/U=
=krKc
-----END PGP SIGNATURE-----

Joshua D. Drake wrote:
> Bruce Momjian wrote:
> > Joshua D. Drake wrote:
> > My basic issue is we can't use "asking for more details" to forever
> > block this change. That's how organizations stop growing.
> >
>
> 5000 bucks and a case of whatever you drink says, that if we drop this
> topic, PostgreSQL won't stop growing.

True, but will a name change increase growth?

The bottom line is I am fine with accepting whatever the group wants on
this, but I don't want our institutional momentum to prevent a change
if a change is overall beneficial. Institutional momentum can be a very
dangerous thing. I am sure we have all seen its effects.

I think one of our big strengths is a lack of institutional friction in
forward momentum.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

I suppose I should weight in on this.

I think the first question is: Is this the best way to go, long-run?
If it is, then we need to decide that first, and build a commitment to
"eventually get there." For this, I think core *should* get feedback on
-general, but I also think this decision needs to be made by the core
team alone based on their review of the costs involved.

If the answer is yes to the above:

The second question is: What sort of priority should this be? This is
going to be a complex decision based on other priorities (building the
codebase, etc). The community may be able to help speed things up, but
the core team will *also* need to answer this based on all the costs
involved.

Personally, I think the name change would be a good idea. My major
hesitation is that I think that it will probably take a year or two
after such a commitment to actually switch everything over unless we
want the project to suffer delays as a result. :-)

Best Wishes,
Chris Travers

Bruce,

> I think we have to decide if we really want to do this, and I don't see
> how we can do that without asking general.  I can ask people to email me
> directly and put up a web page with comments, or just set up a web page
> wiki to add comments.

What are you planning to ask -general, exactly?

Unless it's a call for volunteers, anything you ask -general at this point
will be nothing but a straw poll. You can't even regard it as a vote,
because the folks on -general don't have enough information to make an
informed decision.

When local government has the citizens vote on a bond or initiative, the
voter booklet contains the controller's estimate of the costs of the bond.
This happens *before* anyone takes a vote, because citizens can't vote to
spend city money if they don't know how much they're really spending.

If the question is, do we have enough interest in changing the name to
warrant research into what it will really "cost", then the answer is
"yes", we already have that. The only way in which a poll of -general
would be useful is if most people said they didn't want to change.

I've been waiting for the main proponents of changing the name to step up
and do that research. This will be a good litmus test of whether those
people will actually follow through to do the work required to change the
name. So far, I've seen nothing but e-mail posts.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Joshua D. Drake wrote:
>> Bruce Momjian wrote:
>>> Joshua D. Drake wrote:
>>> My basic issue is we can't use "asking for more details" to forever
>>> block this change. That's how organizations stop growing.
>>>
>> 5000 bucks and a case of whatever you drink says, that if we drop this
>> topic, PostgreSQL won't stop growing.
>
> True, but will a name change increase growth?

Probably not. Consider the number of projects out there with odd names
that are doing just fine.

- From a commercial perspective, people don't purchase PostgreSQL, they
purchase a commercial equivalent.

>
> The bottom line is I am fine with accepting whatever the group wants on
> this, but I don't want our institutional momentum to prevent a change
> if a change is overall beneficial.

That is a good point, a really good point honestly. How about we
eliminate the need for vacuum instead? There is some institutional
momentume that is preventing change that would be overall beneficial.

*** STOP ***

I do not want a thread about what I just said, I was just making a point.

> Institutional momentum can be a very
> dangerous thing. I am sure we have all seen its effects.
>

Absolutely. The:

We already tried that, it failed... mentality is a horribly destructive
thing.

I still say we need to focus on our core strengths, the "Name" isn't
relevant in that argument. Instead of expending energy on that, we
should expending energy on doing everything we can to:

Get windowing queries running
Get real partitioning
Get read only standbys

Yes, yes, yes... someone is already working on those... Really? Where is
the code... where is the review, where is the spec?

Oh and of course there is that little thing called 8.3 that isn't done
yet :)...

Seriously, let's focus on something really important versus something
that has zero technical ballast.

Sincerely,

Joshua D. Drake

> I think one of our big strengths is a lack of institutional friction in
> forward momentum.
>

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6sXIATb/zqfZUUQRAn1nAJ9gbnIUHIZsMTj0Tsu7MlfocWmKKACcDd+g
IsDaulILAj8kXNPKCyVGf6Y=
=WwaL
-----END PGP SIGNATURE-----

Josh Berkus wrote:
> Bruce,
>
>
>> I think we have to decide if we really want to do this, and I don't see
>> how we can do that without asking general. I can ask people to email me
>> directly and put up a web page with comments, or just set up a web page
>> wiki to add comments.
>>
>
> What are you planning to ask -general, exactly?
>
> Unless it's a call for volunteers, anything you ask -general at this point
> will be nothing but a straw poll. You can't even regard it as a vote,
> because the folks on -general don't have enough information to make an
> informed decision.
>

I think we should ask -general: Do you think this is a good idea? What
sort of concerns do you have? Are there any specific issues you feel
would need to be addressed?

However, I think you are right that this thread here *and* the thread on
-general are not things that should be used as a mandate for the core
team. It is simply a feedback mechanism and a way to understand what
people think about the process.

IMO, certain decisions, such as name changes, should not be made
democratically. They should be made by the body which is responsible
for governing the project (though democratic feedback can and should be
a part of the process). *If* the core team wanted to endorse such a
name change, then there would be a call for volunteers.

So here is my only concern: If the project changes names, it is going
to require a lot of grunt work. We do not want this work to cause
delays in future versions of the software. In my estimation, this may
draw out the transition time by months or even years. However, this is
not a bad thing because it means that there is greater community
awareness that the change is happening and more time to transition the
advocacy efforts.

Best Wishes,
Chris Travers

Suppose as an alternative to "changing" the name, we just start
promoting "Postgres" as an alternative version of PostgreSQL in the
course of advocacy efforts, essentially promoting it to equal footing
with PostgreSQL.

I personally don't think that this would cause any substantial
confusion, and would avoid the work involved in a full name change.
Then, down the road, if we want to, we can revisit the decision.

This would seem to give everyone what they want.

Best Wishes,
Chris Travers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Travers wrote:
> Suppose as an alternative to "changing" the name, we just start
> promoting "Postgres" as an alternative version of PostgreSQL in the
> course of advocacy efforts, essentially promoting it to equal footing
> with PostgreSQL.

Add to FAQ:

Q. What is the official name of the project?
A. PostgreSQL, but we accept Postgres as a official shortened version.

Issue resolved and hopefully more productive things actually start to
happen.

Joshua D. Drake

>
> I personally don't think that this would cause any substantial
> confusion, and would avoid the work involved in a full name change.
> Then, down the road, if we want to, we can revisit the decision.
>
> This would seem to give everyone what they want.
>
> Best Wishes,
> Chris Travers
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6svGATb/zqfZUUQRAgsuAJ95HO/9oGKUnmgG4Reb/JQc/6ry/gCggYcg
6tTpOXCAvQQgN0QOrbbzJ/Q=
=xrLz
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Josh Berkus writes:

> What are you planning to ask -general, exactly?
>
> Unless it's a call for volunteers, anything you ask -general at this point
> will be nothing but a straw poll. You can't even regard it as a vote,
> because the folks on -general don't have enough information to make an
> informed decision.

I see -general as our user base, not as a bunch of uninformed 'folks' who
wouldn't know advocacy from a hole in the ground. This is supposed to be a
transparent project, and something like this should be put to the community
at large. The most effective way we have to do that right now is the
- -general list. Consider it a way to talk to the community, and see if anyone
has any pros and cons that this list may not have thought of yet.

> I've been waiting for the main proponents of changing the name to step up
> and do that research. This will be a good litmus test of whether those
> people will actually follow through to do the work required to change the
> name. So far, I've seen nothing but e-mail posts.

You are presupposing that your list of "research/work required" is the same as
everyone elses, especially those in the "Postgres" camp. I, for example,
have always advocated a gradual approach - a FAQ item, a news release,
and we're done. Graphics, etc. can come at their own pace. The project
has been living on two names for a long time now (more, if you count all
the misspellings), it can surely survive with the same top two names swapped
in officialness for a little while.

Joshua D. Drake wrote:

> Probably not. Consider the number of projects out there with odd names
> that are doing just fine.

Are they doing fine _despite_ their name? Let's be really honest, which
project has a worse name than ours?

> I still say we need to focus on our core strengths, the "Name" isn't
> relevant in that argument. Instead of expending energy on that, we
> should expending energy on doing everything we can to:
>
> Get windowing queries running
...
> Seriously, let's focus on something really important versus something
> that has zero technical ballast.

It's not a zero-sum game. Certainly the number of people who can work
on windowing queries are a very small percentage of our community. Nobody
is advocating that we stop Tom and Simon from coding and make them
recreate our handful of graphics.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200709141356
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFG6s1YvJuQZxSWSsgRA6FwAJ4zPNesRevBXuZ2ehO/v4fK/KeejACcCbzs
O+rd+rEHGwhPO/i15MHyBZE=
=0aVO
-----END PGP SIGNATURE-----

Chris Travers wrote:
> IMO, certain decisions, such as name changes, should not be made
> democratically. They should be made by the body which is responsible
> for governing the project (though democratic feedback can and should be
> a part of the process). *If* the core team wanted to endorse such a
> name change, then there would be a call for volunteers.
>
> So here is my only concern: If the project changes names, it is going
> to require a lot of grunt work. We do not want this work to cause
> delays in future versions of the software. In my estimation, this may
> draw out the transition time by months or even years. However, this is
> not a bad thing because it means that there is greater community
> awareness that the change is happening and more time to transition the
> advocacy efforts.

There seems to be a lot of valid concern about having manpower for this.
I am willing to take the lead and form a team to accomplish this goal if
we decide we want it. I did the Win32 port so this should be doable.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

Chris Travers wrote:
> Suppose as an alternative to "changing" the name, we just start
> promoting "Postgres" as an alternative version of PostgreSQL in the
> course of advocacy efforts, essentially promoting it to equal footing
> with PostgreSQL.
>
> I personally don't think that this would cause any substantial
> confusion, and would avoid the work involved in a full name change.
> Then, down the road, if we want to, we can revisit the decision.
>
> This would seem to give everyone what they want.

Yea, that is another approach, making "Postgres" as a nickname more
visible. Can anyone see a good way to do that?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Chris Travers wrote:
>> Suppose as an alternative to "changing" the name, we just start
>> promoting "Postgres" as an alternative version of PostgreSQL in the
>> course of advocacy efforts, essentially promoting it to equal footing
>> with PostgreSQL.
>>
>> I personally don't think that this would cause any substantial
>> confusion, and would avoid the work involved in a full name change.
>> Then, down the road, if we want to, we can revisit the decision.
>>
>> This would seem to give everyone what they want.
>
> Yea, that is another approach, making "Postgres" as a nickname more
> visible. Can anyone see a good way to do that?

Amend FAQ... that's all.

Most people use it anyway ;)

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6tD9ATb/zqfZUUQRAuI3AJ0QDongwtaR0cF/kH3HtAAH03ws7gCeNo/4
/vH15NdEfOKmTeiDXxw4mxw=
=NFbO
-----END PGP SIGNATURE-----

Joshua D. Drake wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Bruce Momjian wrote:
> > Chris Travers wrote:
> >> Suppose as an alternative to "changing" the name, we just start
> >> promoting "Postgres" as an alternative version of PostgreSQL in the
> >> course of advocacy efforts, essentially promoting it to equal footing
> >> with PostgreSQL.
> >>
> >> I personally don't think that this would cause any substantial
> >> confusion, and would avoid the work involved in a full name change.
> >> Then, down the road, if we want to, we can revisit the decision.
> >>
> >> This would seem to give everyone what they want.
> >
> > Yea, that is another approach, making "Postgres" as a nickname more
> > visible. Can anyone see a good way to do that?
>
> Amend FAQ... that's all.
>
> Most people use it anyway ;)

Is this something we can do now, no matter the outcome of the discussion?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Chris Travers wrote:
>> IMO, certain decisions, such as name changes, should not be made
>> not a bad thing because it means that there is greater community
>> awareness that the change is happening and more time to transition the
>> advocacy efforts.
>
> There seems to be a lot of valid concern about having manpower for this.
> I am willing to take the lead and form a team to accomplish this goal if
> we decide we want it. I did the Win32 port so this should be doable.

What the heck Bruce, post to -general but make sure you post to the
following as well:

brasil-usuarios Brazilian Portuguese PostgreSQL community
Yahoo Groups Chinese PostgreSQL community
pgsql-nl-algemeen Dutch PostgreSQL community
pgsql-eu-general European Union PostgreSQL community
pgsql-fr-generale French PostgreSQL community
pgsql-de-allgemein German PostgreSQL community
postgresql_indo Indonesian PostgreSQL community
http://postgresql.linuxtime.it/ Italian PostgreSQL community
pgsql-jp Japanese PostgreSQL community
pgsql-ru-general Russian PostgreSQL community
pgsql-es-ayuda Spanish PostgreSQL community
pgsql-tr-genel Turkish PostgreSQL community
persianpug Persian PostgreSQL community
pdxpug Portland, USA
sfpug San Francisco, USA
sydpug Sydney, Australia

Let's just get it out there.

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6tFrATb/zqfZUUQRAntbAJ94xiJlM+Yqh7cbqoaUPY/4ac3diwCfQ6xE
RMyEjUyXp4N8K7UILsxQKT4=
=t3Sr
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Joshua D. Drake wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Bruce Momjian wrote:
>>> Chris Travers wrote:
>>>> Suppose as an alternative to "changing" the name, we just start
>>>> promoting "Postgres" as an alternative version of PostgreSQL in the
>>>> course of advocacy efforts, essentially promoting it to equal footing
>>>> with PostgreSQL.
>>>>
>>>> I personally don't think that this would cause any substantial
>>>> confusion, and would avoid the work involved in a full name change.
>>>> Then, down the road, if we want to, we can revisit the decision.
>>>>
>>>> This would seem to give everyone what they want.
>>> Yea, that is another approach, making "Postgres" as a nickname more
>>> visible. Can anyone see a good way to do that?
>> Amend FAQ... that's all.
>>
>> Most people use it anyway ;)
>
> Is this something we can do now, no matter the outcome of the discussion?
>

Why not? I have zero problem with the FAQ amendment I suggested.

Q. What is the official name of the project?
A. PostgreSQL, but we accept Postgres as an official shortened version.

I have not seen a single argument against the above and it has been
mentioned by other people (although the wording my be slightly different).

Sincerely,

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6tIDATb/zqfZUUQRAgWFAJ9rS7URFx2qM2hgLeurgPXYQztHIACeOFHr
99RllyqfcpM+kSlIzlDgd5g=
=xhj1
-----END PGP SIGNATURE-----

On 9/14/07, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> > Is this something we can do now, no matter the outcome of the discussion?
> >
>
> Why not? I have zero problem with the FAQ amendment I suggested.
>
> Q. What is the official name of the project?
> A. PostgreSQL, but we accept Postgres as an official shortened version.
>
> I have not seen a single argument against the above and it has been
> mentioned by other people (although the wording my be slightly different).

Agreed, I don't think anyone has contested the FAQ change.

--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
Edison, NJ 08837 | http://www.enterprisedb.com/

Joshua D. Drake wrote:
> >>>> This would seem to give everyone what they want.
> >>> Yea, that is another approach, making "Postgres" as a nickname more
> >>> visible. Can anyone see a good way to do that?
> >> Amend FAQ... that's all.
> >>
> >> Most people use it anyway ;)
> >
> > Is this something we can do now, no matter the outcome of the discussion?
> >
>
> Why not? I have zero problem with the FAQ amendment I suggested.
>
> Q. What is the official name of the project?
> A. PostgreSQL, but we accept Postgres as an official shortened version.
>
> I have not seen a single argument against the above and it has been
> mentioned by other people (although the wording my be slightly different).

OK, FAQ wording updated from:

! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, and is also sometimes
! referred to as just <I>Postgres</I>. An audio file is available in

to:

! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, but can also be
! referred to as simply <I>Postgres</I>. An audio file is available in

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On Sep 14, 2007, at 11:25 AM, Joshua D. Drake wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Bruce Momjian wrote:
>>
>> Is this something we can do now, no matter the outcome of the
>> discussion?
>>
>
> Why not? I have zero problem with the FAQ amendment I suggested.
>
> Q. What is the official name of the project?
> A. PostgreSQL, but we accept Postgres as an official shortened
> version.
>
> I have not seen a single argument against the above and it has been
> mentioned by other people (although the wording my be slightly
> different).

It seems like a good FAQ addition. The only downside I can see
to adopting the two names as equally valid ways to describe PG is:

Q. So... what is "QL" then?
A. Aaaarrrrgggghhhh!

Cheers,
Steve

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Joshua D. Drake wrote:
>>>>>> This would seem to give everyone what they want.

>> I have not seen a single argument against the above and it has been
>> mentioned by other people (although the wording my be slightly different).
>
> OK, FAQ wording updated from:
>
> ! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, and is also sometimes
> ! referred to as just <I>Postgres</I>. An audio file is available in
>
> to:
>
> ! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, but can also be
> ! referred to as simply <I>Postgres</I>. An audio file is available in
>

Cool, now let's move forward :)

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6tSOATb/zqfZUUQRAocnAKCcfSaUbyeNFykWV0L4ieesZryZjACdEj7I
UIA8fulps10E+QbWGuKiMHE=
=DMHi
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> I have not seen a single argument against the above and it has been
>> mentioned by other people (although the wording my be slightly
>> different).
>
> It seems like a good FAQ addition. The only downside I can see
> to adopting the two names as equally valid ways to describe PG is:
>
> Q. So... what is "QL" then?
> A. Aaaarrrrgggghhhh!

I humbly submit that those who would actually ask that, just be kindly
asked to move on to MySQL and leave us alone.

Sincerely,

Joshua D. Drake

>
> Cheers,
> Steve
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6tTiATb/zqfZUUQRAsd+AKCAt3Rfqj40JXWCQGoFqs2rzkSg8gCgqeKW
wklfphJmutcfwOTKKJ3JDbc=
=SwLj
-----END PGP SIGNATURE-----

Bruce Momjian wrote:
> Joshua D. Drake wrote:
> > >>>> This would seem to give everyone what they want.
> > >>> Yea, that is another approach, making "Postgres" as a nickname more
> > >>> visible. Can anyone see a good way to do that?
> > >> Amend FAQ... that's all.
> > >>
> > >> Most people use it anyway ;)
> > >
> > > Is this something we can do now, no matter the outcome of the discussion?
> > >
> >
> > Why not? I have zero problem with the FAQ amendment I suggested.
> >
> > Q. What is the official name of the project?
> > A. PostgreSQL, but we accept Postgres as an official shortened version.
> >
> > I have not seen a single argument against the above and it has been
> > mentioned by other people (although the wording my be slightly different).
>
> OK, FAQ wording updated from:
>
> ! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, and is also sometimes
> ! referred to as just <I>Postgres</I>. An audio file is available in
>
> to:
>
> ! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, but can also be
> ! referred to as simply <I>Postgres</I>. An audio file is available in

I trimmed down the paragraph a little:

<P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, but can also be
referred to as simply <I>Postgres</I>, particularly in conversation.
(For those curious about how to say "PostgreSQL", an
<a href="http://www.postgresql.org/files/postgresql.mp3">audio file</a>
is available.)</P>

Changes?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

On 9/14/07, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> I humbly submit that those who would actually ask that, just be kindly
> asked to move on to MySQL and leave us alone.

:)

--
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
Edison, NJ 08837 | http://www.enterprisedb.com/

Bruce,

> <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, but can also be
> referred to as simply <I>Postgres</I>, particularly in conversation.
> (For those curious about how to say "PostgreSQL", an
> <a href="http://www.postgresql.org/files/postgresql.mp3">audio
> file</a> is available.)</P>

Looks good to me.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bruce Momjian wrote:
> Bruce Momjian wrote:
>> Joshua D. Drake wrote:

> I trimmed down the paragraph a little:
>
> <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, but can also be
> referred to as simply <I>Postgres</I>, particularly in conversation.
> (For those curious about how to say "PostgreSQL", an
> <a href="http://www.postgresql.org/files/postgresql.mp3">audio file</a>
> is available.)</P>
>
> Changes?
>

Looks great to me.

Joshua D. Drake

- --

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 24x7/Emergency: +1.800.492.2240
PostgreSQL solutions since 1997 http://www.commandprompt.com/
UNIQUE NOT NULL
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG6tegATb/zqfZUUQRAlokAJ0UzX98zBZkhp87xYo3xyMLoAH0qwCfWh/2
q0E3DvC8qQ5zqx1fU5GEwAY=
=5rR5
-----END PGP SIGNATURE-----

Greg,

> Consider it a way to talk to the community,
> and see if anyone has any pros and cons that this list may not have
> thought of yet.

Sure. But that's still not taking a "vote", which is what I want to make
clear, and doesn't significantly move forward actually doing a name
change.

> You are presupposing that your list of "research/work required" is the
> same as everyone elses, especially those in the "Postgres" camp. I, for
> example, have always advocated a gradual approach - a FAQ item, a news
> release, and we're done.

And, again, I regard this whole viewpoint as myopically unrealistic. What
sense does it make to have Postgres as the "official" name if the packages
are still named "PostgreSQL", the documentation still says "PostgreSQL",
and the website is still at www.postgresql.org?

Really, you're not proposing anything other than the "official nickname"
approach, which I agree doesn't require any real work. But it's not
changing our "official name".

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

2007-09-14_14:06:22-0400 Greg Sabino Mullane <greg(at)turnstep(dot)com>:

> Are they doing fine _despite_ their name? Let's be really honest, which
> project has a worse name than ours?

XFCE

--
Ron Peterson
https://www.yellowbank.com/

> 2007-09-14_14:06:22-0400 Greg Sabino Mullane <greg(at)turnstep(dot)com>:
>
>> Are they doing fine _despite_ their name? Let's be really honest, which
>> project has a worse name than ours?

Have you ever tried telling your boss that you're going to use "The Gimp" to
design the new corporate logo?

And then there's the saga of Mozilla a.k.a. Firefox a.k.a. Iceweasel or
whatever it is this week.

And of course there's "don't say OpenOffice" OpenOffice.org.

Whatever the marketing people tell you, software names really just don't
matter much.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

Am 14.09.2007 um 21:51 schrieb Gregory Stark:

>> 2007-09-14_14:06:22-0400 Greg Sabino Mullane <greg(at)turnstep(dot)com>:
>>
>>> Are they doing fine _despite_ their name? Let's be really honest,
>>> which
>>> project has a worse name than ours?
>
> Have you ever tried telling your boss that you're going to use "The
> Gimp" to design the new corporate logo?
>
> And then there's the saga of Mozilla a.k.a. Firefox a.k.a.
> Iceweasel or
> whatever it is this week.
>
> And of course there's "don't say OpenOffice" OpenOffice.org.
>
> Whatever the marketing people tell you, software names really just
> don't
> matter much.

Great examples, but wrong conclusion I believe.

Gimp is a perfect example of a Project where the name
is part of the problem.

Firefox became successful incidentally at the time when
the monsterous Mozilla was left behind. The Iceweasel
is a result of being too strict in the way they take
care for the name, but that does not make the general
direction worse. If the marketing people from Firefox
foundation would take time to understand Debian better,
they would allow them to do their packaging and let
them use the common name. And they probably will some
day. Especially as Ubuntu is becoming more and more
the overall preferred desktop distribution.

And OpenOffice, well, this example is perfect because
it is exactly the same case. Never heard anybody say
OpenOffice.org. Thats ridiculous. .org <-> QL ?

Bye, Christian

Hallo,

verfolgt hier eigentlich noch jemand den
"change the name" thread auf advocacy?
Als David Fetter letzte Woche den Hinweis
gab konnte ich nur den Kopf schütteln,
aber mittlerweile macht es mir Spaß.

Nachdem die lokalen Communities in Frank-
reich, Italien und Brasilien immer wieder
als Gegner einer Namesänderung genannt
werden, da Postgres in den romanischen
Sprachen nicht leichter auszusprechen
sei als PostgreSQL, frage ich mich, was
die deutsche Community dazu sagt?

Anfang der weitergeleiteten E-Mail:

> Von: Bruce Momjian <bruce(at)momjian(dot)us>
> Datum: 14. September 2007 20:32:34 MESZ
...
> OK, FAQ wording updated from:
>
> ! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, and is also
> sometimes
> ! referred to as just <I>Postgres</I>. An audio file is
> available in
>
> to:
>
> ! <P>PostgreSQL is pronounced <I>Post-Gres-Q-L</I>, but can
> also be
> ! referred to as simply <I>Postgres</I>. An audio file is
> available in

Gruß, Christian