X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 5A6B69DC85A for ; Mon, 16 Jan 2006 14:24:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 08182-01 for ; Mon, 16 Jan 2006 14:24:41 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by postgresql.org (Postfix) with ESMTP id F27C99DC81F for ; Mon, 16 Jan 2006 14:24:38 -0400 (AST) Received: from [192.168.1.100] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id k0GIFLsJ010571; Mon, 16 Jan 2006 10:15:22 -0800 Message-ID: <43CBE53E.5090106@commandprompt.com> Date: Mon, 16 Jan 2006 10:26:06 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: gforge-admins@pgfoundry.org, pgsql-www@postgresql.org Subject: PgFoundry Move Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Mon, 16 Jan 2006 10:15:23 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.065 required=5 tests=[AWL=0.065] X-Spam-Score: 0.065 X-Spam-Level: X-Archive-Number: 200601/123 X-Sequence-Number: 9311 Hello, In the essence of being efficient I would like to suggest that we move Pgfoundry. I know we have been trying to "migrate" for what seems like forever but maybe it is time we just up and move the whole site :). I would like to again offer Command Prompt's services in hosting pgFoundry. Some key benefits to moving the system to CMD: 1. You can call us 2. You can call us at 3:00 am 3. We have service level monitoring 4. We have a lot of bandwidth 5. All our stuff is on natural gas conditioned power generators We have proven to be very stable with the Buildfarm and with the archives. With the only recent problem with either not being at the hands of CMD, (gentle poke at Andrew). The longest outage we have had in the last 24 months is four hours for a single machine that we had to recover from backup. The longest outage we have had that was global in the last 24 months (that wasn't scheduled) was 90 minutes when we lost a nic in one of our firewalls. We did recently have a scheduled outage of 4.5 hours but that was from midnight to 4:30 while we upgraded some power facilities. The only change that we would require would be to move the system to Linux. This should be a very minor change in general and will probably require very if any work on the Gforge end. Thoughts, Flames, better suggestions? Sincerely, Joshua D. Drake -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PLphp, PLperl - http://www.commandprompt.com/