Meeting 25.03.2024

next meeting 2.4.2024 9:00 (without Jannis)

Attendees

• Markus
• Daniel (protocol done)
• Jannis (protocol done)
• Christoph (protocol done)
• Moritz
• Andrei
• Lukas
• Yvonne

Buddies

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

Agenda

• 09:00 start
• new members
• welcome
• buddy talks: first contact
• protocol: Moritz
• create issues: Andrei
• new issues use cases
  • heatmap as normal layer (Moritz)
  • heatmap and relation layer has same content (Daniel&Andrei)
    • (bi)annual plants
  • additional layer concept (Daniel)
  • read-only non-member (Andrei)
    • no plant data should leak to non-member
• GitHub vs. GitLab
• decisions:
  • rework notification system (Jannis+Andrei)
  • Jannis: move away from utopia
  • Christoph+Jannis: DB documentation, verlinkung
  • Jannis: raw SQL
• TISS texts review
• Scrum:
  • reviews
  • PRs closed
  • (manual) e2e tests
• better diffs: https://difftastic.wilfred.me.uk/
• sprint plan

Tasks for Everyone

To be done until Friday 29.03.2024:

• buddy talk: first contact, dev setup
• approve meeting PR #1220
• create decision PRs to start discussion
• 2x review requested reviews
• do/update sprint plan

Individual Tasks

To be done until Friday 29.03.2024:

• Andrei: copy&paste issues, scrum
• Daniel: finish timeline, drawing layer first version, finish keybinding
• Jannis: creation times reviews missing, drawing layer, tutorial for layer creation (creation/update metadata + what interface should any layer have), review DB Doku from Christoph, notification profilen, TISS Text
• Moritz: group vs. layer new PR
• Christoph: TISS Text, scraper overrides+German names, Gabriel Thesis, SQL heatmap benchmark, how to add column in tables
• Lukas: crop rotation design, review PRs, fix first issue (assigned)

Meeting Notes

Andrei will help to improve our workflows. He has experience in SCRUM-teams and relevant certifications.

A poll was held to decide whether the Project should migrate to Gitlab over Github. The results were inconclusive, most teammembers voted "both are fine". Next steps are on technical feasibility.

Heatmap should be exposed as a "normal layer" (2nd position after plant). Other Positions are to be decided.

An extra meeting is needed for the "relation-layer". It will show additional textual information related to plant relations, that is not covered by the heat map (Daniel & Andre will be assigned). An incomplete use case already exists.

The choice of important libraries, that are not easily replaced, should be justified in a decision document.

The words "model" and "entity" have been used to refer to the same concept. "Entity" should be added to glossary and from now on only "entity" should be used.