From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: The Name Game: postgresql.net vs. pgfoundry.org |
Date: | 2004-03-12 15:14:06 |
Message-ID: | 4051D3BE.8030102@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Dave Page wrote:
>
>
>
>
>>-----Original Message-----
>>From: Andreas Pflug [mailto:pgadmin(at)pse-consulting(dot)de]
>>Sent: 12 March 2004 13:57
>>To: josh(at)agliodbs(dot)com
>>Cc: pgsql-hackers(at)postgresql(dot)org
>>Subject: Re: [HACKERS] The Name Game: postgresql.net vs. pgfoundry.org
>>
>>
>>Isn't gforge a pgsql related project itself?
>>So I'd suggest:
>>
>>www.postgresql.org -> main PostgreSQL site
>>gforge.postgresql.org -> gforge interface site
>><projectname>.postgresql.org -> gforge hosted projects
>>
>>
>
>The problem with that approach is that our 'official' sites then get
>lost amongst the project sites.
>
>We need some distinction between the core project sites and other
>project sites - istm that a different domain is the only way to do that.
>
>
>
(breaking previous rule) I agree.
Also, the gforge people would prefer us *not* to use a name that
includes gforge, because of the risk of confusion. That's how we came up
with "pgfoundry" in the first place.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-03-12 15:14:25 | Re: [HACKERS] The Name Game: postgresql.net vs. pgfoundry.org |
Previous Message | Tom Lane | 2004-03-12 15:04:20 | Re: index leaks ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-03-12 15:14:25 | Re: [HACKERS] The Name Game: postgresql.net vs. pgfoundry.org |
Previous Message | Dave Page | 2004-03-12 15:10:31 | FW: [webmaster] problem with gborg on Emacs-W3 browser |