Meeting 30.09.2024

Attendees

  • Yvonne
  • Markus
  • Lukas (Protocol done)
  • Jannis
  • Filip
  • Stefanie
  • Andrei
  • Christoph

Buddies

  • Stefanie & Christoph & Andrei
  • Jannis & Lukas

Agenda

  • 09:00 start
  • welcome game: wind
  • protocol: Jannis
  • keycloak groups
  • be clear about backend vs. frontend: default value
  • release of new landing page + fix of share ID
  • Stef Präsentation: performance tooling
  • terminology:
    • everything what you measure
    • basically every word of RQ
    • central words and what is in the title
    • more structure!
  • brushing layer architecture (enum?) -> Jannis will talk with Daniel
  • Nextcloud Upgrade:
    • neuer Kalender
    • read-only PermaplanTDev access tbd
  • this week limited time
  • CI issues
  • Iterations until Thursday
  • Issues <-> MR relations
  • (Filip disconnect)
  • focus: dev branch, heatmap
  • time to harvest
  • Task Board
  • 11:00 finish

Tasks for Everyone

To be done until Thursday 03.10.2024:

  • bring README.md in submission up to date (please with non-uni e-mail adr and telephone number)
  • approve requested MRs, including meeting MR
  • create/update issues for yourself and assign to next iteration

Do as needed:

  • request reviews
  • buddy writing (Schreibtreffen)
  • submit a page of text in submissions
  • get MRs done

Individual Tasks

To be done until Thursday 03.10.2024:

  • Filip: add maps, methods collect data (3000 users, why is image loading so slow?)
  • Lukas: get UC shading layer done
  • Stefanie: RQs, look into tools (presentation), bug fixing, more estimations
  • Jannis: complete last issues+MRs
  • Andrei: RQs, categorize and improve issues (collaboration), remembering viewing state (UC extended)
  • Christoph: RQs, continue hierarchy proposals

Meeting Notes

Find a good name for Keycloak groups. Groups for dev and testing may be needed? Issues should be clearly separated into frontend/backend scoped. No release this week. Stef presentation next week on tooling.

Clarifying terminology:

  • term: should be properly introduced related to research question, like measured like "cpu cycle", "delay", units, and words that a central to work,
  • common words, not central to your work: are not introduced, don't need to be explained

Formatting can eliminate text that explains structure.

Pipeline works on master/dev. Please report pipeline errors and rebase MR branches to dev or master. All issues in the iteration should be worked on.