public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Greg Sabino Mullane <[email protected]>
Cc: [email protected]
Subject: Re: Update to FAQ
Date: Tue, 8 Apr 2008 20:46:23 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> 
> Joshua proposed:
> 
> !    In November 2007 a classic Open Source debate took place on whether
> !    or not to change the name of the PostgreSQL project to Postgres.
> !    It was decided that Postgres would be an officially recognized
> !    nickname but that the name would remain PostgreSQL. Postgres was
> !    the original name of the project at Berkeley and is strongly
> !    preferred over other nicknames. If you find 'PostgreSQL' hard
> !    to pronounce, call it 'Postgres' instead.
> !
> 
> The debate has certainly spread well before (and after) November 2007.
> Not sure what makes it a "classic Open Source debate" either. Because
> it was debated in the open? I think the "decision" was basically
> Core's punting of making the tough but necessary decision to make
> the project name pronounceable once again (if I can add some spin
> of my own :). If we are going to say "It was decided", we need
> to state who (Core) actually did the decreeing / deciding.
> 
> In case it wasn't clear, I'm not in support of changing the FAQ
> as proposed above.

In looking at it now I see the Berkeley sentence isn't necessary so I
just remove it.  (It was copied from the documentation.)  New text:

    <P>Postgres is a widely-used nickname for PostgreSQL.  If you find
    'PostgreSQL' hard to pronounce, call it 'Postgres' instead.</P>

Shorter is better in the FAQ.

-- 
  Bruce Momjian  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Update to FAQ
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox