I would like also to see what is the vision for the future of Moose. 

Because we will put some effort on the table but not blindly and I would like to avoid to 
throw away months of work. 

I would like to know what is the status of Glamour development because iceberg shows that Glamour is buggy. 
We also have memory leaks in Pharo because of GT tools and this is super annoying. 

I think that there are too many announcers to my personal taste

stef

On 17 Mar 2018, at 18:26, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:


On 17 Mar 2018, at 17:42, Tudor Girba <tudor@tudorgirba.com> wrote:

Excellent!

Andrei and I allocated next Tuesday to look into migrating the code to GitHub. Can we sync on Discord for this?

Yes it would be nice. 

Now tuesday we will have a meeting with Guille and others because for Pharo  we can make sure that 
we can get exactly the same system to reproduce bugs and not end upi with situation like two weeks ago where we could not get Pharo 
opening. So may be the pattern for Pharo can be applied to Moose.  

For the new moose I do not want to have one year open session. I’m fed up to have no possibility to go back in the past. 
So we should find a solution and a real one. I’m not in the mood to lose my energy on something that 
is unmanageable and just a “fuite en avant”.
So may be automatic release every two weeks is a solution. It should not be difficult to git. 

I also would like that subprojects are managed nicely and modularly. For example I do not understand why we have Roassal-VW in Moose.
I want to make sure that we can get moose without GTExample also. 

We should have a pattern for subcomponents and projects. 
PetitParser
SmaCC
Roassal
XML
Here we see already that there are difference. SmaCC easy it is external. 

I will start to migrate (I cleaned RoelTyper). 

Stef 


On Mar 17, 2018, at 9:58 AM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:

Hi guys

We started to have a look at the bug entries of Moose on github. 
We will start to migrate Moose to github. We will have to think how to manage this. 
Projects
Subprojects
Baseline migration

I would like to enforce the following:

- the feature todos should not be managed in the bug tracker. Trello is good for this. 
- Now todo related to current situation: such as remove empty class, split package should at least the entry should be tagged with todo. 
- close any bug entry that does not have a description how to reproduce it.

Stef

--------------------------------------------
Stéphane Ducasse
http://stephane.ducasse.free.fr
http://www.synectique.eu / http://www.pharo.org 
03 59 35 87 52
Assistant: Julie Jonas 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev

--
www.tudorgirba.com
www.feenk.com

"To lead is not to demand things, it is to make them happen."




_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev

--------------------------------------------
Stéphane Ducasse
03 59 35 87 52
Assistant: Julie Jonas 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France

_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev

--------------------------------------------
Stéphane Ducasse
03 59 35 87 52
Assistant: Julie Jonas 
FAX 03 59 57 78 50
TEL 03 59 35 86 16
S. Ducasse - Inria
40, avenue Halley, 
Parc Scientifique de la Haute Borne, Bât.A, Park Plaza
Villeneuve d'Ascq 59650
France