what would be the point of having them as submodules? it gains nothing but pain. since all projects need to be released at once the simplest way is to keep them in a single source tree.
-igor On Thu, Dec 16, 2010 at 6:15 PM, Martin Grigorov <mgrigo...@apache.org> wrote: > On Thu, Dec 16, 2010 at 5: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)? >> > I would be even more radical - a repository for each project. > wicketstuff-core will be a separate repository which will use git modules > [1] to checkout the other repos and run mvn goals on them :-) > > But as Igor said all in one will be the simplest. > > 1. http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html > >> >> Martijn >> >
