agenda 02.01.2024 (#1143)

<!--
Check relevant points but **please do not remove entries**.
-->

## Basics

<!--
These points need to be fulfilled for every PR.
-->

- [ ] I added a line to [changelog.md](/doc/changelog.md)
- [ ] The PR is rebased with current master.
- [ ] Details of what you changed are in commit messages.
- [ ] References to issues, e.g. `close #X`, are in the commit messages
and changelog.
- [ ] The buildserver is happy.

<!--
If you have any troubles fulfilling these criteria, please write about
the trouble as comment in the PR.
We will help you, but we cannot accept PRs that do not fulfill the
basics.
-->

## Checklist

<!--
For documentation fixes, spell checking, and similar none of these
points below need to be checked.
Otherwise please check these points when getting a PR done:
-->

- [ ] I have installed and I am using [pre-commit
hooks](../doc/contrib/README.md#Hooks)
- [ ] I fully described what my PR does in the documentation
- [ ] I fixed all affected documentation
- [ ] I fixed the introduction tour
- [ ] I wrote migrations in a way that they are compatible with already
present data
- [ ] I fixed all affected decisions
- [ ] I added automated tests or a [manual test
protocol](../doc/tests/manual/protocol.md)
- [ ] I added code comments, logging, and assertions as appropriate
- [ ] I translated all strings visible to the user
- [ ] I mentioned [every code or
binary](https://github.com/ElektraInitiative/PermaplanT/blob/master/.reuse/dep5)
not directly written or done by me in [reuse
syntax](https://reuse.software/)
- [ ] I created left-over issues for things that are still to be done
- [ ] Code is conforming to [our Architecture](/doc/architecture)
- [ ] Code is conforming to [our Guidelines](/doc/guidelines)
- [ ] Code is consistent to [our Design Decisions](/doc/decisions)
- [ ] Exceptions to any guidelines are documented

## Review

<!--
Reviewers can copy&check the following to their review.
Also the checklist above can be used.
But also the PR creator should check these points when getting a PR
done:
-->

- [ ] I've tested the code
- [ ] I've read through the whole code
- [ ] I've read through the whole documentation
- [ ] I've checked conformity to guidelines

Author: markus2330

doc/changelog.md

@@ -25,8 +25,10 @@ Syntax: `- short text describing the change _(Your Name)_`
 - Added Meeting Agenda&Notes for 20.10. 9:00 _(Markus Raab, Samuel)_
 - Added Meeting Agenda&Notes for 27.10. 9:00 _(Markus Raab, Jannis)_
 - Added Meeting Agenda&Notes for 04.12. 9:00 _(Markus Raab, Daniel)_
-- Added Meeting Agenda for 11.12. 9:00 _(Markus Raab)_
-- Added Meeting Agenda for 18.12. 9:00 _(Markus Raab, Christoph)_
+- Added Meeting Agenda&Notes for 11.12. 9:00 _(Markus Raab)_
+- Added Meeting Agenda&Notes for 18.12. 9:00 _(Markus Raab, Christoph)_
+- Added Meeting Agenda&Notes for 27.12.2023 9:00 _(Markus Raab, Daniel)_
+- Added Meeting Agenda for 02.01.2024 9:00 _(Markus Raab, Daniel)_
 - _()_
 - _()_
 - _()_

doc/meetings/2023_12_27.md

@@ -0,0 +1,62 @@
+# Meeting 2023-12-27
+
+## Attendees
+
+- Markus
+- Yvonne
+- Daniel (Protocol done)
+
+Break:
+
+- Samuel
+- Jannis (Protocol done)
+- Christoph (Protocol done)
+- Moritz
+
+## Buddies
+
+- Moritz & Samuel
+- Daniel & Christoph & Jannis
+
+## Agenda
+
+- 09:00 welcome
+- Protocol: Daniel
+- Next meeting 2nd January 9:00 Chris, Daniel
+- [sprint plan](https://project.permaplant.net)
+
+## Tasks for Everyone
+
+To be done until **Sunday 31.12.2023**:
+
+1. buddy talk topic: improvement of documentation
+2. do/update [sprint plan](https://project.permaplant.net)
+3. approve meeting PR [#1129](https://pull.permaplant.net/1129/files),
+   check for [requested reviews](https://pulls.permaplant.net/?q=is%3Aopen+user-review-requested%3A%40me)
+
+If possible/needed, do:
+
+- create/update issues/tests (behavior driven) as needed for future tasks
+- get current issues, PRs and use cases (UC) [done](../usecases/README.md)
+- do reviews of PRs in main repo and submissions
+- submit a (short) text in submissions
+
+## Individual Tasks
+
+To be done until **Sunday 31.12.2023**:
+
+- Daniel: PRs finish, continue drawing layer frontend, create drawing layer backend issue, check events performance, create layers and label layer issues
+
+Break:
+
+- Christoph: finish docu&scraper, plants hierarchy+relations
+- Moritz (?): create shade layer UC issues, group instead of layers, heat map, write about performance tests
+- Samuel: reviews, help others, documentation of unit tests
+- Jannis: push draft NC chat, PermaplanT: de+en plant names
+
+## Meeting notes
+
+- Polygons can be closed by clicking on start point
+- bezier anchors should always be shown when in editing mode of polygon
+- lines should be stored relative to starting point so that moving of elements can be done equally for each element
+- all error toasts should be automatically closed

doc/meetings/2024_01_02.md

@@ -0,0 +1,59 @@
+# Meeting 2023-01-02
+
+## Attendees
+
+- Markus
+- Yvonne
+- Daniel (Protocol done)
+
+Break:
+
+- Samuel
+- Jannis (Protocol done)
+- Christoph (Protocol done)
+- Moritz
+
+## Buddies
+
+- Moritz & Samuel
+- Daniel & Christoph & Jannis
+
+## Agenda
+
+- 09:00 welcome
+- Protocol: Daniel
+- [sprint plan](https://project.permaplant.net)
+
+## Tasks for Everyone
+
+To be done until **Friday 05.01.2024**:
+
+1. buddy talk topic: improvement of documentation
+2. do/update [sprint plan](https://project.permaplant.net)
+3. approve meeting PR [#1129](https://pull.permaplant.net/1129/files),
+   check for [requested reviews](https://pulls.permaplant.net/?q=is%3Aopen+user-review-requested%3A%40me)
+
+If possible/needed, do:
+
+- create/update issues/tests (behavior driven) as needed for future tasks
+- get current issues, PRs and use cases (UC) [done](../usecases/README.md)
+- do reviews of PRs in main repo and submissions
+- submit a (short) text in submissions
+
+## Individual Tasks
+
+To be done until **Friday 05.01.2024**:
+
+- Daniel: PRs finish, continue drawing layer frontend, create drawing layer backend issue, check events performance, create layers and label layer issues
+
+Break:
+
+- Christoph: finish docu&scraper, plants hierarchy+relations
+- Moritz (?): create shade layer UC issues, group instead of layers, heat map, write about performance tests
+- Samuel: reviews, help others, documentation of unit tests
+- Jannis: push draft NC chat, PermaplanT: de+en plant names
+
+## Meeting notes
+
+- new layer: - modal with name and type (only drawing and labels) - new layer will be placed after enabled one - new layer is visible with 100% opacity
+- drawing: - arrows should be available

doc/usecases/assigned/create_layers.md

@@ -14,6 +14,7 @@
   - User has opened the app.
 - **Main success scenario:**
   - The user can create a new drawing or labels layer.
+  - These layers should give hints that they are not semantic for the application.
 - **Alternative scenario:**
 - **Error scenario:**
   - The user attempts to create the layer but the app is experiencing technical difficulties, e.g. too many layers were already created, and is unable to complete the request, displaying an error message.

doc/usecases/assigned/hydrology_layer.md

@@ -18,7 +18,6 @@
     For example: surface water runoff, natural reservoirs, gullies, rills, etc.
     This includes positioning the areas in the appropriate location.
   - Moisture or dry areas can be added by a small (rills) or big brush (surface water) to draw on the moisture layer.
-  - Arrows can be used to indicate water flow.
 - **Alternative scenario:**
   - The user accidentally edits, moves or removes an element and uses undo to correct the mistake.
   - The user accidentally adds an element and deletes it with the "delete" or "undo" functionality.

doc/usecases/assigned/warnings_layer.md

@@ -14,8 +14,10 @@
   The user has opened the app and has selected the warnings layer.
 - **Main success scenario:**
   - Warnings can be individual elements or connecting two elements, when modifying elements on the map:
-    - shade mismatch
     - nearby antagonists
+    - shade mismatch
+    - hydrology mismatch
+    - plant is on unsuitable zone
   - The user successfully adds, edits, moves and hides warnings.
 - **Alternative scenario:**
   The user accidentally adds, edits, moves or hides the wrong warnings and uses the app's undo function to correct the mistake.

doc/usecases/current/drawing_layer.md

@@ -14,10 +14,14 @@
   The user has opened the app and has selected the drawing layer.
 - **Main success scenario:**
   - The user successfully adds, edits, moves, removes and deletes custom drawings of any color of following forms:
-    - polygons (consisting of lines and bezier)
+    - free drawings
+    - ellipses
+    - rectangles
+    - polygons (consisting of lines and bezier helper-points, that can be created by dragging existing lines)
       - open without filling
       - closed with 3 different fillings
     - icons from Nextcloud
+    - Arrows can be used to indicate water flow.
 - **Alternative scenario:**
   - The user accidentally edits, moves or removes an element and uses undo to correct the mistake.
   - The user accidentally adds an element and deletes it with the "delete" or "undo" functionality.