Tom,
> Hmm ... seems like the big question is not "where to keep them" but
> "who's gonna maintain them" ... without active maintenance they're
> just dead bits wherever they're stored, because MySQL and Postgres
> are both moving targets.
>
> These tools are a not insignificant part of our Plan for World
> Domination ;-) so it would be good if somebody stepped up to the
> plate and volunteered to take care of 'em. Anybody?
Well, I'm planning on updating my2pg. Of the 3 packages available (one from
Thomas Lockhart, one from Donna Pavlusinc, and my2pg, originally from Max
Rudensky), it is the most functional. That's kind of a shame, since the Perl
is pretty sloppy, but it does work.
I'd be happy to take the lead as maintainer of my2pg. But, I want to move it
to pgFoundry (due for launch as soon as I get my other 10 super-urgent tasks
out of the way) , and take it out of /contrib. I feel pretty strongly
that it will be more visible and easier to maintain on its own than in
/contrib.
--
Josh Berkus
Aglio Database Solutions
San Francisco
