Meeting 17.03.2025

Attendees

  • Markus
  • Stefanie
  • Johannes (no approval)
  • Moritz
  • Richard (no approval)
  • Christoph

Not here:

  • Filip
  • Andrei (no approval)

Buddies

  • Moritz & Richard
  • Stefanie & Christoph & Andrei
  • Filip & Johannes & Richard (Infrastructure)
  • Lukas & Jannis (Project)

Agenda

  • 09:00 start
  • Meeting Notes: Moritz
  • buddy talk: decisions
  • CI
    • PostgreSQL?
    • scraper data repo
  • methods/results:
    • directly consecutive (can even be in same chapter if you have several benchmarks)
    • define each setup precisely (e.g. git SHA), give them a name
    • don't use words with special mathematical meaning unless meant that way, e.g. significantly
    • no drama; it can be in intro or conclusion, though
    • everything with opinion must go to discussion/conclusion
    • rounding
  • consider using for LaTeX:
    • obviously TU Wien latex template
    • theorems (with restatable) for RQs
    • theorems or glossaries (if needed with glossaries-extra) for terms (e.g. see Jannis thesis)
    • siunitx for percent etc.
    • cleveref (or some other way of consistent naming of labels)
    • what you definitely don't need is savetrees as we never print it out anyway :-)
  • case study/discussion:
    • with garden
    • screenshot
    • talking about features you added
  • Tasks for Everyone
  • Development Board

Tasks for Everyone

To be done until Thursday 20.03.2025 23:59:

  • buddy talk: decisions
  • review requested MRs, including meeting MR
  • complete your issues or state in the issue any block/alternative
  • create/update issues for yourself

Do as needed:

  • request reviews
  • submit a page of text in submissions
  • get MRs done

Meeting Notes

  • CI
    • scraper data repo
      • updating files in-place as is currently done is not desired
      • artefacts should be stored in a separate folder
      • still open discussion if artefacts should be checked in or not
    • Current Build Issues
      • db:5432 - no response
      • no updates yet
  • Bachelor thesis
    • The research question is sometimes not the starting point but rather it is derived from other aspects such as hypothesis, the goals or used methodologies.
    • Define terms like Konva early and precisely. Latex theorems and glossaries can help with this.
    • Methodology and Benchmarks should be tightly coupled, preferably as consecutive chapters.
    • As part of the test setup it's important to also document the used software versions.
    • The conclusion can also include non-technical observation such as the improved user experience of the application.