The next wave of project migrations begins tonight. This last couple of months have been quite a learning experience. Things that seemed easy and straightforward became impossibly complicated, and impossible things went just fine. I'm sure the next few months will bring more of the same. We're learning as we go, and as a result we made a couple of minor changes in the plan:
1. Due to the time needed to do CVS to SVN conversions, the Kenai team asked to get those knocked out first, so this wave will be the first 200 CVS projects requested and the maven2 repository.
2. To reduce the downtime for projects during migration we decided to leave mailing list archives and uploaded documents on the old site for a few weeks. You will have read-only access to them, you'll be able to use the mailing lists on the new site as soon as the projects go live and be able to upload new or updated documents to the new site immediately as well. The email and doc archives will be backfilled on the new site in January, and then redirects for project pages will be put in place.
The most frustrating thing for both you and me has been the request process. We tried to put together an automated system to process the requests as they came in, but it just didn't work. The Kenai team ended up needing different data on the projects from me, and the system we set up ended up being useless and we switched to brute force. Next time I need to move a few thousand projects from one forge to another, I'll get it right the first time, I promise.
Meanwhile, I'm still getting some migration requests coming in. I'm processing that list and we will move those projects after we receive the final tarball from Collab. What this means for those projects is they will be dark for a few days while we wait for delivery of the final data from Collab. When we receive that data we will upload them on the new site and put the redirects in place.