Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Papyrus IC/Architecture/MoM/2017-03-07 Architecture Committee Minutes

Attendees

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

Next Phone call: April 4th, 2017, 4PM

Topics

Task Forces

Florian: Product line support/ splitting of the repos

Goal: prepare for sub-projects with the TLP

  • About gerrit activities:
    • split is done almost, code moved to new repositories
    • Left only => migration to github. Solutions for these ongoing
  • Discussion with Philip: Become a Papyrus committer, so he could lead Collaborative modeling for Papyrus
  • Architecture framework switch under review.
    • Under review by Florian: potential merge this week.
    • This one needs to be tested! Many possible scenarios
    • documentation should be available as soon as it is merged.

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.
    • Initial version for June
  • 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
    • Philip to organize a meeting with Per

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

Per: Dependency management, dependencies from Papyrus

  • Update in a near future, after meeting with Philip
  • Describe what has been done manually

Release train for Papyrus

  • Neon.3 RC4 tomorrow (2017 March 8th), available 23rd.
    • Some regular release after Neon.3?
  • Oxygen M6 next week.

Additional topics

  • Action: Florian to organize an event on Papyrus architecture workshop focusing on web? Hopefully on June, @EclipseCon France?

Back to the top