Re: [HACKERS] Collaboration Tool Proposal - Mailing list pgsql-www

From Josh Berkus
Subject Re: [HACKERS] Collaboration Tool Proposal
Date
Msg-id 200402261107.03351.josh@agliodbs.com
Whole thread Raw
In response to Collaboration Tool Proposal  (Josh Berkus <josh@agliodbs.com>)
List pgsql-www
Jeroen,

> I for one am willing to try this in the near term.

Great!

> I've got an external
> domain (pqxx.tk) pointing to the libpqxx page on GBorg, and moving it over
> to a new URL is child's play.  My main worry is transition management:
>
>  - How will mailing list subscribers be affected?
>  - How will CVS users be affected?
>  - Can the mailing list archives be moved over?
>  - Where will my old bug reports and corresponding discussions go?
>  - Can FAQ entries be copied over automatically?
>  - Is there a way of migrating these services one by one?

Either Tim, Chris, or both will help with this.    If we can't migrate
everything by script, we'll have to give up on the idea.  Some projects, like
JDBC, have huge mailing list archives.

I think you would want to do the migration "all at once", though.   Putting up
a page explaining that the CVS is on GForge but the mailing lists are non
GBorg for a week would confuse the heck out of people, I think.

Since both systems are based on postgresql databases, migration should be the
simple expedient of writing the right Perl/PHP+SQL script.

> If it takes some scripting and/or programming to do some of this, I'm
> willing to help insofar as I have time.

Terrific!

--
-Josh Berkus
 Aglio Database Solutions
 San Francisco


pgsql-www by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [HACKERS] Collaboration Tool Proposal
Next
From: Joseph Tate
Date:
Subject: Re: [HACKERS] Collaboration Tool Proposal