Meeting 07.04.2025

Attendees

  • Markus
  • Stefanie
  • Richard: did not approve
  • Maiia
  • Andrei: did not approve
  • Christoph Schreiner
  • Christoph Kraus (Chris)
  • Ben
  • Philip: did not approve
  • Johannes
  • Moritz

Buddies

  • Ben & Philip
  • Moritz & Richard
  • Andrei & Maiia & Chris
  • Stefanie & Christoph
  • Filip & Johannes & Richard (Infrastructure)
  • Lukas & Jannis (Project)

Agenda

  • 09:00 start
  • Meeting Notes: Ben
  • Welcome: Technical skills
  • Overall goal of workflow: self-organization instead of micro-management (FLOSS certificate)
  • Everything assigned to you and in current iteration should be worked on:
    • if you cannot fully do it, you should at least find out if it can be done by you in one week (or help is needed or issue should be split etc.).
    • make sure to do 3 reviews (at least comment or approval)
    • make sure to not get behind
  • always give life signs
    • at least weekly
    • better after every block of work (fixed working hours)
    • at least write: I am stuck here
    • to avoid spending lots of time on something that is maybe not so important
  • create issues
    • left-overs in MRs
    • if something is discussed
    • if you find something incomplete
    • if something violates the guidelines
  • then:
    • you can assign yourself the issue and put into the next iteration (until Thursday!)
    • but don't immediately work on it
    • issues should be shortly acknowledged in meeting
    • all such issues count to your progress
  • already rejected application to have more time for you
  • deadline Thursday important for me
    • so that I have time to plan/answer
  • person who created MR can resolve
  • with questions you might also approve
  • copy review checklist as needed
  • current focus 0.5.0 release:
    • migrations (done?)
    • security updates
    • CI
    • rust 1.86 update?
    • add yourself to team, mark as "release critical"
    • small bug fixes, mark as "release critical"
  • break
  • release procedure:
    1. merge of last MRs
    2. manual tests
    3. merge dev to master
    4. release master
  • PermaplanT Anzeige Permakultur Magazin
  • buddy talk: use cases and issues, collaboration?
    • created value, not eagerness, is what counts: ideas how to simplify use cases
    • also assign "done" use cases or assign by technical skills?
  • Tasks for Everyone
  • Development Board
    • Andrei
    • Ben
    • Christoph Kraus (Chris)
    • Christoph Schreiner
    • Johannes
    • Maiia
    • Moritz
    • Richard
    • Stefanie
    • Philip

Tasks for Everyone

To be done until Thursday 10.04.2025 23:59:

  • write&check use cases
  • buddy talk: use cases and issues
  • collaboration talk: use cases
  • review at least 3 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

  • 09:00 start
  • Meeting Notes: Ben
  • For:
    • Christoph Kraus (Chris): CI/CD, Docker, Python
    • Philip: svelt, react/vue/angular
    • Ben: prettier, tsc, npm, zustand, React Query, React, tailwindcss
    • Maiia: React, Typescript, Konva, React Query, Zustand, npm, webpack, SCSS
    • Moritz: DB-Migrations (Liquibase, Flyway, SQLite), CI/CD, Openshift, Frontend Stores
    • Richard: Docker, Networking, npm/pnpm, Rust, Makefile
    • Johannes: IT-Security, Logging and Collection, SIEM Stuff, SoC Stuff, Makefile
    • Filip: Did not attend
    • Stefanie: prettier, vite, figma
    • Andrei: Typescript, npm, prettier
    • Christoph Schreiner: Python, npm, Finding bugs

FLOSS workflow:

  • Overall goal: self-organization instead of micro-management (FLOSS certificate)
  • Everything assigned to you and in current iteration should be worked on:
    • if you cannot fully do it, you should at least find out if it can be done by you in one week (or help is needed or issue should be split etc.).
    • make sure to do 3 reviews (at least comment or approval)
    • make sure to not get behind
  • always give life signs
    • at least weekly
    • better after every block of work (fixed working hours)
    • at least write: I am stuck here
    • to avoid spending lots of time on something that is maybe not so important
  • create issues
    • left-overs in MRs
    • if something is discussed
    • if you find something incomplete
    • if something violates the guidelines
  • then:
    • you can assign yourself the issue and put into the next iteration (until Thursday!)
    • but don't immediately work on it
    • issues should be shortly acknowledged in meeting
    • all such issues count to your progress
  • already rejected application to have more time for you
  • deadline Thursday important for me
    • so that I have time to plan/answer

Notes:

  • Give feedback based on what technologies you are comfortable with.
  • Question about MR comments from Moritz: Should we close review comments by ourselves or wait for Markus? => resolve comments yourself when done
  • Question about MR merging from Ben: Should we merge small merge requests with enough approvals ourselves? => if not critical, wait for Markus
  • Comment from Christoph K.: What should we do if review blocks approval? => Approve so it does not hold up the merge request if not critical flaw, should take a look
  • person who created MR can resolve comments
  • Question from Moritz about docs: should you copy down checklist from review template? => copy as needed

Release and Tasks:

  • current focus 0.5.0 release:

    • migrations (done?)
      • Status update from Richard: Looking into it, should be working but pipeline still blocking
    • security updates
    • CI
    • one last big MR
    • rust 1.86 update? -> no later
    • add yourself to team, mark as "release critical"
    • small bug fixes, mark as "release critical"

  • release procedure:

    1. merge of last MRs
    2. manual tests
    3. merge dev to master
    4. release master

  • PermaplanT Anzeige Permakultur Magazin

  • buddy talk: use cases and issues, collaboration?

    • created value, not eagerness, is what counts: ideas how to simplify use cases
    • also assign "done" use cases or assign by technical skills?

  • break

  • Tasks for Everyone

  • Development Board

    • Andrei
    • Ben
      • fixed blockers with onboarding on windows setup, nextcloud folder issue
    • Christoph Kraus (Chris)
    • Christoph Schreiner
      • no blockers but open issues to be worked on
    • Johannes
      • found issue, made some good progress
    • Maiia
      • working on bug report for typeshare
      • discussion about brushes
    • Moritz
      • working on open issues/use cases, guidelines mostly done, working on mockups
    • Philip
      • working on onboarding, had some setup issues
    • Richard
      • Migrations now passing, now in review. looking at CI failure next
    • Stefanie
      • mockups done, looking at reviews

  • MR about cleanup entity.rs: Unrealistic to fix remaining problems of incomplete APIs, add this to next release