Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id E8E369FB7C9 for ; Tue, 12 Jun 2007 05:07:12 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 38990-06 for ; Tue, 12 Jun 2007 05:07:02 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from developer.pgadmin.org (developer.pgadmin.org [63.246.23.140]) by postgresql.org (Postfix) with ESMTP id 9456B9FB77D for ; Tue, 12 Jun 2007 05:07:02 -0300 (ADT) Received: from [172.24.32.116] ([62.232.55.118]) (authenticated bits=0) by developer.pgadmin.org (8.13.8/8.13.8) with ESMTP id l5C7og8B002881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 12 Jun 2007 07:50:44 GMT Message-ID: <466E5422.9070102@postgresql.org> Date: Tue, 12 Jun 2007 09:06:58 +0100 From: Dave Page User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: pgsql-www@postgresql.org Subject: Moving the website project from GBorg Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/40 X-Sequence-Number: 12079 I've created a pgweb project on pgFoundry to migrate from GBorg to. The original idea was to migrate the CVS and just lose the bugs etc. as they're largely out of date at the moment anyway. We can make an effort to be more organised with the more usable pgFoundry trackers in the future. Magnus has since come up with an idea though, that instead of using CVS on pgFoundry, we move the website CVS to an SVN repository actually on wwwmaster to remove the dependency on pgFoundry for the operation of the website. This seems like a fine idea to me - any other thoughts or ideas? /D