PEAR shifting to git

Hi all, Time for another round of discussion on this :) I'm not plugged into php-internals, but came across http://news.php.net/php.internals/58549. So, to date, we've migrated a bunch of packages - mostly unmaintained packages. The process is workable, but we do tend to lose tags in some cases; and by goodness it's slow. A few people have commented that "we'll just get picked up by the php migration". Personally, I'd like to make this either explicit or come up with our own migration outside of the php core effort. My reasoning behind this: 1) There are hundreds of PEAR packages; and if any of them go wrong in the migration process, it means that David / others have to spend a lot of time and effort fixing up problems for +6 months. That's assuming that an infrequent committer comes along and even knows how to talk to the folks who have run the migration. 2) It's a lot of coordinated effort - we would have to update all of the project links as they successfully migrate, and make sure all pear committers were aware of this change. Internally, we've lost of a lot of contributors who could help that coordination over the last few years. We would have to get our folks deeply involved in all discussions and helping out with the migration. David, what's the latest thinking around things-that-live-in-php-svn-but-arent-PHP? PEAR-dev folks - what's the preferred plan?