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
