Meeting 23.09.2024

Attendees

  • Yvonne
  • Markus
  • Lukas
  • Filip
  • Stefanie
  • Jannis

Planned Holidays:

  • Andrei
  • Christoph

Buddies

  • Stefanie & Christoph & Andrei
  • Jannis & Lukas

Agenda

  • 09:00 start
  • welcome game: mood check
  • protocol: Lukas
  • when to do and incorporate reviews
  • don't neglect documentation
  • release of new landing page + fix of share ID
  • methodology
    • more structure
    • reproducibility, be detailed in what was done/happens on the computer
    • avoid general statements, write how you will do it.
    • Concerns/problems of methods should be separated (usually called "Threats to Validity")
    • ! Overview first (who is involved, which machines, which components, ...)
  • new branch names schema, username needs to be replaced with a name chosen by you, which you don't change
  • branch names
  • brushing layer architecture (enum?) -> Jannis will talk with Daniel
  • Nextcloud Upgrade:
    • neuer Kalender
    • read-only PermaplanTDev access tbd
  • next two weeks limited time
  • CI issues
  • (Filip disconnect)
  • focus: dev branch
  • Task Board
  • 11:00 finish

Next time:

  • Iterations until Thursday
  • Issues <-> MR relations

Tasks for Everyone

To be done until Thursday 26.09.2024:

  • bring README.md in submission up to date (please with non-uni e-mail adr and telefone 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 26.09.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, bug fixing, more estimations
  • Jannis: complete last issues+MRs

Planned Holidays:

  • Andrei: RQs, categorize and improve issues (collaboration), remembering viewing state (UC extended)
  • Christoph: RQs, continue hierarchy

Meeting Notes

Code reviews improved over the last week but need to be done even more frequently (rule of thumbs: two for every MR). The quality of reviews should be improved by communicating what parts were reviewed. Assignees should tell reviewers which parts they each should focus on based on their expertise. Writing documentation should not be neglected and is part of the thesis without it being included in the actual thesis text. Documentation like Thesis should be worked on regularly. To stay productive one should reflect on personal preferences and keep in sync with the own biorhythm.

The next release should be done with minimal changes which will include landing page updates and changes to Nextcloud.

Instead of writing complicated sentences we should structure information using elements such as enumerate or itemize. This makes it clear for the reader at first sight and is also easier to write. Methodology should explain everything that is needed to answer the research questions and nothing else. It should specifically not include justifications, recommendations and comparisons. It should be started with an overview and then go into more detail. More general statements should be avoided.