Re: [gemoc-dev] names for new repositories

[Erwan Bousse <erwan.bousse@xxxxxxx>]

Le mercredi 14 novembre 2018 à 17:03 +0100, Benoit Combemale a écrit :
> Hi all, 
> 
> To mimic the naming of namespaces, what about :
> - gemoc-studio-execution-ale
> - gemoc-studio-execution-java

+1, it's nice to have a common prefix!

And I'm overall very much in favor of having a dedicated repo for the Java engine, to cleanly isolate it at the repo level from the framework it
relies upon. This can be part of making the life of new engine contributors easier.

In fact I would almost prefer to call it "gemoc-studio-execution-k3" because at the moment it's (still) rather k3 specific, and I believe we could aim
someday to have a real Java engine that would rely on automated instrumentation and/or jdb to control pure Java code… but that's another story :).
Let's go with gemoc-studio-execution-java to remain consistent with the current naming.


Thanks Didier!
Erwan

> 
> For the second question, I would argue to ask Eclipse themselves if they prefer to create it now (at the time we create new ones), or if this is
> something doable later, when it will become important to do it. 
> 
> Thanks! 
> benoit
> 
> > Le 14 nov. 2018 à 10:23, Didier Vojtisek <didier.vojtisek@xxxxxxxx> a écrit :
> > 
> > Hi all
> > 
> > as part of https://github.com/eclipse/gemoc-studio/issues/119  (integration of ALE) I plan to take the opportunity  to also contribute to 
> > https://github.com/eclipse/gemoc-studio/issues/97 (Ie. better split component and use dedicated repo)
> > 
> > so I plan to ask for 2 new repositories: (or tell Benoit as the project leader to ask ;-)  )
> > - gemoc-studio-ale-execution  which will contain ALE engines (interpreted first but also compiled versions when available)
> > - gemoc-studio-java-execution which will contain the current java+k3 engine   (ie. move gemoc-studio-modeldebugging/java_execution/ to this new
> > repo )
> > 
> > are these name ok for everybody ?
> > 
> > as a second question, we may also consider to have our dedicated github organisation and ask eclipse webmaster to move our repositories there,
> > this would simplify action as the one above.
> > However this action will have much more impacts since the urls will change too (and thus I'm not sure how the forks will behave)
> > 
> > Didier
> > 
> > _______________________________________________
> > gemoc-dev mailing list
> > gemoc-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> > https://www.eclipse.org/mailman/listinfo/gemoc-dev
> 
> _______________________________________________
> gemoc-dev mailing list
> gemoc-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/gemoc-dev
-- 
Erwan Bousse
Associate Professor, Université de Nantes
NaoMod research group, LS2N research laboratory