docs: week 2 meeting minutes

docs/minutes/week2-meeting-minutes.md

@@ -0,0 +1,51 @@
+# Week 2 meeting minutes
+
+| Date         | 21 November 2025                                                           |
+| ------------ | -------------------------------------------------------------------------- |
+| Time         | 16:46 - 17:10; Duration: Expected 32 minutes; Actual 24 minutes            |
+| Location     | DW PC Hall 2                                                               |
+| Chair        | Natalia Cholewa                                                            |
+| Minute Taker | Steven Liu                                                                 |
+| Attendees    | Aysegul Aydinlik, Mei Chang van der Werff, Oskar Rasieński, Rithvik Sriram |
+
+## Team allocation and responsibilities during week 3
+
+4 people should be in the UI development team, and 2 people should be in the server development team (UI has more functionality to do)
+### Common TODOs
+1. Submit signed Code of Conduct document by Monday.
+2. There will be a **Discord call on Monday starting around 15:00 / 16:00** (Final meeting time on Discord) to discuss these points:
+	- **IMPORTANT:** Agree on basic attributes and methods for data structures (`Recipe`, `Ingredient`, etc.)
+	- Structure project progress through GitLab issues and time-bound milestones for each 4.x requirement in backlog.
+### UI Team
+- **Composition:** *Aysegul Aydinlik, Mei Chang van der Werff, Rithvik Sriram, Natalia Cholewa*
+- **TODOs:** 
+	- Create a JavaFX client that can display and edit recipes, where the UI is structured similar to the backlog reference design
+	- For this the team can work with locally available mock data & unit testing after the schema has been determined after Monday (24th November)'s Discord call.
+### Server Team
+- **Composition**: *Oskar Rasieński, Steven Liu*
+- **TODOs:**
+	- Define a list of REST endpoints that the client will call
+		- Also write this list in a document `docs/api.md` so the frontend team has a reference.
+	- Build CRUD functionality and storage to a database for the relevant data structures, any other functionality to be built if communicated from frontend
+
+### Code review process
+
+- Each feature should be a branch classified as either concerning server/client/commons.
+- Merging a feature requires approval from all other people from your own team and 1 person from the other team.
+	- Rationale: Everyone working in the same codebase as you needs to know what's going on, and approval from one of the other team is needed since they need to continue working on your codebase the next week. 
+## Technical details
+### Web protocol stacks (REST vs. WebSockets)
+- **REST** used when:
+	- fetching complete data
+		- E.g. fetching a list of all recipes stored in the server, or getting a single one.
+	- pushing new data
+		- E.g. creating a new recipe from scratch; this should trigger a server broadcast that propagates the new recipe to every client.
+- **WebSockets** used when:
+	- refreshing (4.2 requirements)
+		- E.g. The client sends updates in small chunks and then broadcast by server to propagate changes to client 
+### Java
+
+- **Don't hard-code strings**: Use Java resource bundles where possible (such that we have a head start in implementing *4.6? Internationalisation*).
+## Backlog implementation priorities
+
+- Start with building for completing *4.1 Basic requirements* in backlog, but start building server-side WebSockets infrastructure for *4.2 Automatic change synchronization*.