[Moose-dev] Re: How to organize Moose on SmalltalkHub

Hi, I already created a Moose team, and a Moose project inside. I see the forces as follows: - We need to have each engine individually loadable because they are often used in orthogonal projects - There are projects that are developed separately (like Roassal), and thus these are better living outside of the Moose team repository for the moment. - Projects that are either no longer maintained, like Fame, or developed only within the context of Moose, like MooseAlgos, should go into the Moose team repository. Nevertheless, I think each of these projects would better have their own repository inside the Moose team repository. - Moose is the platform, not the actual analyses. Thus, the engines should be grouped in a separate configuration. We can call it MooseEngines. Right now, this would include: Fame, Magritte, Metanool, Glamour, Arki, Merlin, Roassal, (Mondrian for a short time), EyeSee, MooseAlgos, PetitParser, MooseCore, the Core of MooseFinder. - FAMIX should become a family of meta-models and should receive its own configuration and repository with everything related inside: FAMIX-Core, FAMIX-Extensions, FAMIX-Java, FAMIX-Smalltalk, Hismo, Dynamix. In the same repository, I would add also FAMIXAnalysis to include various extensions such as MondrianPaintings or RoassalPaintings or specific browsers and algorithms. - At the moment, we still need to clean DSM and SmallDude. Until they are not cleaned, I would not migrate them as they are. What do you think? Cheers, Doru On Jan 29, 2013, at 1:11 AM, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote: -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev