+1 for the easy approach. It is not that huge of a project that it needs to be split up in modules or so.
In fact I'd only migrate wicketstuff-core, something like I did about a year ago. https://github.com/wicketpit/wicketstuff-core But ended up in having no fun in merging the new commits that cam in on the svn. I hope the merging part will be more fun as the main repo will be in git. The other projects besides the core project I'd leave were they are. If someone comes up with the will to maintain them a way will be found for migration. mf Am 16.12.2010 um 17:11 schrieb Igor Vaynberg: > i think keeping things in the same repo is the easiest, it also allows > us to use github's built in svn repo import function. > > -igor > > On Thu, Dec 16, 2010 at 6:04 PM, Martijn Dashorst > <martijn.dasho...@gmail.com> wrote: >> I've claimed an organization for Wicket Stuff: >> https://github.com/wicketstuff and we can create multiple repos under >> that, and create and assign different teams to the repositories. How >> we organize things is just a matter of this debate ;) >> >> I have put a redirect from apache extras -> wicket stuff -> github, so >> we don't get fragmented. I'm going to look into doing something >> similar to the sf.net project (but after we have moved everything >> over) >> >> Next we need to discuss how to migrate everything over. >> >> Are we going to move whole wicketstuff over to one repo, or a git repo >> per project (where wicketstuff core counts as one project)? >> >> Martijn >>
