X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 338869FB24A for ; Sun, 3 Sep 2006 23:55:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 11368-02 for ; Mon, 4 Sep 2006 02:55:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id 0FFA69FB228 for ; Sun, 3 Sep 2006 23:55:17 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id D480930E31; Mon, 4 Sep 2006 04:55:14 +0200 (MET DST) From: Christopher Browne X-Newsgroups: pgsql.hackers Subject: Re: gBorg status? Date: Sun, 03 Sep 2006 22:55:03 -0400 Organization: cbbrowne Computing Inc Lines: 57 Message-ID: <87d5acnxx4.fsf@wolfe.cbbrowne.com> References: <608xl5yny7.fsf@dba2.int.libertyrms.com> <20060902224155.GN84229@nasby.net> <878xl17jru.fsf@wolfe.cbbrowne.com> <44FA4E7B.4080400@commandprompt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) Cancel-Lock: sha1:mESMrLnpzDwE7nj00gk2PZcYp6I= To: pgsql-hackers@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.273 tagged_above=0 required=5 tests=INFO_TLD X-Spam-Level: * X-Archive-Number: 200609/286 X-Sequence-Number: 89815 The world rejoiced as jd@commandprompt.com ("Joshua D. Drake") wrote: > Christopher Browne wrote: >> Oops! jim@nasby.net ("Jim C. Nasby") was seen spray-painting on a wall: >>> On Thu, Aug 31, 2006 at 10:33:36AM -0400, Chris Browne wrote: >>>> What's up there? It has been down all week. >>>> >>>> We're trying to get the Slony-I 1.2 release out, so we can then >>>> migrate over to pgFoundry. But that doesn't working terribly well >>>> when gBorg's down... >>> Speaking of which, what's the status of the migration tools? Is that >>> ball still in Larry's court? >> Which migration tools? Were there migration tools specific to >> gBorg->pgFoundry? Or something else? > > There was, kind of, sort of. AFAIK they are dead and gone and the > current method of thought on Gborg is here: > > http://archives.postgresql.org/pgsql-general/2006-08/msg01167.php That seems fine to me. We already had a plan set up for Slony-I that was not too dissimilar. To wit... - There already is a project set up at pgFoundry, and fairly much all committers at gBorg are members of the project at pgFoundry - Downloads are being handled from pgFoundry - We figured we'd migrate outstanding bugs to pgFoundry by hand - We figured we'd migrate copies of old mailing list archives - We figured we'd announce the deaths of old lists, and suggest subscribing to the new ones - We figured there would be some ability to copy CVS over fairly losslessly The *big* steps are moving email and CVS. I really haven't yet heard a peep yet that hasn't been third-hand about the gBorg outage, after it has been out for over a week now. To say that's displeasing is something of an understatement. It certainly leaves me in no mood to want to keep any services I care to actually have running hosted on gBorg. The fact that it has been out for a week, without any public comment being made, certainly gives me pause. I *HOPE* that we can still recover CVS and email. Question about email: Do we need to migrate the old mailing list archives before setting up new lists on pgFoundry? Or could I set up a "slony1-discuss" at pgFoundry, fairly immediately, and migrate in old archives later? [Possibly helpful factor: It's now September, and the last gBorg traffic was dated in August, so we may not need to mix months...] -- (format nil "~S@~S" "cbbrowne" "gmail.com") http://linuxdatabases.info/info/x.html Who needs fault-tolerant computers when there's obviously an ample market of fault-tolerant users?