19 Sep
2011
19 Sep
'11
2:14 p.m.
Hi Alex,
On 19 Sep 2011, at 13:13, Alexandre Bergel wrote:
It seems that there was a misunderstanding :)I did not say 2h for commenting and I was
certainly not trying to diminish your efforts. I said 2 hours for investing in the
infrastructure that goes beyond Mondrian (although it is already great to know that
Mondrian is taken care of :)).
It is important to make transparent what people are willing to invest and then we do it.
That is all.
In particular we need to work together to form a coherent image of the inner architecture
of Moose. I mean, I have an idea of what I want it to be, but I would like to get more
people around it so that we can spread the knowledge and limit the truck factor.
Btw, welcome Angel :).
Please,
let's put ultimatums aside. The issue is not allPropertySelectors, and not even
problems in the core (which actually are not that many). It would be great indeed to have
more comments, and I would welcome any effort in this direction.
Yes. And your book is important.
However, the main issue is collaboration around
the infrastructure. Everyone is working in his own corner with very little integration and
collaboration happening. I can coordinate the work and spread knowledge around, but only
if people work with me.
I will work on CAnalyzer. I started to make it up to date. I will continue next week.
So, here is a proposal:
Who wants to join the core team?
Right now we have:
• Stef
• Me
• Simon
• Alex
Joining the core team would imply investing at least 2h / week on actually working on the
infrastructure, and on cleaning it.
Simon, I am not sure if you are interested in this anymore. Stef, do you have the time to
do it? Alex, do you want to work on more than Mondrian? I certainly will continue.
Hey! Working on Moose involves plenty of other things than commenting the core. I work
more than 2h / week on Moose, however little coding on the core. Moose is used in my
lectures. Angel's postdoc did not come up from nothing. More grants will come soon.
I will revive CAnalyzer because of a case study we
have to do here. I have no problem at commenting uncommented things that I use for this.
CAnalyzer is welcome. It would be great to have a step-by-step instructions of how to use
it on different platforms (right now, it is difficult to figure it out).
Cheers,
Doru
Alexandre
--
www.tudorgirba.com
"Reasonable is what we are accustomed with."
On 19 Sep 2011, at 09:36, Stéphane Ducasse wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi moosers
I would like to know if you are interested in Moose?
Why because the comments are not good.
Now this is simple either we let moose decay (I can focus on Pharo easily) or we do
something
Now I should know what you can do and energy you can put on the table because there is
little use
we get a new engineer and postdoc (because if the core is not clean than nobody can learn
from it).
So
Plan A- build a roadmap and do it (I can probably work every two evenings on it for a
month).
Right now (this evening we log on chat and we fix) these two
allPropertySelectors
is used
allDeclaredProperties
is used
FamixCore class comments
Plan B - I focus only on pharo (because I cannot do both especially right now).
But I should know because we are hiring a new engineer and a new postdoc for moose and
without a community effort
I do not see the point.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev