Re: Proposed new WG


Adding back others (Philipp has some issue with the mailing list – are you registered in these groups?)


From: Ahmann, Philipp (ADITG/ESS1) <pahmann@...>
Sent: Wednesday, September 29, 2021 6:28 PM
To: jason.smith@...; gpaoloni@...; Elana Copperman <Elana.Copperman@...>
Cc: development-process@...; devel@...; Paul Albertella <paul.albertella@...>
Subject: RE: [ELISA Technical Community] Proposed new WG


I go for 2.5:

Linux features for safety-critical systems

Best regards,



Philipp Ahmann
Manager System Software 1 (ADITG/ESS1)

Data protection information: We use your contact information and e-mail communication to process your inquiry and for internal and possibly tax documentation purposes. Your information will only be passed on to third parties if this is necessary to carry out your request or if we are legally obliged to do so.


From: devel@... <devel@...> On Behalf Of Smith, Jason via
Sent: Mittwoch, 29. September 2021 17:15
To: gpaoloni@...; Elana Copperman <elana.copperman@...>
Cc: development-process@...; devel@...; Paul Albertella <paul.albertella@...>
Subject: Re: [ELISA Technical Community] Proposed new WG


I’d prefer #2.  Simple and to the point.


Jason R. Smith, UL-CFSX
Principal Engineer, Robots & Control Systems (CMIT)

Distinguished Member of Technical Staff

333 Pfingsten Road
Northbrook, IL 60062-2096 US
T: 1.847.664.1352


From: devel@... <devel@...> On Behalf Of Gabriele Paoloni via
Sent: Wednesday, September 29, 2021 10:12 AM
To: Elana Copperman <elana.copperman@...>
Cc: development-process@...; devel@...; Paul Albertella <paul.albertella@...>
Subject: Re: [ELISA Technical Community] Proposed new WG


From my perspective I would go for 5. Right now I don't have other names suggestions






On Wed, Sep 29, 2021 at 4:18 PM <elana.copperman@...> wrote:

Following today's TSC call and discussion, the new WG proposed in  has been tentatively approved.  Thanks to all (especially Lukas and Paul) for your support.

See below, the preliminary list of suggested names:

  1. Linux Developers
  2. Linux features for safety
  3. Linux features amenable for safety
  4. Safety engineering features
  5. Linux-based elements for safety-critical systems
  6. Applying Linux features

Actually I don't really prefer any of these names, so would offer a prize to the winning name, allowing additional suggestions to be raised.


Next steps:

  1. All those subscribed to this mailing list are cordially invited to vote on (or suggest any new) names for the new WG.
  2. Elana will extend a call for collaboration in tomorrow's session at the Linux Security Summit, including a call for participation in the newly formed WG.  I would ask to have a tentative agreement (via email) on the name for the WG by tomorrow if possible, the name can be updated later before meetings actually begin.
  3. Elana will issue a proposal to present the new WG at the upcoming ELISA workshop (proposal deadline is this coming Friday).  The proposal will be high level, and we have agreed to continue this discussion at the next TSC meeting to refine / clarify some of the remaining open points.  However, the basic format and concept as summarized in the WG proposal (see above link) is not expected to be changed in any major way.  For example, we need to agree on how to avoid misunderstanding and provide a clear disclaimer on any safety claims related to the technical suggestions made by the WG.  In addition (as discussed today), all technical features will be clarified within the context of a specific use case, while at the same time understanding the limitations of NDAs and exposure of proprietary details of business applications. 



This e-mail may contain privileged or confidential information. If you are not the intended recipient: (1) you may not disclose, use, distribute, copy or rely upon this message or attachment(s); and (2) please notify the sender by reply e-mail, and then delete this message and its attachment(s). Underwriters Laboratories Inc. and its affiliates disclaim all liability for any errors, omissions, corruption or virus in this message or any attachments.

Join to automatically receive all group messages.