Papyrus IC/Architecture/MoM/2017-04-04 Architecture Committee Minutes

Attendees

• Reibert (Ericsson)
• Philip (EclipseSource)
• Rémi (EclipseSource/chair)
• Simon (Zeligsoft)
• Per Jonsson (Saab)
• Samuel Brown
• Florian (CEA)

Next Phone call: May 2nd, 2017, 4PM

Topics

Task Forces

Florian: Product line support/ splitting of the repos

Goal: prepare for sub-projects with the TLP

• About gerrit activities:
  • Restructuring almost done. SysML 1.1 still on main repo.
  • Most of new repo are up and running.
  • 1st step for this year done.
  • Next year: work much on decoupling core architecture:
    • provide a headless version of Papyrus
    • less technology dependent (in particular, the GMF aspects).

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

• Architecture framework switch under review.
  • Merged on M6.
  • This one needs to be tested! Many possible scenarios
    • documentation should be available as soon as it is merged.
  • Action RS: link to the record of the video recording. Record not received yet? Maybe tomorrow. Florian to send information as soon as it is available.

Philip: DSML task force

• Work ongoing with students to help building products. DSL to describe small subset from UML
  • Small subset first
  • Then extend with new concepts
  • Demo first on Information Modeling, then enhance when Architecture Framework switch is on place.
    • goal:
      • ease the creation of simple product version of Papyrus
      • add support for profiles
    • textual language to define a customized version of Papyrus
    • code generator to configure the tool (Papyrus4IM would be the blueprint for that)
    • demo at the end of the cycle
    • work done with students
• 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

• Action: Simon to get back to interested stakeholders - since last meeting
  • Working with Ericsson, then will be extended to other full requirements
  • also get input from Per
  • No news since last meeting (especially feedback from users?)
    • projectional
    • replace xmi serialization (more intrusive)

Per: Dependency management, dependencies from Papyrus

• Describe what has been done manually
• Philip & Per: meeting last Friday to confront self experiences
  • Same analyze of the problems
  • See issues on the dependencies (JDT / xtext / PDE?) -> addition of UI not required, so better to remove dependencies.
  • Description on why such dependencies?
  • Action RS: florian & optional stuff? Best time?
    • Team is currently working on dependencies, but no revolutions => clarifying some boring dependencies. Objective for next release.

Release train for Papyrus

• Neon.3 released
  • Some regular release after Neon.3?
• Oxygen
  • M6 next week.
  • M7 - mid may

Additional topics

• Action: Florian to organize an event on Papyrus architecture workshop focusing on web? Hopefully on June, @EclipseCon France?
  • no more news: focusing on Oxygen currently. Organisation end of May?
• Guava 15/21 issues?
  • fixed from Papyrus perspective?
  • but Papyrus not leaf anymore (Papyrus Compare for example)
  • problem with OCL, fixed by Ed W. Trying not to be dependent on any version, no forwarding specific version to anyone. very new, so still need some investigation
  • look at avoid reexporting projects that are not singleton. Not looked at it since
  • Started working on this?
    • Guava issues solved, if 94130 is integrated?
    • Need to synchronize with Compare, very important for them. Changing for guava 21 is not such evident yet.
• Papyrus collaborative modeling repository
  • Action Florian: Having Philip as a Committer?
  • Action Philip/Remi: release engineering on that topic