Participants

Notes

State of documentation, state of the following:
- Arbitrary Load Balancing Strategies? (Patrick Firnkes) → TODO DW: Check what Patrick Firnkes has done on Load Balancing Strategies, Ask Anne / Patrick
Prototype of next gen Simulizar (Sebastian) → WiP, Sebastian is still looking for student
Possible student's theses (selection of reconfiguration mechanisms) (Max) → WiP
- Review of theses by Sebastian → WiP
Review of removal of IModelAccess (Max)
- State of code review by Floriment → Comments and several issues are on GitHub, another session after the issues have been received
Impliciation of removing PCM measuring points without additional information (Dominik) → No update
Assign tasks for cleanup of top 10 classes (wrt code) → No update
Discussion about changes that shall be released → Discuss with new version of SimuLizar

Delta to EPL 2.0?
- Compatibility to GPL, but not beneficial to us, other than having one license.
- If we still can: share code, binaries and release binaries it should be fine.
- The current common licence should be used in all projects.
Decision: Switch to EPL 2.0

Same concept in JIRA, assignment can become outdated
Merge/pull requests should get through. This should also be possible more quickly.
Code ownership can be reassigned by administrators of the organization, therefore there should not be a problem.
Align process with normal process for people leaving organizations.

Problem: requires changing pcm.ecore and regenerating the model code.
Test cases for StoEx are passed.
Inline validation only uses validation by EMF, but does not trigger the validation by Sirius
Decision: Move forward, change metamodell/regenerate if necessary

Follow up of Simulizar workshop
- State of documentation, state of the following:
  - Arbitrary Load Balancing Strategies? (Patrick Firnkes)
- Prototype of next gen Simulizar (Sebastian)
- Possible student's theses (selection of reconfiguration mechanisms) (Max)
  - Review of theses by Sebastian
- Review of removal of IModelAccess (Max)
  - State of code review by Floriment
- Impliciation of removing PCM measuring points without additional information (Dominik)
- Assign tasks for cleanup of top 10 classes (wrt code)
- Discussion about changes that shall be released
General switch to EPL 2.0 license (Stephan)
- Licenses mentioned on Github and in code differ in some cases
- Apply EPL 2.0 to all projects?
- Release and usage of new license feature required
  - Replaces all old and custom licenses
  - More simple installation dialog (only one license to accept)
Introduction of code owners (Stephan)
- code owners is concept of Github to define responsible person for code parts
- used in kit-sdq group to track code and build responsibilities
- branch protection rules can require review of a code owner before merge
- role of code owner: watch for open pull requests and fix build errors
- initial definition of owner based on JIRA
- opinions?
StoEx-Xtext integration (Stephan)
- Idea: Add constraints to PCM Core elements that assert the correct type of a stoex by calling ExpressionTypeVisitorFancyTM
  - cool new feature
  - but also simplifies integration code for Xtext inline editor