Hi, Yes, I saw the activity in the GitHub repositories. Unfortunately, the concrete path is not communicated and as a consequence we cannot contribute. We created Releaser and this can be used to reliably release nested projects residing in different repositories. I believe the reason why everything is in on repository in Moose was to limit the different repositories problem. Perhaps that can be revisited now. As for the new UI: what do you have specifically in mind? Cheers, Doru -- www.feenk.com "No matter how many recipes we know, we still value a chef."

Hi, In fact you did communicate between yourselves only not on chat but on the whiteboard :). In any case, I was not complaining. I was just stating that we cannot contribute in the current arrangement. Yes, sure. I was waiting for some news about a state that is usable. There are projects that do evolve separately such as: GtExamples, DeepTraverser, NeoCSV, XMLParser and SmaCC. As it stands now, the versions from Moose are forks of the code maintained by the original authors. For example, in GT we already use GtExamples, DeepTraverser and SmaCC. To play with the new FAMIX and GT, we will have to fork the code from the Moose repo. At the very least, you can still introduce fine grained baselines in the same repository. Of course. We announced when we met in Lille that we will produce a tool that can address the nested projects problem. We think we have a solid basis now, and it would be worthwhile to investigate it. A key aspect to make this work smoothly is to not rely on Groups, but instead rely on fine grained Baselines. It works for GT, and we have deep nesting and projects spread over many repositories with a mix of projects with fix dependencies and dependencies to latest master version. Ok. Good to know. Doru -- www.feenk.com “Programming is executable philosophy."