Well, except you may want to have a different set of permissions around each one - e.g. if you give each one a full project status in the forge, then you can control the set of contributors for that particular project, such that the set of contributors for all "external" modules does not have to line up with the set for dso core.
From a management standpoint, it also makes sense. But strictly speaking, no I don't think they have to be moved. Steven Harris wrote: > I'm thinking about the config module separation issue. I don't think > we necessarily need to move them out of the source repo. I think we > just need to do a few things: > > 1) Change the kit building to not include them with releases > 2) Restructure so we can have demos, tests and maybe for each one > right next to the module. > > Any thoughts on this? > _______________________________________________ > tc-dev mailing list > [email protected] > http://lists.terracotta.org/mailman/listinfo/tc-dev > _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
