Meeting 06.10.2025

Attendees

Markus
Alfons (not approved)
Ben
Johannes
Justus
Liza
Maiia
Moritz
Paul
Richard (not approved)

Came later:

Hannes (later, unexecused)

Not here:

Andrei (unexcused, not approved)
Chris(toph) Kraus (unexcused, not approved)
Christoph Schreiner (unexcused)

Buddies

Andrei & Maiia & Alfons
Christoph & Liza
Ben & Chris
Moritz & Paul
Johannes & Richard
Justus & Hannes

Success Partners

Maiia & Moritz (Frontend)
Ben & Andrei & Alfons (Frontend)
Hannes & Johannes (DevOps)
Liza & Paul (PM)
Richard & Chris (Tooling)
Christoph & Justus (Backend)

Agenda

09:00 start
Meeting Notes: Liza
Welcome Alfons
- introduce success partners
- Alfons help with 1.0 and study
BBB: how notes work:
- copy Agenda down
- Note taker modify this copy based on what was actually said
- Markus modifies Agenda according what we skip etc.
importance of Thursdays deadline
workflow for creating workflows
guidelines:
- documentation: links
- user-facing messages
updating authors.md (Hannes prepared a template)
tech talk:
- differences production to others in frontend (feature flag)?
RQ brainstorming
- terminology: initiative vs. project
- pro/cons for each question
reminders:
- documentation guidelines: links
break until 10:05
reinsaat.at Demo on Friday afternoon
PM this week
Development Board
- Chris(toph) Kraus (not here)
- Liza
- Hannes
- Paul
- Ben
- Christoph Schreiner (not here)
- Johannes
- Justus
- Maiia
- Moritz
- Richard
- Andrei (not here)
- Alfons
- Tasks for Everyone

Outlook

Paul: iterations
Liza won't attend next meeting
workflows:
- onboarding (add to review issues, CODEOWNERS)
- iteration (how to prepare weekly issues, add in:progress)
- decisions (TBD)
eye strain
reviewing
- guidelines
- how to review
- workflow
maybe in two weeks? Hannes will give a short talk about how to debug network requests to Nextcloud
status (looking back):
1. meeting with success partner: journalling, review an MR together
2. current progress and blocks
talks:
tech talk: map overview sorting
last decisions for 1.0
- JSON
- Quality of infrastructure
Tasks for Everyone next week: update authors.md according the template

Tasks for Everyone

Tasks to be done until latest Wednesday 08.10.2025 23:59:

submission RQ brainstorming
reread guidelines (especially documentation and about error messages)
Regular Tasks, Reminders:
- Set issues to "status::in progress" if you worked on an issue

Muth, Moritz: 8 Dinu-Coreth, Andrei Cristian: 7 Raab, Markus: 6 Kuzmishyna, Maiia: 5 Kraus, Christoph: 2 Weilguni, Justus: 2 Bachinger, Paul: 1 Lakits, Lukas Anton: 1 Mokshantseva, Elizaveta: 1 Schlegel, Ben: 1 Ziehengraser, Johannes Leonhard: 1

Issue progress (status changes + closed)/ total assigned

Bachinger, Paul: 6/7 Dinu-Coreth, Andrei Cristian: 3/6 Kraus, Christoph: 5/7 Kuzmishyna, Maiia: 3/9 Mokshantseva, Elizaveta: 2/10
Muth, Moritz: 4/6 Raab, Markus: 3/3 Schlegel, Ben: 5/10 Schreiner, Christoph: 2/8
Weilguni, Justus: 4/4 Wutscher, Richard: 1/3 Zettl, Hannes: 1/3 Ziehengraser, Johannes Leonhard: 0/4 Total: 39 / 82

Meeting Notes

welcome Alfons
- success partners introduced each other
- Alfons helps with 1.0 and study
Introducing success partners
BBB: how notes work:
- copy Agenda down
- Note taker modify this copy based on what was actually said
- Markus modifies Agenda according what we skip etc.
- explanation of how to manage Issues, less discussion in meeting and more in issue tracker
importance of Thursdays deadline
- for project management
- this week the deadline is Wednesday!
workflow for creating workflows, quick summary:
1. Suggest a new Workflow in an issue
2. Document Workflow in a MR
3. Approve Workflow (MR)
4. Implement Workflow new issue+MR
5. Review Workflow (MR)
- For details please look at !1896
guidelines:
- documentation: links
- user-facing messages
- Explanation of how to document
updating authors.md
- Hannes prepared a template
- this week only be used by Alfons, next week others
tech talk:
- differences production to others in frontend (feature flag)?
- Configuration of how to enable/disable features?
- current solution: we don't implement Collaborators
RQ brainstorming
- terminology: initiative vs. project
- provide context
  - introduce terminology
- pro/cons for each question
- the more RQs for now, the better
- Example:
  - pro: could yield interesting result?
  - con: not enough data?
- For people without question yet:
  - just provide as many research questions as possible
  - reviewers should give further ideas with more RQs
  - order them (including the one suggested by reviews) by preference and then ask Markus for review
break
reinsaat.at Demo on Friday afternoon
- Hannes will do the fix Tuesday morning
Development Board
- Hannes
  - nextcloud
  - helps Paul with triage
- Ben
  - Stuck on Tanstack, new ideas:
    - CPU/network slowdown
    - mockup for requests to find faulty one
  - some issues reduced from iteration
- Johannes
  - decision
- Justus
  - problem with failing e2e
- Liza
  - couple issues to finish until tomorrow
- Maiia
  - If there are too little issues should take issues from iteration planning for next week (if available)
- Moritz
  - Talked about mobile usability issues
- Paul
  - triage
  - cutback on infrastructure issues
  - assigns issues this week instead of Liza
- Richard
  - Rust PIN and mostly infrastructure
- Alfons
  - onboarding (except of avatar)
  - start creating workflow how to collect improvements for guided tour
    - e.g. collect them via doc/releases/dev.md in a special section for user-facing changes

PermaplanT