Re: Why is Gborg still listed?

>
> 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 projects.postgresql.org.
You could even have a a projects.postgresql.org/old 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.

Sincerely,

Joshua D. Drake

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

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL