Meeting 06.05.2024

Attendees

  • Markus
  • Yvonne
  • Moritz
  • Lukas
  • Daniel (Protocol done)
  • Andrei (Scrum Master)

Came late:

  • Jannis

Not here:

  • Christoph (Protocol done)

Buddies

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

Agenda

  • 09:00 start
  • protocol: Lukas
  • short mid-term presentation (Andrei)
    • Product Owner: Yvonne&Markus
    • Scrum Master: Andrei&Markus
  • TUgitLab migration
  • BBB: everyone is admin now
  • demos from Daniel
    • brushes
    • creation of layers
  • which (docker) dev setups are used?
    • 2x dev container (or more?)
    • 2x docker+backend/frontend local
    • 1x pure local (no docu needed?)
  • next presentation: Daniel
  • scrum with Andrei next week:
    • 45 issues in progress?
    • reviews
  • new burndown chart
  • refactoring frontend&store (conclusion was written down in issue)
  • next release (postponed)
  • (manual) e2e tests (postponed)

Tasks for Everyone

To be done until Friday 10.05.2024:

  • buddy talk: presentation topic
  • approve meeting PR
  • get MRs done
  • cleanup/clarification of all currently assigned issues
  • request and approve for requested reviews
  • add tasks to burndown chart

Individual Tasks

To be done until Friday 10.05.2024:

  • Lukas: issues hydrology, toolbar refactoring (dev), merge master into dev, hydrology
  • Daniel: finish timeline, drawing, create new layer, (brushes)
  • Jannis: postponed deletion layers+map, create issues: (1) tutorial for layer creation (creation/update metadata + (2) what interface should any layer have), (3) unify layer design
  • Andrei: categorize and improve issues, remembering viewing state (copy&paste)
  • Moritz: grid UC finish, base layer image offset, avatar GitLab, (map deletion), selection+deselection refactoring

Not here:

  • Christoph: SQL heatmap optimization, hierarchy, delete plants, subtyping

Meeting Notes

Andrei presented a software development process: Agile is a mindset for software developement and Scrum is the framework implementing it. It defines at least three roles (Product Owner, Scrum Master, Devs), three Artifacts (Product Backlog, Sprint Backlog, Increment) and five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retro. MRs, issues and requested reviews should always be assigned to someone to then see the todos at the top left in Gitlab. Labels should also always be set at issues & MRs for everyone getting a good overview.

Iterations are set as a property and when an issue is not done the iteration automatically increases at the end. Sprints and dailies are mixed in PermaplanT because of only weekly meetings. Big issues describing big parts of use cases can be used to organize and link together small issues which should be easily done in one week and actually describe/represent the work to be done.

The migration to GitLab worked out quite smoothly issues in the pipeline are discussed which were mostly already existed in the past but not visible due to missing or bad error handling. Some changes in the submissions repo were lost but everyone can push them again because they should exist locally.

Daniel presents the current state of the brush feature as a demo. It is already possible to mark/create areas using the brush in the draft. Together with Jannis he also demoed the creation of new layers which is already possible for drawing layers in their draft.

Refactoring and implementations about environmental factors should be merged to dev and everything else should be merged to master. Master is merged into dev weekly. (Lukas for upcoming week)

Everyone should create issues for himself before the weekly meeting which represent upcoming work. Andrei is always creating issues after the weekly meetings for everyone for things discussed in the meeting.