09:00 start
Meeting Notes: Stefanie
buddy talk: report from amazing tools and skills we have:
- trying out copilot integration, https://coolors.co for generating color palettes
- note that trying out tools, also takes time
MR Reviews
- don't invite everyone
- instead specific invitation, with specific checks
- describe which manual tests you already did
project:
- board was added on https://project.permaplant.net (for Lukas & Jannis)
- first issue: working on access control
- backend should return 404 for maps with no access, so it should be handled as a map not existing
Scientific English:
- simple rule: ' only for possessive, so it can only be "its"
- Methods should not have anything about approach or implementation
- answer only one RQ (sub-RQs are okay)
- approach vs. methodology: approach is about how how the software does something, methodology is just how you run and measure the software
CI
- next meeting?
- build errors
- make dev green again+new map 1
- Maintenance Time Slots?
09:30 short break
Extra Meetings February?
- Project: done
- Infrastructure: open
- Retrospective: next week (see Outlook above)
buddy talk next time: strength+support
- where lie your strengths? where do you need support?
10:00 break
validation documentation:
- rust vs ts: for rust null is an empty value, TS does prefer undefined for optional values (.? operator)
- but in other cases, null gets passed through
- so we need to adapt documentation of architecture again

PermaplanT