Hi Stef, The first task should be to get Glamour up and running on Seaside. Currently, there is a problem most likely induced by the changes in Announcements. We need some focused work on this.

Andrei, the original author, does not have much time (he has a job now :)), so we need to get other people to look into this. Andre, Cyrille, do you have time?

Cheers, Doru On 14 Jul 2011, at 13:02, Stéphane Ducasse wrote: > Hi guys > > I would like your input and (also help) for the following. > I would like to have a web servers with some selected case studies for a show room on internet > We should have it for December. Now I think that we should join forces. > > > I think that we could take > > We take one or two projects: > ArgoUML > Papyrus > Seaside > > We could have an apache rewrite rule to dispatch to the right image > > We create two specific images that contain models > for argoUML multiple versions > for papyrus a model with a limited amount of entities > for Moose itself/seaside so that we get testcoverage.... > > Then we propose different analysis > - metrics > - polymetric views > - eyeScope > - cycle identification > - distribution map (may of commits or something) > - evolution hierarchy (cf the paper of girba on using Hismo) > - reports > > Usman this should correspond to your ideas of scenario. > > So let me know what you think. It would be beneficial for the complete community so we need help. > > Stef > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi guys I would like your input and (also help) for the following. I would like to have a web servers with some selected case studies for a show room on internet We should have it for December. Now I think that we should join forces. I think that we could take We take one or two projects: ArgoUML Papyrus Seaside We could have an apache rewrite rule to dispatch to the right image We create two specific images that contain models for argoUML multiple versions for papyrus a model with a limited amount of entities for Moose itself/seaside so that we get testcoverage.... Then we propose different analysis - metrics - polymetric views - eyeScope - cycle identification - distribution map (may of commits or something) - evolution hierarchy (cf the paper of girba on using Hismo) - reports Usman this should correspond to your ideas of scenario. So let me know what you think. It would be beneficial for the complete community so we need help. Stef _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Hi, I have but they are commercial. The idea is that if you want to increase quality you first have to define what that is :). You need a stakeholder that can tell you what is important and what is not. Otherwise, you only measure things that you think are important, and which usually turn out to not be important in reality. All in all, it's not just the code that you need, but also the one that can define the problems that should be solved. Cheers, Doru On 14 Jul 2011, at 15:12, Alexandre Bergel wrote: > Is there a case study where moose helped increasing it's quality, and not only identifying anomalies? > > I have some case studies, but in smalltalk only > > Alexandre > > > > Le 14 juil. 2011 à 13:02, Stéphane Ducasse <stephane.ducasse(a)inria.fr&gt; a écrit : > >> Hi guys >> >> I would like your input and (also help) for the following. >> I would like to have a web servers with some selected case studies for a show room on internet >> We should have it for December. Now I think that we should join forces. >> >> >> I think that we could take >> >> We take one or two projects: >> ArgoUML >> Papyrus >> Seaside >> >> We could have an apache rewrite rule to dispatch to the right image >> >> We create two specific images that contain models >> for argoUML multiple versions >> for papyrus a model with a limited amount of entities >> for Moose itself/seaside so that we get testcoverage.... >> >> Then we propose different analysis >> - metrics >> - polymetric views >> - eyeScope >> - cycle identification >> - distribution map (may of commits or something) >> - evolution hierarchy (cf the paper of girba on using Hismo) >> - reports >> >> Usman this should correspond to your ideas of scenario. >> >> So let me know what you think. It would be beneficial for the complete community so we need help. >> >> Stef >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Speaking louder won't make the point worthier." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev