X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 424D1D1BAC8 for ; Tue, 9 Mar 2004 21:22:24 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 66719-01 for ; Tue, 9 Mar 2004 17:22:20 -0400 (AST) Received: from bramble.mmrd.com (unknown [65.217.53.66]) by svr1.postgresql.org (Postfix) with ESMTP id E87EBD1DAC4 for ; Tue, 9 Mar 2004 17:22:14 -0400 (AST) Received: from thorn.mmrd.com (thorn.mmrd.com [172.25.10.100]) by bramble.mmrd.com (8.12.8/8.12.8) with ESMTP id i29KsxcM030051; Tue, 9 Mar 2004 15:54:59 -0500 Received: from gnvex001.mmrd.com (gnvex001.mmrd.com [192.168.3.55]) by thorn.mmrd.com (8.11.6/8.11.6) with ESMTP id i29LM3l20795; Tue, 9 Mar 2004 16:22:03 -0500 Received: from camel.mmrd.com ([172.25.5.213]) by gnvex001.mmrd.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id FVMAWY3H; Tue, 9 Mar 2004 16:22:00 -0500 Subject: Re: pgFoundry WAS: On pgweb project From: Robert Treat To: Josh Berkus Cc: Dave Page , pgsql-www@postgresql.org In-Reply-To: <200403091203.04152.josh@agliodbs.com> References: <03AF4E498C591348A42FC93DEA9661B889F5DD@mail.vale-housing.co.uk> <200403091203.04152.josh@agliodbs.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 09 Mar 2004 16:22:02 -0500 Message-Id: <1078867322.3204.388.camel@camel> Mime-Version: 1.0 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/88 X-Sequence-Number: 3904 On Tue, 2004-03-09 at 15:03, Josh Berkus wrote: > Dave, > > > Did I miss a thread? I can't find anything about a pgFoundry in my > > archives. I assume it's Gforge based? > > Yes. It's the whole GForge discussion on Hackers. > > Hmmmm ... let me apologize for not directly addressing this list about the > "final plans" for GForge/pgFoundry, and try to remedy the situation now. I > spent so much time discussing this on Hackers that I failed to notice that > this list got cut off the CC before we reached a conclusion. > > Marc, Chris Ryan, Andrew D. and the Core *have* been in the loop on this. > > We've set up a new host, www.pgfoundry.org. This will hold our GForge > installation, to which we will be migrating GBorg projects as their owners > are ready to do so. We've already stopped accepting new GBorg projects. > Migration is painless and almost 100% automatic. > > Within 1.5 weeks we should be offficially launching pgFoundry. Among other > things, at that time we'll be launching a contest to "re-theme" the foundry. > When portal is done, we can also discuss using some of the headers and > includes from portal to support site integration. > > Anything else you need to know? > Are you planning on running this along with the current website projects (www/techdocs/etc...) or will this be independent? ie. There was previous discussion of a projects.postgresql.net domain to be used for this, is that deprecated? Also for theming, shouldn't it use the main postgresql.org css ? Robert Treat -- Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL