2017-01-07 Architecture Committee Minutes

Attendees

• Reibert (Ericsson)
• Philip (EclipseSource)
• Florian (CEA)
• Rémi (EclipseSource/chair)
• Simon (Zeligsoft)
• Patrik (Ericsson)
• Keith (OneFact)

Next Phone call: March 7th, 2017, 4PM

Topics

Task Forces

Florian: Product line support/ splitting of the repos

Goal: prepare for sub-projects with the TLP

• Plan almost done. Small technical details to be fixed.

• Discussion with Philip: Become a Papyrus committer, so he could lead Collaborative modeling for Papyrus

• Restructuring on the tests
  • Tests are passing again!
  • Split the execution in multiple layers, about to be backported to Neon

• Architecture framework switch under review. should be released very soon
  • M5 was released => issue with people committing during release... new rules to come there.
  • M6 => will contain update of the architectural framework description. People should be able to start using it with enough stability, but early enough to give feedback.

Philip: DSML task force

• Not a lot of progress to report
• work with students to help building products
• Waiting for some inputs from Per for Dependency management. Reduce dependencies from Papyrus to external, to avoid UI polution
  • Action: Philip to get back to Per
• Information modeling with additionnal component with profile, to show support for DSL's. Interest for example for Flanders's Make
• Have a look to Architectural Framework description. Composition of Papyrus products in mind for AF ongoing work. Would be nice to have views on it.
  • Action Florian: some publication when AF is released, and some documentation to facilitate access to the framework

Simon: Textual / graphical modeling

• Some progress with Federico and Philip. Transform from graphical and textual + facade on the model.
• requirements for hybrid textual approach: no unified requirement from customers
  • Action: Simon to get back to interested stakeholders
• now scheduling the work

Per: Dependency management, dependencies from Papyrus

• Absent - no update on the task force

Additional topics

• GMF runtime and GEF3: for M5, things are OK. Papyrus imported all required classes from GMF tooling runtime. Not so hard to integrate and maintain this.
• 'new' GMF runtime has a new project leader => GMF runtime + GMF notation, Pierre Charles David is very willing to help, but prefers for simplicity avoid to integrate GMF tooling stuff. Next step would be to accept further contributions, but later and after iterations.
• Papyrus developer side depends a lot on GMF tooling, but OK because only for developers. Indication here that we should move out this technology?
• For a longer term:
  • GEF4 as a replacement of GMF runtime? Eclipse web modeling ? Very long term, but nothing decided yet. Decision, or at least, design of 'new' components in Papyrus should be done to avoid dependency towards GMF runtime.
  • Eclipse Che as a base to go on the web? Other framework? no obvious choices here.
    • Action: Florian to organize an event on Papyrus architecture workshop focusing on web?
  • Diagrammatix: already demo'ed at last Ericsson Modeling Days. Could help replacing GMF tooling