---
# System prepended metadata

title: Meeting 9 February 2021 (Planning)

---

# Meeting 9 February 2021 (Planning)

## Topics/Agenda

- [x] Expectations of work delivered this week
- [x] What will everyone work on?
- [x] Technology choices per repo explained (wiki page) -> 3 different people who can write about it?

## Notes
==> Expectations of work delivered at the end of this week?
 
Each repository should be defined
Part of the UI (bare bone, proof of concept) of the editor and application should be implemented => Some (simple) Springboot service should be implemented to see if the application/communication works.
Start with the skeleton of the application and editor. 
Keep track of what everyone is working on so that no double work is done and merge conflicts won't occur.
Start on the databank, this can be an easy temporary implementation that works for testing.
How would we implement the map in the editor and the application. How would we do the navigation?

What resources is also need on the virtual wall?
- Only CPU heavy part is the ModelIngestionService, We want to use Kubernetes in the future to be able to be scalable, we can't upgrade the resources, we should be able to create virtual nodes for testing (Maxime).
- We will need enough storage if we want to implement different tours, we also need enough storage for all the package that need to be installed on the nodes.
- Docker need at least 4-8Gb RAM, Springboot also need quite a lot of RAM, so more would be better ;).
- Maybe a separate build node and a separate test node. 2 would be beneficial.
- For development, it would be easier to use Docker and Docker Compose, instead of Docker and Kubernetes.

==> What will everyone work on?
* Maxime: Add Buefy to tour-manager repo; Technology choices voor webapp
* James: Mail huis van kina and GUM
* Wim: Initialiseer springboot repo
* Wouter: AR unity integratie in Flutter
* Tom: Homepage Flutter
* Jone: Map init
* Marybeth: Webapp prototype editor; Technology choices voor tour app
* Vince: Depends on meeting of 10/02/2020; Technology choices voor backend
* Quinten: Gather information about testing
* nameless: Database definities & initialisation; Http requests tour app -> backend; Http requests webapp -> backend