Linus said (on a different thread) that he didn't think that he had the knowledge to do this. I've got (most of) the knowledge, but not the time to do it. I've run the ArgoEclipse repo through git2svn and have a local git repo of it, but it needs to have the kits and other large binary artifacts pruned out of it before it gets pushed to Github. This would likely need to be done for any repo which has (or had?) large binaries in it.
I assembled an authors list to use in the conversion process. By default, I mapped usernames to tigris email addresses, e.g. [email protected]. People can either add those addresses to the Github accounts or they can be replaced with current email addresses. I'd be willing to invest a little time to convert one of the Python tools that I used for Google Code -> Github conversion as long as it didn't get too involved. I also investigated issues a little bit and it's pretty easy to get a complete XML dump of all the project issues. There doesn't seem to be any ready made tool to convert them to Github format, but it probably wouldn't be too hard to piece something together using one of the other tools. Wiki conversion is something else that someone would need to tackle. Re-hosting (at least some of) the release kits is another thing to add to the list. I'm at Google I/O this week, but I can try to spend a little time progressing some of the basic items next week and start assembling a list of steps to be followed to convert a project. Speaking of which what other things should be added to the list of things to be done? Tom ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=3119806 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
