Meeting 30.03.2026

Next Meeting

Due to holiday next week is no meeting, we see each other again 13.01.2026. Nevertheless we do normal weekly iterations, simply without a meeting.

Attendees

  • Markus
  • Chris(toph) Kraus
  • Christoph Schreiner
  • Elia
  • Hannes
  • Ines
  • Liza
  • Lukas
  • Moritz
  • Mo(ritz) Adelsberger
  • Patrick
  • Peter
  • Vseslav
  • Helene (only listen)

Not here:

  • Ben

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
  • Talks:
    • Patrick: Security from DevOps Perspective: DevSecOps
  • Meeting notes: Chris(toph) Kraus
  • Security:
  • Liza: intro in PM/dev workflows
    • Liza: time estimation in issue template via /
  • One-Word Check-In
    Everyone describes how they feel in exactly one word.
    Twist: The next person must choose a word starting with the last letter of the previous one.
  • technicalities:
    • different comments in GitLab
    • pushing vs. suggestions
    • incident vs. issues
  • English writing:
    • use of symbols in thesis, e.g., parentheses (say that information this information is not essential but also function call etc.)
    • consistency, also symbols or formatting can be defined
  • proper workflows:
    • first clarify terminology (glossary), workflows and guidelines
    • it is easy to create mess, difficult to clean up
  • please read documentation guidelines:
    • small clarifications in usage of links
  • feedback round: terminology, workflows and guidelines
  • next step: cleanup of MRs
  • manually triggered pipeline with branch selection
  • Verein:
    • Saison gestartet
    • we have first members!
    • Statuten ab 1.3. voll rechtskräftig (gemeinnützig und mildtätig)
  • Org:
    • meeting notes always in "meetings" branch, initially copied by Markus
    • invitation&reminding
  • Dev:
    • Moritz: experimental branch proper setup?
  • Development Board
    • Chris(toph) Kraus*
    • Christoph Schreiner*
    • Elia*
    • Hannes*
    • Liza*
    • Lukas*
    • Ines*
    • Moritz*
    • Mo(ritz) Adelsberger*
    • Patrick*
    • Peter*
    • Vseslav Levchenko

Outlook

Tasks for Everyone

Tasks to be done until latest Thursday 02.04.2026 23:59 (normal iteration!):

  • suggest a talk in the meeting MR
  • cleanup of your MRs: check if there are issues in iteration to all your open MRs
  • submit some text with some terms/definitions relevant for your thesis
  • Weekly Regular Tasks

Statistics (19.03.2026 - 26.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

Meeting invitation was messed up, in the last iteration we had two meeting MRs.

Talks

  • upcoming talks:
    • Hannes (TBD, Debugging Nextcloud Images, CORS etc.)
    • Mo (TBD)
    • Lukas (TBD)
    • Vseslav (TBD)
    • Peter (TBD)
    • Elia (TBD)
    • Ines (TBD)
  • done talks:
    • Patrick (30.03, Security from DevOps)
    • 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
  • Talks:
    • Patrick (Security from DevOps)
    • Moritz asked: Any concerns running Ansible under a root user. Patrick says that if hardened correctly the risk can be minimized, but its a weakpoint.
    • Markus: new strategy to normally not execute Ansible directly on the production machine.
  • Meeting notes: Chris(toph)
  • Liza: intro in PM/dev workflows
    • Do time estimations in your issues to review.
    • Write into the calender how much time you have next week.
    • If an issues takes more than 40h, it should be split up.
    • Questions:
      • Markus: What analytics are you gathering? what are you trying to find out.
      • Liza: How long an issues takes to finish, from the Issue Review to Done.
  • One-Word Check-In
    • Everyone describes how they feel in exactly one word.
    • Twist: The next person must choose a word starting with the last letter of the previous one.
    • Chris: Workflow
    • Christoph: Wonderful
    • Elia: LittleBitOfTired
    • Hannes: Dreamy
    • Helene: Yawn
    • Ines: Nice
    • Lukas: Euphoric
    • Mo: Coding
    • Moritz: Grumpy
    • Patrick: Yawn
    • Peter: N
    • Vseslav: Driven
  • technicalities:
    • different comments in GitLab
    • pushing vs. suggestions
    • incident vs. issues
  • English writing:
    • use of symbols in thesis, e.g., parentheses: in normal English it says that information this information is not essential but in computer science it might mean a function call
    • can be distinguished by formatting, like monospace
    • consistency is important
    • also symbols or formatting can be defined
  • proper workflows:
    • first clarify terminology (glossary), workflows and guidelines
    • it is easy to create mess, difficult to clean up
  • please read documentation guidelines:
    • usage of links
  • Keycloak 2FA:
  • News:
    • Maiia got certificate
  • Verein:
    • Saison gestartet
    • we have first members!
    • Statuten ab 1.3. voll rechtskräftig (gemeinnützig und mildtätig)
  • Org:
    • meeting notes always in "meetings" branch, initially copied by Markus
    • invitation&reminding
  • Dev:
    • Moritz: experimental branch proper setup?
    • Keycloak changes: language, OTP
  • status round:
  • Development Board
    • Ben
    • Chris(toph) Kraus: workflow feedback, enable image based tests again
    • Christoph Schreiner: works on scraper override step
    • Elia: FAQ for the help page
    • Hannes: Terminology, define basic terms
    • Liza: working on structure of thesis
    • Lukas: started with research question this week
    • Ines: looking at frontend performance and onboarding. Wants to start working on benchmarking.
    • Moritz:
    • Mo(ritz) Adelsberger: setting up staging with Hannes.
    • Patrick: working on unexpected downtime of the pipeline
    • Peter: setting up local dev env, now working on concepts how to do Nextcloud integration.
    • Vseslav Levchenko: Wants to find a more specific topic for the thesis. Will finish up MRs.