Yes, I am interested in this! However the tasks you mentions are highly time consuming...
Alexandre
On Oct 15, 2012, at 3:28 AM, Tudor Girba tudor@tudorgirba.com wrote:
Hi,
We have to think about releasing Moose 4.7 and moving to Pharo 2.0.
There are several reasons why the move to 2.0 would make sense:
- Athens is coming. We have a major interest in this technology and we need to get on it as soon as possible.
- The environment moved to RPackage entirely.
- Pharo needs users.
Before moving to Pharo 2.0, we need to release a robust 4.7. There are still some open points: http://code.google.com/p/moose-technology/issues/list?can=2&q=milestone%...
The most pressing ones are: Issue 799: Editing code in Glamour must be faster Issue 851: Create a stable version for Moose and all its subparts Issue 853: ConfigurationOfMoose should be split to reflect core vs suite
Another area to look into is the cleaning of the FAMIX navigation. Right now it's a mess in there. We should probably remove most of the hardcoded methods and rely on Chef. Any taker?
My idea is to target a release this year. Input is more than welcome :)
Cheers, Doru
-- www.tudorgirba.com
"Every thing has its own flow"
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev