Meeting 01.12.2025

Attendees

Markus
Alfons
Christoph Schreiner
Hannes
Liza
Maiia
Moritz
Paul
Justus
Richard
Andrei
Johannes
Chris(toph) Kraus

Not here (excused):

Patrick (excused)
Ben (excused)

Buddies

Andrei & Maiia
Patrick & Alfons
Christoph & Liza
Ben & Chris
Moritz & Paul
Johannes & Richard
Justus & Hannes

Success Partners

Maiia & Moritz (Frontend)
Ben & Alfons (Frontend)
Hannes & Johannes (DevOps)
Liza & Paul (PM)
Richard & Chris (Tooling)
Christoph & Andrei (Testing)
Patrick & Justus (Backend)

Agenda

09:00 start
Meeting Notes: Maiia
status report, blocks:
- CI: mode variable -> issue created
- Moritz: new container feature.staging.permaplant.net -> open
availability during lecture-free period (vote):
- 22.12. 29.12. 5.1. -> probably all 3 dates
Andrei: presentation performance, RQ, Method
releases (date of last MR merges):
- 0.9.0 (03.12.2025)
- 1.0.0 (17.12.2025)
- afterward: months/seasons (German Link with graph)
important tasks for releases:
- please check release critical for this week until 03.12.2025
- please check if any 1.0-must-have/should-have cannot be done until 17.12.2025
- outcome of last decisions
- regular release with master.permaplant.net
scientific work:
- which question to choose: clear approach, background and method
- related work etc. usually is secondary (can always be found, more is better)
- clutter vs. context
dev tricks:
- if something might be reverted, please put in separate commits: git add -p
Development Board:
- Alfons
- Andrei
- Ben (not here)
- Chris(toph) Kraus
- Christoph Schreiner
- Hannes
- Johannes
- Justus
- Liza
- Maiia
- Moritz
- Patrick (not here)
- Paul
- Richard
- Tasks for Everyone

Outlook

Moritz and Richard cannot come next week
retrospective by Liza
repository renames
tech talk (frontend/backend coordination):
- map overview sorting

Tasks for Everyone

Tasks to be done until latest Wednesday 03.12.2025 23:59 (earlier is of course better):

buddy: look at release critical/1.0 issues/MRs/decisions together
fix release critical problems
review release critical MRs

Tasks to be done until latest Thursday 04.12.2025 23:59:

Regular Tasks
- Reminder: Change from last time: reply to issues from next iteration!

Talks

next time:
- Ben (08.12, FLOSS refactoring on library upgrades)
- Johannes (08.12., open telemetry)
later upcoming talks:
- Christoph Schreiner (15.12., final thesis presentation, developer-central)
- Chris(toph) Kraus (any date not next week, developer perspective of e2e tests)
- Hannes (January?, Debugging Nextcloud Images)
- Moritz (any time fine, pitfalls about pagination&endless scrolling)
- Patrick (TBD)
- Richard (TBD pipeline, dev-centric or architecture)
done talks:
- Maiia (27.10. socratic questioning on RQ)
- Liza (03.11.2025, PM)
- Paul (10.11., Running Meetings That Don't Waste Time)
- Alfons (17.11., methodology)
- Justus (24.11., Debugging+Logging in the Backend)
- Andrei (01.12., performance, RQ, Method)

Bachinger, Paul: 16 Muth, Moritz: 11 Raab, Markus: 11 Müller, Alfons: 5 Schlegel, Ben: 4 Schreiner, Christoph: 4 Dinu-Coreth, Andrei Cristian: 3 Kuzmishyna, Maiia: 3 Graßl, Patrick: 2 Mokshantseva, Elizaveta: 2 Weilguni, Justus: 2 Zettl, Hannes: 1

Issue progress (status changes + closed)/ total assigned

Bachinger, Paul: 6/11 Dinu-Coreth, Andrei Cristian: 2/6 Graßl, Patrick: 3/6 Kraus, Christoph: 0/8 Kuzmishyna, Maiia: 2/8 Mokshantseva, Elizaveta: 4/13 Muth, Moritz: 1/6 Müller, Alfons: 5/13 Raab, Markus: 3/4 Schlegel, Ben: 4/8 Schreiner, Christoph: 3/6 Weilguni, Justus: 2/10 Wutscher, Richard: 0/4 Zettl, Hannes: 1/3 Ziehengraser, Johannes Leonhard: 1/4 Total: 37 / 110

Did Not Approve Last Meeting Notes In Time

Chris(toph)
Johannes
Richard

Meeting Notes

09:00 start
Meeting Notes: Maiia
Andrei: final thesis presentation
- including performance, RQ, method, results (counting and FPS)
status round:
- Alfons: Ok week, met with Patrick, worked on privacy overview & decision. Not blocked
- Christoph: A couple of MRs ready for review, issues clear
- Chris: Reenabled image tests
- Andrei: Good week, progress on most tasks from the iteration. Focusing on writing the thesis
- Hannes: creating Nextcloud environment that should be done this week, this may lead to sudden progress in many issue because they are blocked by this
- Johannes: good progress, next week could show telemetry data
- Justus: good progress, needs help from CI people to setup env vars (issue was created by Paul)
- Liza: not much time last week, will catch up this week
- Maiia: probably fixed "broken image" problem for 1.0, needs help with testing the MR
- Moritz: not much time last week, for some issues didn't know how to finalize them, will miss PermaplanT meeting next week, touch screen for 1.0 still blocked
- Paul: good progress, not blocked
- Richard: worked on Infrastructure topics
Does staging variable already exists? (Paul) - See https://issues.permaplant.net/2353
Touch screen - idea: spin up a new container and copy FE code manually there
Release critical MRs will be marked - they need reviews asap
releases (date of last MR merges):
- 0.9.0 (03.12.2025)
- 1.0.0 (17.12.2025)
- afterward: months/seasons (German Link with graph)
after 1.0 no more breaking changes in releases (only compatible migrations, otherwise we are free to change anything anyways)
if there are outstanding changes that are not possible to migrate, they need to be done asap
important tasks for releases:
- please check release critical for this week until 03.12.2025
- please check if any 1.0-must-have/should-have cannot be done until 17.12.2025
- outcome of last decisions
- will we already use www.staging.permaplant.net?
- we probably won't have it ready for 0.9.0
availability during lecture-free period (vote):
- 22.12. 29.12. 5.1.
scientific work:
- clutter vs. context
- 2 types of problems people have with writing:
  - problem to write enough - always need to establish context around the claim
  - problem of writing too much - clutter needs to be reduced, only the main point should be repeated several times throughout the thesis
- pay attention to clutter & context also when reviewing documentation
- which question to choose: clear approach, background and method
- RQ: something easily describable, something where the method has clear steps
when not to change RQ (one of the following):
- you have a nice background paper
- you have a clear method/approach
- if the only reason is to have a "better" RQ (endless process)
- related work etc. usually is secondary (can always be found, more is better)
- sometimes existing related work can be paraphrased to be relevant even to a changed RQ
dev tricks:
- if something might be reverted, please put in separate commits: git add -p
Development Board:
- Alfons:
  - look back at older MRs,
    - address open points,
    - reinvite people,
    - mark as ready for merge.
  - Will carry out 0.9.0 manual tests after notification from Paul
- Andrei:
  - one blocked task - unclear what should be done next
  - two more issues to put into iteration to finalize the work on his project
- Ben (not here)
- Chris(toph) Kraus:
  - check your own MRs
  - 1-2 more issues to put into current iteration
- Christoph Schreiner:
  - main focus - reproducibility
  - new issue on database constraint
- Hannes:
  - a couple of open issues related to Nextcloud and staging
  - some needed for releases (picture to landing page)
- Johannes:
  - needs to document OpenTelemetry,
  - will give overview from CI perspective on Friday
  - will give overview from dev perspective on Monday
  - will continue to investigate the keycloack issue
- Justus:
  - 4 release critical MRs, blocked issue needs to checked whether workaround helps
- Liza:
  - Liza to help with reviews on rust code
- Maiia:
  - no unclarities
  - will focus on 1.0 must_have
- Moritz:
  - one issue would be nice to be done for release
- Patrick (not here)
- Paul:
  - focus on release critical issues
  - how to come to the situation that nothing is "open" - "just implement everything XD"
- Richard:
  - give answers on questions and help with staging
- Tasks for Everyone:
  - buddy talk
  - information on all issues in the iteration until Thursday so that next iteration can be planned on Friday

PermaplanT