Meeting 26.05.2025

Attendees

  • Markus
  • Christoph Kraus (Chris) (not approved)
  • Ben
  • Moritz
  • Christoph Schreiner
  • Richard
  • Andrei
  • Johannes (not approved)
  • Stefanie

Cannot come:

  • Maiia (not approved)

Buddies

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

Agenda

  • 09:00 start
  • Meeting Notes: Andrei
  • buddy talk: review of research question, feedback of review
  • requirements for test maps?
    • a bit of everything
    • also one of everything? -> not needed
    • also get the dump
  • requirements for WSL?
  • warme Dusche Stef
    • review her thesis
    • goodbye
  • focus testing:
    • strategy (Chris)
    • extra plant test data? (Chris)
    • blank pages (Richard)
    • working together: manual tests or Chris push fixes/e2e
    • estimations of recurrence of regressions
  • break
  • Tasks for Everyone
  • decisions
    • what they are for
    • for all libs
  • CI improvements:
    • regular checks for CI pipeline
    • after CI problems: trigger scan to rebuild everything
    • check if CI also fails if it should
    • review of submissions
  • Development Board
    • Andrei
    • Ben
    • Christoph Kraus (Chris)
    • Christoph Schreiner
    • Johannes
    • Maiia (not here)
    • Moritz
    • Richard
    • Stefanie (last tasks)

Tasks for Everyone

To be done until Thursday 29.05.2025 23:59:

  • rebase/merge dev after e2e is fixed
  • update README.md in submissions:
    document your setup (OS, editor)
  • review 2x MRs in submission (background+method)
  • buddy talk: important decisions?
  • 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

Outlook Next Week

  • next talks:
    • Ben next week about a new react tool
    • Moritz, maybe about usability
    • Christoph Schreiner
    • Richard
  • new feature idea PermaplanTasks:
    • toggle states (protection against freezing, remove it again)
    • user/map configuration/view state strategy
    • highlight elements with open tasks
    • make updates of width/height/positions/notes also as (removable) events or as version history?
    • attributes splitup? (like drawing)
      • added/removed/notes/created/..
      • plant info (not editable data)
      • changeable data (width, height)
      • version history
      • PermaplanTasks
  • reconstruct text (nouns, verbs)

Meeting Notes

  • 09:00 start
  • Meeting Notes: Andrei
  • buddy talk: review of research question, feedback of review
    • Andrei, Ben - did not manage to do this
    • Chris - found some papers for e2e but not specifically for the topic he wanted
    • Christoph - could not find good papers, either too broad or not related to my topic
    • Johannes - only a few papers related to opentelemetry, but good start
    • Moritz - read through submissions, had feedback for Stef. Did not get to talk to Richard
    • Richard - sick, did not manage to do it and hopes to catch up
    • Stef - MRs from submission done, still to look into her open MRs in the main app
  • requirements for test maps?
    • how should maps look like? What are bottlnecks to test?
    • Maybe have one more 'realistic' map besides Loase, to get a feel on how a user would use a map
    • Map with one of every brush layer
    • Would be good to have access to existing test maps to use them on local environment (topic taken to infrastructure meeting next week)
  • requirements for WSL? (Stefanie?)
    • there is existing documentation, but it has gaps or parts where it's not specific enough
    • document what WSL version, what setup we use etc - Andrei
  • warme Dusche Stef
    • review her thesis
    • goodbye
  • focus testing:
    • strategy (Chris)
    • backend tests fail - could be because of not clean db
    • mdbook tests fail - there issue for it
    • e2e tests vs unit tests
      • write the easier tests first
      • unit tests are good at finding where the issue is
      • important to have use cases covered somehow
      • e2e tests are harder to write/ takes longer to get a proper coverage and feedback to devs is poor (manual tests even more so)
    • extra plant test data? (Chris)
    • blank pages (Richard)
    • working together: manual tests or Chris push fixes/e2e
    • estimations of recurrence of regressions
  • decisions
    • what they are for
    • for all libs to be introduced there must be a decision
  • CI improvements:
    • regular checks for CI pipeline
    • after CI problems: trigger scan to rebuild everything
    • check if CI also fails if it should
  • Tasks for Everyone
    • review of submissions
  • Development Board
    • Andrei
    • Ben
    • Christoph Kraus (Chris)
    • Christoph Schreiner
    • Johannes
    • Maiia (not here)
    • Moritz
    • Richard
    • Stefanie (last tasks)