Meeting 20.05.2024

Attendees

  • Markus
  • Yvonne
  • Moritz
  • Jannis (Protocol done)
  • Lukas (Protocol done)
  • Daniel (Protocol done, Presentation done)
  • Andrei (Scrum Master, Presentation done)
  • Christoph (Protocol done)

Only in the beginning:

  • Filip

Buddies

  • Daniel & Andrei
  • Moritz & Christoph
  • Jannis & Lukas

Agenda

  • 09:00 start
  • protocol: Moritz
  • CI dev issues (Filip)
  • next release (Filip)
  • presentation: Jannis
  • next presentation: Christoph
  • finish line: Daniel & Moritz
  • GitLab "please merge" only if:
    • 2 reviewers
    • all threads solved
  • add more manual and automatic e2e tests
  • scrum with Andrei:
  • refactoring frontend&store:
    • Lukas refactors side bar
    • Daniel does other refactorings

Not Yet Discussed

  • JSON in database

Tasks for Everyone

To be done until Friday 24.05.2024:

  • buddy talk: logical architecture
  • approve meeting MR
  • get MRs done
  • request and approve for requested reviews
  • create/update issues for yourself and assign to next iteration

Individual Tasks

To be done until Friday 24.05.2024:

  • Jannis: create issues: (1) tutorial for layer creation (creation/update metadata + (2) what interface should any layer have), (3) unify layer design, presentation
  • Moritz: base layer image offset, finish PRs: group vs. layers
  • Lukas: toolbar refactoring (dev), clarification+issues
  • Christoph: SQL heatmap optimization, hierarchy, delete plants, subtyping, presentation
  • Daniel: finish drawing UC (tests etc.), create new layer, brushes
  • Andrei: categorize and improve issues, remembering viewing state (copy&paste), merge master to dev

Meeting Notes

More E2E tests should be implemented for existing as well as new features. If this is not possible, describing a manual test is also a viable alternative. Add manual tests to doc/tests/manual/protocol.md

There are subtle differences between the done and closed issue status. Usually issues should be closed once the corresponding PR is merged.

Blocked issues are either marked with links (preferred) or the scoped label blocked (if it is blocked because of e.g. waiting for input which is not reflected as an issue).