-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding agenda for 20240430 discussion
Signed-off-by: Alessandro Carminati <[email protected]>
- Loading branch information
1 parent
86daeac
commit b04bd77
Showing
1 changed file
with
33 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
# Meeting 2024.04.30 | ||
|
||
## Hosts | ||
* Alessandro Carminati | ||
|
||
## Attendees | ||
|
||
## Topics & Notes | ||
|
||
* Past items | ||
* None | ||
|
||
* Planned agenda | ||
* Review TSC discussion about AoU [outcome](https://github.com/elisa-tech/tsc/wiki/24-Apr-2024) | ||
* LFSCS WG has yet to evaluate a feature as it lacks a system | ||
definition to focus, highlighting the need for a clear understanding | ||
of AoU. | ||
* While LFSCS may consume AoU externally, they may also develop them | ||
internally, with a requirement to provide feedback. | ||
* Feedback is meant to be back-propagated using Basil. | ||
* Basil needs an architecture definition document, which will be one | ||
of our outcomes in any feature analysis. | ||
* Start the discussion for the architecture document. | ||
* One document for all the features. | ||
* Different documents for each feature. | ||
* Define Safety Goals for the "kernel address space integrity" | ||
* Enumerate Kernel safety claims for this specific case | ||
* Which assumed Kernel safety requirements or AoUs can be defined to | ||
meet System Safety claims? | ||
|
||
## Meeting minute | ||
|
||
## Action items |