PCM Development/Palladio Concall/Minutes 20211116

Aus SDQ-Wiki

Agenda

  • JIRA issues status Dev Board
  • Stand-up: On which topic are you currently working?
  • Discussion: what are your expectations of a satisfying concall?
  • Removing the GMF editors and keep only Sirius editor from the new PCM (Snigdha)

Attendees

  • Martina
  • Anne
  • Floriment
  • Larissa
  • Manar
  • Maximilian
  • Nicolas
  • Snigdha
  • Steffen
  • Stephan
  • Yves

Stand Up

  • Martina: in progress: trigger code generation in experiment automation and upper bound for amount of users
  • Stephan: monitors build mailing list and manages transfers of build role to Larissa and Nicolas
  • Floriment: Mosaic project, new features based on project, nested resource containers, SSP presentation of event-based Slingshot simulator
  • Maximilian: ticket about adding constraints to metamodel finished, new ticket for triggering constraint validation in analyses
  • Yves: reviews for API to create PCM models based on code
  • Snigdha: working on ticket for selecting required role if ambiguous. new points to be discussed later in the meeting.
  • Larissa: migration of build to new Eclipse version and working on test cases for new project wizard.
  • Nicolas: migration of projects to new Eclipse version
  • Manar: finished ticket on operations tab in properties view, merge and review of JaMoPP contributions of student, work on SoMoX
  • Anne/Steffen: Secured funding to keep work running

Status Dev Board

  • How to do review for results, which are not code on Github?
    • Set status to "closed" and ask someone to review the issue
    • After the review has been done, set status to "fixed" if result is satisfying
    • Move back to "in progress" if result needs some improvements
  • Not too much progress in sprint, therefore the current sprint will be just prolonged

Expectations of Satisfying Concall

  • Steffen
    • positive: Get to know about recent changes and work -> works quite well on a high level already.
    • negative: Integration of Karlsruhe and Stuttgart could be improved
  • Maximilian
    • focus on discussion about tickets is good
    • exchange of implementation details / background knowledge for working on tickets is limited because knowledge is already missing in the team
  • Yves
    • getting help works usually quite well
    • avoid in-depth discussions on topics only relevant for one person because knowledge to contribute to discussion is not available (maybe prepare or at least introduce such discussion in a way that all people can understand the context, maybe support by visual drawing on whiteboard, maybe timebox such discussions and move to bi-lateral discussions -> audience should indicate that the current discussion gets out of hand e.g. via chat)
  • Snigdha
    • should we contact the reportee or discuss trouble with tickets in the concall -> first reportee, then concall if reportee cannot help
      • posting questions in Palladio Slack could also be a good way to get feedback
      • distinguish between the introduction of an issue and solving the issue
  • Floriment
    • overall satisfying, good overview
    • integration of Stuttgart/Karlsruhe should be improved process-wise
  • Manar
    • requesting support / asking questions works pretty well
    • supporting teaching groups and pointing to them is beneficial
  • Martina
    • some discussions are too long/in-depth
    • attendance could be improved
  • Action items for next time:
    • Do stand-up in the following concalls again
    • Moderate/introduce discussions in a way to keep everyone on track

Remove GMF Editors

  • remove them from aggregated update site
  • keep dedicated update site of GMF editors as long as possible

Testing Day

  • 26.11.
  • wait for email before downloading stuff