PCM Development/Palladio Concall/Minutes 20201407

Aus SDQ-Wiki

Agenda

Please add things you want to discuss to the agenda below.

  • new Palladio release 4.3 available [1]
  • JIRA issues status Dev Board
    • SIMULIZAR-97: Proposed fix okay? [2]
  • Review process
    • Situation: peer groups that assign reviews to each other
    • Goal: distribute reviews of pull requests over people to spread knowledge
    • Requirements: timely reaction to requests (as discussed during last con call 12.05.2020)
      • average time for first reaction should be 2 days
      • final review within 1 week
      • exception handling allowed e.g. in case of high work balance
      • reviewer assignment
        • maybe slack channel for urgent reviewers
        • finding potential reviewer -> postponed
    • final comittment how to proceed in the future regarding PRs in the team (postphone to next ConCall)
    • proposed process:
      • when JIRA task is finished the JIRA task owner triggers pull request and assigns it to a dedicated reviewer (reviever should be an experienced developer in this domain)
      • reviewer receives an email notification from github about the review
      • reviewer conducts the review within X days; if passed will execute the merge
      • github will send an email notification to the JIRA task owner to inform him about the successful pull request
      • JIRA task owner can now close the ticket
  • Fork and cleanup of SimuComFramework for SimuLizar (Sebastian)
    • Allow for more fundamental structural changes without effort to update SimuCom
      • SOLID principles
      • Reduce depth of inheritance hierarchies
    • Externalize from SimuCom project, adapt namespace to prevent conflict
    • Strategically drop SimuCom development/support


Protocol

  • SIMULIZAR-97
    • can be closed with current fix, note in comments current state and ideas and close it as is
    • if further logging issues come up, hopefully it or this protocol is found.
  • EDITORS-225
    • Too much effort to fix, unclear how much work it is currently.
    • Can be implemented without majorly changing the framework, however requires custom code.
    • Try it for second lollipop connector and then re-judge effort. Associated Links for Stephan's example: branch / commit
  • Fork and cleanup of SimuComFramework for SimuLizar (Sebastian)
    • Fork the current state of the framework so that SimuCom still works
    • Strategic decision, take it into stategic meeting (27.07.).