Meeting 19.08.2024

Attendees

  • Markus
  • Stefanie
  • Andrei
  • Christoph
  • Filip

Only listen:

  • Lukas

Cannot come:

  • Yvonne
  • Jannis

Buddies

  • Stefanie & Christoph & Andrei
  • Jannis & Lukas

Agenda

  • 09:00 welcome
  • protocol: Christoph
  • holiday 28.8. -> 5.9., no regular meeting 2.9.
  • all CI pipelines green again
  • all MRs now on dev, except:
    • landing page updates
    • CI fixes not specific to dev (keep Jenkinsfile consistent)
  • PermaplanT Fest
    • 25.08.
    • Anreisemöglichkeiten Wien Hbf -> Deutschkreutz um 08:23 -> 09:47 oder 09:23 -> 10:47
    • Car Sharing?
    • Any questions?
  • colors
  • heatmap:
    • check on every date too resource intensive?
  • entity.rs:
    • Christoph: family?
  • Task Board

Left for next time:

  • branch names:
    • keep default of GitLab?
    • don't use special characters like #!
  • brushing layer architecture (enum?)
  • crop rotation
  • Lukas: drought tolerance

Tasks for Everyone

To be done until Friday 23.08.2024:

  • buddy writing (Schreibtreffen)
  • submit a page of text in submissions
  • approve meeting MR
  • request and approve for requested reviews
  • get MRs done
  • create/update issues for yourself and assign to next iteration

Individual Tasks

To be done until Friday 23.08.2024:

  • Filip: test maps, collect data (2000 concurrent users, why is image loading so slow?)
  • Christoph: RQs, continue hierarchy
  • Andrei: RQs, categorize and improve issues, remembering viewing state
  • Stefanie: RQs, look into tools, bug fixing

Only listen:

  • Lukas: Shading fixes, mockup for shading&moisture&soil

Not here:

  • Jannis: complete MRs, hydrology&soil type backend implementation, fixes, write methods, klarheit über issues

Meeting Notes

No meeting on 02.09.2024

Filip included a test map on https://mr.permaplant.net, further maps to come.

From now on everything will target dev except landing page updates and CI fixes.

Heatmap colors to be decided after color settings table issue is done. #1525

We shouldn't use special characters like '#' in branch names.

We'll leave the family field in the plants entity in entity.rs to be used later with the hierarchy rework.

If it's clear how to incorporate feedback you can merge directly but if it is a bigger change / refactor you can make a new submission of the corrections. The submission should be focused on one chapter (e.g. introduction, methods, ...).

Take small steps, e.g. for finding a research question:

  • Brainstorming
  • Deciding on the RQ
  • Refining the RQ
  • Deciding on tools

This is not necessarily in these steps and sometimes also iterations are needed.