Meeting 04.05.2026

Attendees

  • Markus
  • Chris(toph) Kraus*
  • Christoph Schreiner*
  • Hannes*
  • Ines*
  • Liza*
  • Moritz*
  • Peter*
  • Vseslav*
  • Mo(ritz) Adelsberger*

Not here:

  • Lukas (unexcused)

Cannot come:

  • Elia
  • Patrick

Buddies

  • Moritz & Patrick
  • Christoph & Liza
  • Chris & Hannes
  • Elia & Peter
  • Vseslav & Ines
  • Lukas & Mo

Success Partners

  • Elia & Moritz (Frontend)
  • Vseslav & Chris (Tooling)
  • Mo & Justus (Backend)
  • Ines & Liza (Quality)
  • Peter & Hannes (Nextcloud)
  • Patrick & Lukas (Infrastructure)

Special Partners

  • Hannes & Peter (Nextcloud)
  • Vseslav & Elia (Übergabe Guided Tour)
  • Christoph & Vseslav (Übergabe Scraper Data)

Agenda

  • 09:00 start
  • Meeting notes: Hannes, Zettl (Backup: Moritz)
    • change in meeting notes writing: don't copy agenda
  • Welcome game: The Object Challenge Everyone grabs one object from their desk. They explain in 10 seconds why this object represents their day or mood.
  • efficient collaboration:
    • thread closing strategy
    • follow-up before closing thread
    • update issue description
    • unassign people if enough reviews
    • decisions: all text in repo
    • think about which notifications it creates
  • Talk Moritz (4.5., thesis presentation)
    • problem: mobile usability
    • avoid release testing, more screen sizes
    • which tool? playwright works?
    • which screen size?
    • workflow
  • status: looking back
    • how to become more efficient?
    • how were reviews?
  • fun with reviews
    • make sure to invite others for review, or ask others for help
    • minimum 2 reviews: 1x testing, 1x code
  • test case guidelines
  • code quality
  • efficient glab hacks: approve+comment
  • More about PermaplanTreffen
    • wo wir sind: Unterfrauenhaid (Oberpullendorf)
    • was wir machen: div. Team-Aktivitäten
    • public transport possible
    • +1
  • status: looking forward
    • commitment
    • next steps
    • all clear?
    • right amount of issues?
  • Development Board
    • Chris(toph) Kraus
    • Christoph Schreiner
    • Elia
    • Hannes
    • Ines
    • Liza
    • Lukas
    • Mo(ritz) Adelsberger
    • Moritz
    • Patrick
    • Peter
    • Vseslav
  • next talks
  • Tasks for everyone

Outlook

  • Jenkins and doc login
  • infrastructure roles
  • code review guidelines
  • decision workflow
    • simplifications
    • when which state
  • FAQ brainstorming: ask a question -> next time
  • workflows:
    • improvements of coding guidelines
    • adding new plants
    • design decisions: should be complete, Peter is manager

Tasks for Everyone

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

Did Not Approve Last Meeting Notes In Time

  • Ines
  • Patrick
  • Christoph, Kraus
  • Elia
  • Christoph, Schreiner

Statistics (23.04.2026 - 30.04.2026)

Merge Request approved

Levchenko, Vseslav: 3 Raab, Markus: 3 Kraus, Christoph: 2 Muth, Moritz: 2

Issue progress (status changes + closed)/ total assigned

Adelsberger, Moritz: 1/5 Dinu-Coreth, Andrei Cristian: 1/1 Graßl, Patrick: 1/12 Kraus, Christoph: 6/12 Levchenko, Vseslav: 10/17 Mokshantseva, Elizaveta: 6/10 Mrkonjic, Peter: 6/16 Muth, Moritz: 3/10 Oberhauser, Lukas: 1/4 Schlegel, Ben: 1/6 Schnabl, Ines Katharina: 7/13 Schreiner, Christoph: 2/10 Weilguni, Justus: 1/8 Wenty, Elia: 5/12 Zettl, Hannes: 1/1 Total: 52 / 137

Talks

  • upcoming talks:
    • Peter (11.05. decision workflow, Nextcloud folder structure proposal)
    • Elia (11.5. guided tour workflow, presenting study and dev feedback)
    • Mo (DevOps)
    • Lukas (TBD)
  • current talks:
    • Moritz (4.5., thesis presentation)
  • done talks:
    • Ines (27.04. static analysis, eslint)
    • Patrick (30.03, Security from DevOps)
    • Liza: 16.03, retrospective
    • Ben (02.03., FLOSS refactoring on library upgrades)
    • Liza (03.11.2025, PM)
    • Paul (10.11., Running Meetings That Don't Waste Time)
    • Justus (24.11., Debugging+Logging in the Backend)
    • Andrei (01.12., performance, RQ, Method)
    • Paul: (15.12 efficient issue refinement)
    • Moritz (29.12., pitfalls about pagination&endless scrolling)
    • Christoph Schreiner: 12.1. final thesis presentation, developer-central
    • Chris(toph) Kraus (02.02., workflow+developer perspective of e2e tests)

Notes

  • we started with the object game as an ice-breaker
  • Collaboration Efficiency:
      1. MR threads: We try to close our threads as quickly as possible, within iterations, either by fixing things or by creating a follow-up issue and writing "Follow up in #nr" (which closes all threads)
      1. Issues: keep issue descriptions updated when you learn more about what is to be done or the situation changes etc., and also write in the comments because only changing the description doesn't notify issue participants
      1. Labels: usual labels are already part of the issue template with the "/label" command that sets these labels
      1. Sized Bites: try to keep units of work atomic and as small as possible
  • Moritz's Talk:
    • thesis topic: make PermaplanT mobile-friendly
    • Issues with the application:
      • mobile wasn't really a dev focus
      • overlapping components, wrong size of components, imprecise or missing touch controls, ...
    • Goals:
      • How to get rid of inconsistencies?
      • Can UI common issues be avoided with automatic testing?
      • Unit tests: cannot capture constraints of real devices
      • End2End testing:
        • executes things in a real browser
        • captures real devices constraints
        • four error classifications were implemented in the e2e checks
        • overlap with parent
        • scrolls in multiple directions
        • overlap with boundaries
        • size of clickable elements
        • results analyzed over time (e.g. using a graph)
    • current state: analysis in the finalization
    • question: Was it possible to integrate the tests in the existing playwright setup?
      • yes, but also alternatives (e2e as well as other paradigms) were tested
      • e2e tests turned out to be the best approach (captures real world constraints)
      • from the e2e alternatives, playwright turned out to be the best overall
    • question: which usability concerns are more important: usefulness vs execution cost
      • ultimately tests should be plug-and-play, intermediate states as well
      • the priorities are an outcome of the thesis discussion (cost of executing test vs. usefulness), the data on that is currently being collected
      • resource usage is very optimized
  • status round: progress
    • Chris K: good progress
    • Christoph S: little project progress but good thesis progress
    • Hannes: huge progress, good week
    • Ines: found some important fixes, now looking at literature for thesis, very happy
    • Liza: not that much time, but opened an MR and worked on closing one
    • Mo: good week, a lot of progress, happy with current progress, but currently sick a bit
    • Moritz: progress as usual, not 100% productive due to local setup problems
    • Peter: didn't have much time, but progress in his current decision, started writing background on thesis
    • Vseslav: progress average, sadly couldn't do everything, this week getting a certain MR done and more MRs/issues
  • issue estimations:
    • time and effort estimations can be wrong easily, especially if issue is unclear or big or vague
    • it's impossible to have everything clear (additional follow-up is completely normal)
    • but situation can be improved a lot by asking good questions in issue-review
    • we use the following mitigations within issue-review:
      • Definition of Done (DoD): it gives acceptance criteria that must be fulfilled and from this DoD, everything else can be derived
    • Self-Estimation: part of issue review is to do a time estimation with the question "can it be done in one working day?"
    • glab tool: use gitlab in command line via glab if you're tired of using the UI for things; glab can e.g. approve MRs
  • PermaTreffen vote: extended until 07.05., 9 people have voted (checked: 04.05. 10:25)
  • Development Board:
    • Chris K: Question about test prioritization. Answer: full range from:
      1. manual tests (lowest priority)
      2. automated tests that sometimes run
      3. automated tests that always run on every commit
      4. automated tests that always run on every commit and also every release (smoke tests: highest priority tests)
    • Hannes: asked about whether the "do reviews" issue can be deleted now that the contrib/weekly.md file exists: Markus closed the "do reviews" issues because our iteration process is much better now and the reminder issues aren't necessary anymore
    • Ines: asked about where the access control components are located in frontend code: as a general guide, you can always search previous MRs, but in her personal case Moritz already knows where everything is
    • Liza: regarding the iteration workflow, should everyone ask questions by wednesday already or should reminders be done on wednesday: reminders should be sent on wednesday already
    • Mo: does the Jenkins access token we use for Gitlab has API permissions: Markus has no idea, but we should investigate in an issue (or find it easily): create issue with question
    • Moritz: (mic didn't work>)
    • Peter: his talk would have been for today, but what should we do now: Markus wasn't sure about whether there is enough time and also the decision progress isn't so far yet, so talk will need to be postponed
    • Vseslav: is there a template for research investigations like #2302: no there is none yet, it is rather a free-writing task