Meeting 17.08.2026

Attendees

  • Hannes
  • Johannes
  • Lea
  • Markus
  • Patrick
  • Peter
  • Vseslav
  • Chris

Left early:

  • Elia

Cannot come:

  • Noah (excused)
  • Liza (excused)

Not here:

  • Lukas (unexcused)

Last Time:

  • Moritz (last time)

Agenda

  • 09:00 start
  • Meeting notes: Moritz (Backup: Noah)
  • Welcome: What do I do for nature protection?
  • new Flyer/texts
  • no PermaplanT meeting on 7th September
    • Nextcloud calender already updated
    • reminder changed to be on Thursdays (for approval etc.)
  • AI usage for bachelor thesis
  • thesis submission
    • submit short texts as early as possible, especially:
      • RQ brain storming
      • method
      • terminology/background papers
    • grading
    • full draft reviews please only once, when everything is basically done
    • no further steps needed for certificate
  • Moritz recap (17.08), issues for:
    • use --devices in e2e/e2e.sh
    • remove PAGE_WIDTH and viewport_size
    • new test: for verifying usability issues
  • Warm Shower: Moritz
  • back and forth can also happen in one week: https://gitlab.tuwien.ac.at/perma/apps/planT/-/merge_requests/2431
  • status round: success partner/buddy
  • Development Board
    • Elia
    • Hannes
    • Johannes
    • Lea
    • Liza (not here)
    • Lukas (not here)
    • Markus
    • Moritz (last time)
    • Noah (not here)
    • Patrick
    • Peter
    • Vseslav
  • Tasks for everyone
  • Talks
    • Noah: (after release) current state of workflows and retrospective
  • release preps:
    • who does testing?

Tasks for Everyone

Please do until Thursday 20.08.2026 23:59:

  • fix all release critical issues
  • buddy or success partner: fix release critical problems together
  • All Weekly Regular Tasks

Outlook

  • manual test case workflow prioritization
  • no PermaplanT meeting on 7th September
  • Peter/chris re-onboarding after confirmation e-mail
  • test case transition to Gherkin in PlanT repo as well (after infrastructure)
  • PM next steps
    • meeting
    • workflows & guidelines & decisions
    • release planning (milestones? weight?)
  • documentation
    • database
    • ci
    • decisions
  • reviews
    • how to do reviews normally
    • when to do review
    • responsibilities
    • glossary: MR owner
  • please comment here if you want something added in the next meetings

Did Not Approve Last Meeting Notes In Time

  • Oberhauser, Lukas
  • Rasched, Adam Moritz
  • Zettl, Hannes
  • Wenty, Elia
  • Schreiner, Christoph

Statistics

Merge Request approved

Issue progress (status changes + closed)/ total assigned

Talks

  • upcoming talks:
    • Elia: presentation study (24.08)
    • Noah: workflow+testing improvements (after release)
    • Lukas
  • current talks:
  • done talks:
    • Moritz (17.08., recap + issues from e2e testing)
    • Peter (11.05. decision workflow, Nextcloud folder structure proposal)
    • Ines (27.04. static analysis, eslint)
    • Vseslav (20.04. PostgreSQL tools & tips; comparing databases)
    • Patrick (30.03, Security from DevOps)
    • Liza: various retrospective
    • Chris(toph) Kraus (02.02., workflow+developer perspective of e2e tests)

Notes

Flyer Feedback

  • Elia: Green blobs have different colors.
  • Hannes: Looks nice.
  • Johannes: Depiction of Loase is nice. Other font preferred (Less formal). Currently used: LiberationSans
  • Chris: Format works well.
  • Lea: Blue blobs are also different colors and the contrast is not always the best.
  • Moritz: Not sure if contrast is a problem when printed out. Keeping the different color blobs is fine too.
  • Patrick: Blobs should fully encapsulate the text.
  • Peter: Using slash instead of minus. Also provide an English flyer.
  • Vseslav: Sharp contrast at blob borders should be avoided for text areas.

AI usage for bachelor thesis

  • big impact on the environment
  • fine for spellchecking and similar tasks, as long as usage is documented
  • LaTeX template fixes are not really part of the thesis, but any generative AI use should still be documented according to TU Wien guidelines.
  • The implementation is an artifact of the thesis and therefore the same rules apply.
  • Used tools need to be documented, but it is not necessary to link to the libraries' documentation.