Re: [ELISA Development Process WG] Proposed new WG
Oh my, this is really "fun". But let's converge on a decision.
So we are down to 3 choices here:
I'll give participants a few more hours to express their favorite, although please keep in mind – this is only up to the ELISA workshop, after which we may agree on a new name.
My personal favorite is still #2, further details can (and should) be defined by the mission statement. But feel free to speak up, pro or con any option.
From: Philipp Ahmann <philipp.elisa.project@...>
Sent: Wednesday, September 29, 2021 9:56 PM
To: Elana Copperman <Elana.Copperman@...>; development-process@...; devel@...
Subject: Re: [ELISA Technical Community] [ELISA Development Process WG] Proposed new WG
Wow, this turns out to be a fun part. Eveybody can say something about the topic, even without full understanding and still can be right and the winner.
TLDR: "Kernel elements"
Something just came through my mind. We are in ELISA project, which means Enabling Linux in Safety Applications.
So by the project definition we cover Linux and safety application. Our work should focus on this and does not require to have it in a working group name.
Making an example we are not an "Automotive Linux for safety application WG", but the "Automotive WG".
If we take the last proposal "Linux-based components/elements for safety-critical systems" it turns into "components/elements" working group.
Next step will be that people from safety say: "Wait, we do not have an element from the ISO26262 perspective" and the group is called "components WG"
But reading through the mentioned proposal from todays TSC discussion, the WG for now concentrates on Kernel. (I read it in almost every bullet point of the proposal). So Kernel may need to be in the name.
The beauty of adding "Kernel" is to be able to add "elements" again, because therse are "Kernel elements" suddenly, which does not limit it to safety elements and may be wide enough to take subsystems, driver, config, modules or whatever elements you define to be part of the Kernel. And I am pretty sure, the group will touch all of them. Once the group reaches upper application layers or middleware, we will anyway form another working group as the scope becomes too large.
This brings it to "Kernel elements" or as an alternative "staple". And closing the loop to ELISA you can call it the Linux "kernel elements" working group for safty applications.
I hope this makes sense or directs to another even fancier proposal. Just be creative.
Am Mi., 29. Sept. 2021 um 18:32 Uhr schrieb <elana.copperman@...>: