Re: The Name Game: postgresql.net vs. pgfoundry.org

David Garamond <lists(at)zara(dot)6(dot)isreserved(dot)com> writes:

> Also, we're targetting the developers right? Please do not consider
> ourselves as being too stupid to differentiate between postgresql.org and
> postgresql.net...

I can never remember whether the current site is postgresql.{com,org,net} even
now. Making postgresql.net one thing and postgresql.org another thing is a
recipe for confusion.

I would say follow the same model as modules.apache.org, pear.php.net, etc.

I don't understand the "too long" complaint at all. a) Nobody's forcing us to
use a subdomain for each project, and b) nobody's actually going to type
"slony.gborg.postgres.org" or "gborg.postgres.org/slony" anyways. They'll go
to "gborg.postgres.org" and type "slony" into the search box.

In any case, complaining about "too long" when each component means something
specific only means you want to leave off one of those meanings. Either the
name of the project, the distinction from the main site, or the association
with postgres.

Ie, Using "postgres.org" vs "postgres.net" or leaves the user with no clue
which site he's on or even that there is another site. Using something like
"pgfoundry.com" leaves the user with no idea the web site is related to the
postgres.org web site.

--
greg