Meeting 11.08.2025

Attendees

  • Markus
  • Moritz
  • Andrei (not approved)
  • Liza
  • Maiia (not approved)
  • Christoph Schreiner
  • Paul
  • Richard (not approved)

Cannot come:

  • Ben (not approved)
  • Johannes
  • Chris(toph) Kraus (not approved)

Buddies

  • Christoph & Liza
  • Ben & Chris
  • Moritz & Paul
  • Andrei & Maiia
  • Johannes & Richard

Agenda

  • 09:00 start
  • Meeting Notes: Andrei
  • Liza: presenting changes to issue management
    • Codeowners
    • creating issues
    • milestones
    • retrospectives
    • timeslots one week in advance
  • Please Support Liza
    • definition of done
  • Terminology update:
  • current planning time (make terms longer to make them clear)
  • how to quote
  • round:
    1. buddy talk
    2. socratic questioning
    3. progress previous and next week
  • Tech-Talk:
    • schedule
    • down migration enum
    • DateTime
  • submissions book-keeping:
    • OS+editor
    • browser
    • availability
  • break
  • Next week: Paul Talk
  • I have little time this week
  • Liza Project Management
  • buddy talk:
  • Development Board
    • Andrei
    • Ben (not here)
    • Chris(toph) Kraus (not here)
    • Christoph Schreiner
    • Johannes (not here)
    • Liza
    • Maiia
    • Moritz
    • Richard
    • Paul
    • Tasks for Everyone

Tasks for Everyone

To be done until latest Thursday 14.08.2025 23:59.

Tasks:

  • review at least 2+2*X (X = number of created MRs), including meeting MR
  • submission of RQs/goal
  • Schedule your working time in PermaplanTWork calendar
    • Create a new Event for each timeslot you plan to work and name it "{Name} (available)" example: "Liza (available)".
    • If you know that you always have time in a specific timeslot, you can also repeat this event.

Do as needed (same deadline):

  • create MR in submissions repo with your current RQs
  • state in the issues any block/alternative/progress
  • submit a page of text in submissions
  • get issues/MRs done
  • request reviews
  • create/update issues for yourself

To be done before the meeting:

  • buddy talk: how can project management support you best?
  • finish your assigned tasks of the iteration

Meeting Notes

  • Liza: presenting changes to issue management, details will be in other MR

  • Issues

    • Use templates
    • Add scopes
    • Please include time estimation on creation:
      • ~ 1 h
      • ~ 3 h
      • ~ 1d = 8h
      • ~ 2d = 16h
      • ~ 1w = 40h
    • estimation can be added later if not known at time of creation, tag with triage needed
    • time tracking as you work on it Q: - Maiia: skeptical about time estimation not easy to do, not the best fit for our project as people are not working full-time; would 'weight' fit better? -> we will try to estimate the effort, we use the time because it is a feature already well integrated in GitLab (so we do a sort of weight estimation represented in time) Q: - Richard: the estimation 'steps' might be a bit big, thinking that most people only work about 10h a week, so 1w=40h seems very big Q: - Christoph: include the time estimation options in the template so we don't need to look it up Markus: we should do checklist related to the estimation

  • Milestones

    • once a month, release
    • can tag the issues with the relevant milestone Q: - Andrei: should we do the milestone planning together? -> no, this will be provided

  • Retro

    • After every release (monthly)

  • Time planning

    • by thursday for next week
    • you can remove later if you can't work on that day

  • Codeowners:

    • helps with automatic assignment of reviewers based on files/folders
    • to be reviewed by everyone in an upcoming MR Q: - Christoph - maybe problem if only one person is 'responsible' for that part of code (e.g. Scraper) Q: - Paul - have a 'main' person responsible for a part of code, also in terms of who might know that code the best -> next buddy talk to also discuss how we can improve project management

  • Terminology update:

    • current planning time (make terms longer to make them clear) -> have a clear definition of your terms to make sure you keep it consistent -> if you use one word in different contexts to represent different terms, then you should expand on the term to ensure clarity
    • how to quote -> using terminology (or generally text or ideas) from other papers - ensure proper quotation and citation; when rephrasing, don't use quotation but use proper citation!

  • buddy talk, socratic questioning

  • progress previous and next week

    • Andrei:
      • buddy talk good, talked about socratic questioning and helped with each other's RQs
      • this week focus on preparing for thesis writing (next week more time to focus on that)
    • Christoph:
      • met with Liza, talked about socratic questioning, open issues
      • writing session with Maiia and reviewed questions, tried to refine what 'performance' means
      • A bit hard to apply some of the socratic questioning elements
      • struggling with some sql work because of chaning enums (they need to be recreated)
    • Liza:
      • talked with Christoph on Friday
      • progress with writing presentation.
    • Maiia:
      • discussed about socratic questioning and reviewed the research questions
      • inputs for what to include and not include in the questions, to not limit what the thesis wil lbe about (for example, how exactly performace can be improved, what is performance, etc.) -> the thesis is a 'context' around the RQ, in which you then answer the question
      • good progress on most tasks, did not have time for one
    • Moritz:
      • did not do buddy talk, will do this week
      • socratic questioning: tried it on his own, but would like to apply it to other people's RQs as well
      • did not have as much time as planned, could not progress a lot on his own tasks
      • met with Liza to discuss the use cases and tickets to be created
    • Paul:
      • no time for buddy talk
      • worked on setting up the project and the new things (Email) he will be working on, took longer than expected but should be ready this week
    • Richard:
      • no time for buddy talk last week
      • progressed with his infra work
    • Johannes on holiday, maybe meet with Ben

  • Tech-Talk:

    • SQL statement for updating enum
      • no experience
    • DateTime
      • Only use the "date" part and agree to use a default time with no timezone
      • Write guideline on how this should be used
      • probably no changes needed in the code as we don't use time anywhere, only date

  • break

  • Markus will be less available this week

  • Next week: Paul Talk

  • Development Board

    • Andrei
    • several issues in review, waiting for more reviews
    • to triage measurement related issues, make small MRs
    • Christoph Schreiner
    • rerun scraper for master
    • new issue for plant icon changes (track in the release)

  • icons should be tested, some problems - plant hierarchy - antagonist/companions MR -> still needs some cleanup

    • Liza
      • create more issues on current work, to track better the progress
      • for now work more on what we have (improve current issues), to not create big gap between where we are and what we want to achieve
    • Maiia
      • one task still waiting for reviews,
      • heatmap colors vs relation colors
      • 'play' with opacity to ensure colors don't clash too much
      • colors are hardcoded, make new issue for extracting them
      • brush shape issue - can be improved by increasing number of points
    • Moritz
      • 2 MRs still need more reviews
      • task in progress not release critical
      • mobile design - working on it -> make an MR to start getting inputs from others
    • Richard
      • map import -> check again, all info should be there, talk to Filip and do it together with Paul, write documentation
      • release task -> only a few small open points
      • split into sub-issues to track better where there is progress and where you might be blocked
    • Paul
      • CI broken - upgrade image
      • then continue work on other things (Email)

  • review at least 2+2*X (X = number of created MRs), including meeting MR

  • submission of RQs/goal

  • Schedule your working time in PermaplanTWork calendar

    • Create a new Event for each timeslot you plan to work and name it "{Name} (available)" example: "Liza (available)".
    • If you know that you always have time in a specific timeslot, you can also repeat this event.

Do as needed (same deadline):

  • create MR in submissions repo with your current RQs
  • state in the issues any block/alternative/progress
  • submit a page of text in submissions
  • get issues/MRs done
  • set your time estimation on issues you are currently working on with:
    • ~ 1 h
    • ~ 3 h
    • ~ 1d = 8h
    • ~ 2d = 16h
    • ~ 1w = 40h
  • track your actual time on the issues
  • request reviews
  • create/update issues for yourself

To be done before the meeting:

  • buddy talk: how can project management support you best?
  • finish your assigned tasks of the iteration