diff --git a/lfscs-meetings/20240319.md b/lfscs-meetings/20240319.md
index 4721c53..d52903a 100644
--- a/lfscs-meetings/20240319.md
+++ b/lfscs-meetings/20240319.md
@@ -5,7 +5,14 @@
 * Vikas Gupta
 
 ## Attendees
-
+* Rob Wooley
+* Nagayama Asuka
+* Daniel Weingaertner
+* Igor Stoppa
+* Florian Wuhr
+* Gabriele Paoloni
+* Christofer Temple
+* Mikel Azkarate
 
 ## Topics & Notes
 
@@ -19,6 +26,19 @@
 ## Meeting minute
 
 * Wg Roadmap presentation
-* Discuss lfscs Members' contribution to the roadmap.
+    * Alessandro Presented himself
+    * Vikas presented himself
+    * Wg [Roadmap](https://github.com/elisa-tech/wg-lfscs/lfscs-meetings/resources/Linux.Features.for.Safety-Critical.Systems.activities.summary.pdf) presentation
+        * Mikel: Any timeline? Is this work targeted at 1-10 years?
+        * Alessandro: It makes no sense to have the work spread in long timeline, Linux is a rapidly changing software, our result might suffer [TOCTOU](https://en.wikipedia.org/wiki/Time-of-check_to_time-of-use)
+        * Igor: Linux is not safe, if we have other means e.g., watchdog or safe island, probably it make no sense to check certain components.
+        * Gabriele: As for the boot discussion, it makes sense, despite the method to use to qualify Linux, to analyze what the component does, and understand what can go wrong.
+        * Igor: Suggests to deprioritize components that can be monitored with external components/hardware.
+        * Gabriele: To understand what can be deprioritized, you need to analyze the system.
+        * Chris: Perhaps we can just agree on priorities and rearrange components analysis to comply with new priorities.
 
+* Discuss lfscs Members' contribution to the roadmap.
 
+## Action items
+* prepare a poll to query lfscs members about opinion about component priority
+* find a new ordered list, according with the poll result.