Skip site navigation (1) Skip section navigation (2)

Re: Why is Gborg still listed?

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: pgsql-www(at)postgresql(dot)org
Subject: Re: Why is Gborg still listed?
Date: 2004-10-30 18:02:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-www
On Sat, 30 Oct 2004, Joshua D. Drake wrote:

>> Its not the project admin's that is at issue ... if you would like to 
>> become one of the PgFoundry admin, please talk to Josh Berkus about it, but 
>> right now, its on the 'PgFoundry' side that the bottleneck is ... unless, 
>> of course, you are advocating scrapping/deleting off the trouble tickets 
>> and such on the gborg project side, and having each project start from 
>> scratch?
> Of course not :) That was the point of the Read only access. No loss of data, 
> but requires movement to the new
> You could even have a a that brings up the old 
> gborg site if you want.
>> Not 100% certain what your problem is though ... ppl are visiting both 
>> sites, and finding what they are looking for ... is there a specific reason 
>> you feel that there is a panic to move ppl from GBorg -> PgFoundry?
> Well my problem is:
> 1. Lack of consistency.
> 2. Large amounts of traffic being pushed to the "old" site via multiple 
> places on the www site.
> 3. The slow migration :).
> I am not blaming anyone, just trying to get things moving.

Do you have the time that you can allocate to helping with the migration 
stuff?  It isn't lack of desire to move things that is holding things up, 
its finding the time to scheduale/do it :)

Marc G. Fournier           Hub.Org Networking Services (
Email: scrappy(at)hub(dot)org           Yahoo!: yscrappy              ICQ: 7615664

In response to


pgsql-www by date

Next:From: Joshua D. DrakeDate: 2004-10-30 18:06:21
Subject: Re: Why is Gborg still listed?
Previous:From: Joshua D. DrakeDate: 2004-10-30 17:50:32
Subject: Re: Why is Gborg still listed?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group