I think email is not particularly good for this. Let’s talk directly next week.
In the meantime, here is some input:
It would be great to align the development of Moose with that of Pharo. We were waiting
for this for a long time, and now that Pharo is built similar to how other projects are
built, we can finally do it. So, this is really great!
And I also do not want to have 1 year releases. In fact, that is why for our work we
actually use the latest version. The only reason why we did not have faster releases was
that there was no reliable way to do it, except the manual way. Right now, we still do not
have such a way for Git either, and this is not a problem unique to Moose. It would be
great work on some solution for this problem to benefit all Pharo projects.
For Glamour and existing GT, we can deal with bugs at most, but we will not invest in
further development. The memory leaks problem seems to have reappeared. This shows that we
do not have the right tools for understanding it, and I would be happy to work with
someone that wants to invest in this, especially when it comes to Announcements.
On the UI front, our complete energy is on Bloc, and the goal is both to produce the IDE
for Pharo and to provide the browsing infrastructure for Moose. Over the past year, the
main UI we used when working with Moose was the Moose Playground and GTInspector and it
works really well. This shows that the investment in Bloc can pay off easily for Moose as
Also, beside the UI, the new GT also comes with visual components, like Mondrian and
Diagrammer, and with the basic support for documentation with Documenter.
I am not sure I understand what not loading GTExample mean. Bloc/Brick/GT are tested and
documented like this, so we need to have that around. I guess that you are referring to
the issue "GT-Examples-Roassal2 should not be packaged in GT-Examples #1180”. I think
there is a confusion, so I added a comment for that:
On Mar 17, 2018, at 6:39 PM, Stéphane Ducasse
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
> On 17 Mar 2018, at 18:26, Stéphane Ducasse <stephane.ducasse(a)inria.fr> wrote:
>> On 17 Mar 2018, at 17:42, Tudor Girba <tudor(a)tudorgirba.com> wrote:
>> 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
> is unmanageable and just a “fuite en avant”.
> So may be automatic release every two weeks is a solution. It should not be difficult
> 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.
> Here we see already that there are difference. SmaCC easy it is external.
> I will start to migrate (I cleaned RoelTyper).
>>> On Mar 17, 2018, at 9:58 AM, Stéphane Ducasse
>>> 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
>>> Baseline migration
>>> I would like to enforce the following:
>>> - the feature todos should not be managed in the bug tracker. Trello is good
>>> - 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.
>>> 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
>>> Moose-dev mailing list
>> "To lead is not to demand things, it is to make them happen."
>> Moose-dev mailing list
> 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
> Moose-dev mailing list
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
Moose-dev mailing list
"Beauty is where we see it."