diff --git a/lfscs-meetings/20240402.md b/lfscs-meetings/20240402.md
new file mode 100644
index 0000000..36cfda7
--- /dev/null
+++ b/lfscs-meetings/20240402.md
@@ -0,0 +1,61 @@
+# Meeting 2024.03.19
+
+## Hosts
+* Alessandro Carminati
+* Vikas Gupta
+
+## Attendees
+*
+
+## Agenda
+
+* Past items
+    * Results of the pool
+```
+       Kernel address space integrity............................................50
+       ##################################################
+       Memory allocators.........................................................47
+       ###############################################
+       Interrupt management......................................................38
+       ######################################
+       Boot......................................................................30
+       ##############################
+       Clock timers..............................................................24
+       ########################
+       Scheduler.................................................................20
+       ####################
+       Multicore interference....................................................20
+       ####################
+       Hardware access...........................................................18
+       ##################
+       Networking................................................................17
+       #################
+       Security, File system......................................................6
+       ######
+```
+       6 Voters
+
+* Planned agenda
+    * **Clarification on System Composition and Analysis Scope**: Some 
+      members of the working group are questioning the efficacy of 
+      immediately start searching safety concepts to analyze Linux 
+      components.
+      They argue that we should first define the composition of the
+      systems we're examining, as this will dictate our focus areas. 
+      Clarifying whether our analysis scope encompasses only Linux or
+      includes external systems like safety islands and watchdogs is
+      crucial.
+    * **Initiating Poll for New Safety Strategy and Roadmap Elaboration**:
+      The focus has shifted to initiating a poll to craft a new strategy
+      for safety concepts, following discussions about the roadmap in the
+      previous meeting. This strategy will be pivotal for conducting a 
+      thorough analysis of Linux components and identifying potential 
+      interdependencies. The current roadmap serves as a framework for 
+      the working group to generate a list of safety concepts, which will 
+      then inform the in-depth analysis process.
+
+## Meeting minute
+
+*
+
+## Action items