Meeting 23.03.2026

Attendees

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

Not here (unexcused):

  • Ben
  • Lukas

Cannot come (sick):

  • Elia
  • Patrick

Buddies

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

Success Partners

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

Special Partners

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

Agenda

  • 09:00 start
  • Meeting notes: Vseslav
  • Everyone picks an emoji that represents their day and explains it in one sentence.
  • Vote: Should CI automatically fix formatting errors?
  • Vote: Language?
  • apricots and cherry blossom 🌸
  • motivation:
    • not only the grade
    • create sustainable earth surface
    • being proud excellent work
    • diversity
    • relay
  • commit as many mistakes as possible
    • but not twice
    • be open about them
    • and report so that we can learn from them
    • process/learning is part of finishing thesis
  • round: what you learned from mistakes
    • if issue is unclear reflect in own words
    • gitlab workflow
    • Pq4r method for understading information like academic texts or documentation or descriptions: https://subjectguides.york.ac.uk/study-revision/pq4r-method
    • testing first
    • iteration also on thesis (feature scope)
  • focus on quality, take your time
    • no hurry
    • less is more
  • Chris Talk: new e2e test workflow
  • 10/20/70 rule
    • reviews motivation (20%)+process
  • further weekly iteration obligations
    • move along all issues and give feedback to your issues
    • report if anything is blocking you/took much time so that PM can improve
  • 1.0.1 after-release status
    • BaseLayerImages
  • cloud.perma.health update
  • make MR Checklists shorter:
    • "Details of what I changed are in the commit messages." removed
    • also several lines in changelog are okay
  • Please keep the "Delete source branch" ticked
  • review workflows: do tests or do code review, write what you did
  • Development Board:

    • Ben (not here)

    • Chris(toph) Kraus

    • Christoph Schreiner

    • Elia (not here)

    • Hannes

    • Justus

    • Liza

    • Lukas (not here)

    • Maiia

    • Ines

    • Moritz

    • Mo(ritz) Adelsberger

    • Patrick (not here)

    • Peter

    • Vseslav Levchenko

    • Tasks for Everyone

Outlook

Tasks for Everyone

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

  • Weekly Regular Tasks
  • search background paper, add a sentence about it in submissions repo
  • update README.md in submissions as needed (working title, buddies, etc.)
  • get topic+date for talk

Statistics (12.03.2026 - 19.03.2026)

Merge Request approved

Raab, Markus: 13 Müller, Alfons: 8 Mokshantseva, Elizaveta: 6 Adelsberger, Moritz: 5 Kuzmishyna, Maiia: 5 Schreiner, Christoph: 5 Levchenko, Vseslav: 4 Muth, Moritz: 4 Graßl, Patrick: 3 Bachinger, Paul: 2 Stummer, Eszter: 2 Kraus, Christoph: 1 Schlegel, Ben: 1 Weilguni, Justus: 1

Issue progress (status changes + closed)/ total assigned

Adelsberger, Moritz: 5/5 Bachinger, Paul: 2/4 Dinu-Coreth, Andrei Cristian: 0/2 Graßl, Patrick: 1/8 Kraus, Christoph: 1/12 Kuzmishyna, Maiia: 8/13 Levchenko, Vseslav: 7/14 Mokshantseva, Elizaveta: 5/9 Muth, Moritz: 2/13 Müller, Alfons: 15/15 Oberhauser, Lukas: 3/4 Schlegel, Ben: 0/8 Schreiner, Christoph: 3/9 Weilguni, Justus: 8/16 Wutscher, Richard: 0/2 Zettl, Hannes: 0/5 Total: 60 / 139

Did Not Approve Last Meeting Notes In Time

  • Ben

Talks

  • upcoming talks:
    • Patrick (TBD, Security from DevOps)
    • Hannes (TBD, Debugging Nextcloud Images, CORS etc.)
    • Mo (TBD)
    • Lukas (TBD)
    • Vseslav (TBD)
    • Peter (TBD)
    • Elia (TBD)
    • Ines (TBD)
  • done talks:
    • Liza: 16.03, retrospective
    • Ben (02.03., FLOSS refactoring on library upgrades)
    • 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)
    • 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)

Meeting Notes

  • 09:00 start
  • Meeting notes: Lukas (Backup: Vseslav)
  • Everyone picks an emoji that represents their day and explains it in one sentence.
  • Vote: Which language should we use in meetings?

Both fine - 8 English - 2

Decision - stick to English.

  • Vote: Should CI automatically fix formatting errors?

Yes - 3 No - 6 I don't care - 1 Both fine - 1

Decision - no.

  • apricots and cherry blossom 🌸
  • motivation:
    • not only the grade
    • create sustainable earth surface
    • being proud excellent work
  • commit as many mistakes as possible
    • but not twice
    • and report so that we can learn from them
    • process/learning is part of finishing thesis
  • round: what you learned from errors

Markus: - biggest mistake: putting too much into one release, making it take longer - fix: split things, put non-critical things off when possible

Chris: - biggest mistake: not having a clean and stable for e2e tests - fix: a stable environment that's well used for tests

Christoph: - biggest mistake: always trying to make a perfect MR fixing everything, including things that aren't problems - fix: some things can be split or put off

Hannes: - biggest mistake: difficult to know when it's ok to go and ask for help - fix: structurally write down and recite what is my understanding of something and then ask someone to verify it (this helps to think more clearly)

Ines: - biggest mistake: often confused by git commands - fix: learn and practice more

Justus: - biggest mistake: tend to lose the scope when researching something, hard to maintain structure - fix: focus on one topic without getting too much off track

Liza: - biggest mistake: working on bigger ideas and forgetting smaller issues - fix: work on smaller issues more

Maiia: - biggest mistake: honey shouldn't be microwaved for more than a couple of seconds; implementing new solution with not enough testing - fix: any kind of experimental solution has to be tested as early as possible

Mo: - biggest mistake: rolling playbooks out on production - fix: wait/test until rolling out major infrastructure features

Moritz: - biggest mistake: always trying to get everything right the first time - fix: more efficient, iterated ways of implementation

Peter: - biggest mistake: underestimating how long certain issues take - fix: plan for pitfalls, edge cases, etc.

Vseslav: - biggest mistake: rushing to implement features without looking up existing code/templates/solutions for specific issues - fix: learn off other people's code for more efficiency

  • Chris Talk: new e2e test workflow
    • Overview:
      • E2E tests check if the whole system works as expected, from start to finish, just like a real user would interact with it
      • Currently 82 E2E tests; 70 more are in MR !2193
      • Goal - make sure most "Done" use cases are covered by E2E tests
      • Running E2E tests is a required step in the CI/CD pipeline before code gets deployed
    • Debugging:
      • Check test-report/report.html for E2E runs console output
      • Videos of test runs are available
      • Use --slowdown option to slow down the tests and actually see
      • Trace files are generated (use https://trace.playwright.dev/) for better debugging
      • To see the browser in action, use --headed flag while running the tests
    • Workflow introduction:
      • Purpose: standardize process for transforming use cases to E2E tests
      • Audience: developers, testers, QA
      • Ensures comprehensive, reliable, automatic and consistent test coverage
      • Step 1.
        • Who: developer, tester, QA
        • When: new features, before marking use case "done", expanding coverage, fixing bugs
        • Actions:
          • Read use case docs
          • Check for missing/unclear tests
          • Review manual & E2E test files
          • Create issues for missing/unclear tests
        • Result: issues created for writing or improving tests
      • Step 2.
        • Who: developer, domai nexpert, tester, QA
        • Actions:
          • Analyze which scenarios need tests (main, alt, error)
          • Decide on manual vs e2e
          • Identify smoke tests, dependencies, complexity
        • Result: Issue has detailed test proposal for prioritization
      • Step 3.
        • Who: product manager (with dev/QA input)
        • Actions:
          • PM sets Level of Criticality
          • Dev/QA provides technical metrics (complexity, regression likelihood, execution time)
      • Step 4.
        • Who: tester/contributor
        • When: during feature impl. or after issue creation
        • Actions:
          • Write Gherkin test cases
          • Follow manual testing guidelines
          • Measure and record exec time
        • Result: manual tests ready for MR
      • Step 5. Create MR
      • Step 6. Merge
      • Step 7. Implement E2E tests
        • Who: developer
        • When: after manual tests are merged
        • Actions:
          • Create e2e scenarios
          • follow e2e guidelines
          • tag tests as needed
          • remove automated scenarios for manual tests
        • Result: e2e tests ready for MR
      • Step 8. Create E2E MR
      • Step 9. Test and merge
      • Step 10. Update use case with coverage status
        • Who: developer/tester
        • When: after all MRs for a use case are merged
        • Actions:
          • Mark use case as done if fully covered
          • Update doc with tests
        • Result: use cases fully covered
      • Special cases
        • If a use case is already marked done but test cases are missing: follow full workflow
        • If feature is merged before tests are ready: create high priority issue to add missing tests

Vote: Do you need videos for e2e tests on CI? No - 6 Abstained - 1 Maybe - 4

  • checkbox in MR template
  • 10/20/70 rule
    • reviews motivation (20%)+process
  • further weekly iteration obligations
    • move along all issues and give feedback to your issues
    • report if anything is blocking you/took much time so that PM can improve
  • focus on quality, take your time
    • no hurry
    • less is more
  • 1.0.1 after-release status
    • BaseLayerImages
    • icons
    • base layer
    • Maiia
  • cloud.perma.health update
  • Justus Warme dusche
  • make MR Checklists shorter:
    • "Details of what I changed are in the commit messages." removed
    • also several lines inc hangelog are okay
  • Please keep the "Delete source branch" ticked
  • review workflows: do tests or do code review, write what you did
  • Development Board:
    • Ben (not here)
    • Chris(toph) Kraus
    • Christoph Schreiner
    • Elia (not here)
    • Hannes
    • Justus
    • Liza
    • Lukas (not here)
    • Maiia
    • Moritz
    • Mo(ritz) Adelsberger
    • Patrick (not here)
    • Peter
    • Vseslav Levchenko
    • Ines
    • Tasks for Everyone