Re: [sdv-wg] [Tech Alignment] Crickets and next Tuesday

["Krippner Daniel (SDV/EAR ETAS-VCS/ETH)" <daniel.krippner@xxxxxxxxxxxx>]

 

               Hi Peter,

 

I just mailed you an invite from Slack – let me know if that works for you,

               Daniel

 

 

 

Mit freundlichen Grüßen / Best regards

Daniel Krippner

Connected Mobility Solutions, SDV/EAR ETAS-VCS/ETH
Robert Bosch GmbH | Hoferstr. 30 | 71636 Ludwigsburg | GERMANY | www.bosch.com
Mobil +49 172 833 1416 | daniel.krippner@xxxxxxxxxxxx

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Prof. Dr. Stefan Asenkerschbaumer; Geschäftsführung: Dr. Stefan Hartung,
Dr. Christian Fischer, Filiz Albrecht, Dr. Markus Forschner, Dr. Markus Heyn, Rolf Najork
​

From: sdv-wg <sdv-wg-bounces@xxxxxxxxxxx> On Behalf Of Kersting, Peter (TA-13)
Sent: Friday, 30 September 2022 09:27
To: Software Defined Vehicle Working Group <sdv-wg@xxxxxxxxxxx>
Subject: Re: [sdv-wg] [Tech Alignment] Crickets and next Tuesday

 

Hi Daniel,

 

I also have issues with the registration as the confirmation code for the slack invitation expires around the time when I finally receive the email containing it.

 

Peter

 

 

INTERNAL

Von: sdv-wg <sdv-wg-bounces@xxxxxxxxxxx> Im Auftrag von Hudalla Kai (IOB/PAD-PM)
Gesendet: Donnerstag, 29. September 2022 17:41
An: sdv-wg@xxxxxxxxxxx
Betreff: Re: [sdv-wg] [Tech Alignment] Crickets and next Tuesday

 

Hi Daniel,

 

I have no access to the Slack channel and can not register without an invitation from the workspace administrator 😞 Can you help with that?

Kai

---

From: sdv-wg <sdv-wg-bounces@xxxxxxxxxxx> on behalf of Krippner Daniel (SDV/EAR ETAS-VCS/ETH) <daniel.krippner@xxxxxxxxxxxx>
Sent: Tuesday, September 27, 2022 3:35:40 PM
To: sdv-wg@xxxxxxxxxxx
Subject: [sdv-wg] [Tech Alignment] Crickets and next Tuesday

 

 

               Hello Gentlefolk,

 

I still feel quite alone in the SDV Slack channel for our tech alignment activity – I do think that we need to find some way to get people to actually rough-align/write-down/iterate on the topic areas we identified to be relevant, beyond having our bigger slot every other week.

 

I would not mind throwing some starter content into the round – however, I really want this to be a joint effort with joint responsibility for results and artifacts that might be generated. So please revisit our talking points from the last session (that I was participating in – I have not yet seen if/what you guys did last week), and consider whether you might be joining one or the other subgroup.

 

So for the session next week Tuesday, I propose the following talking points:

• “call for action” – who is willing to enter the topical discussions we want to have?
• Review of the first 2-3 “information sharing sessions” we might have (projects/topics that are willing to introduce themselves in our round), and maybe voting of preference/priority
• Continuing our discussion on “what makes an SDV ecosystem”, and “what initial alignment points do we want to lay down”?

 

 

Topic funnel for information sharing sessions:

• The openfasttrace project – how requirements engineering could be done in an open source codebase [topic area “automotive-grade code base”]
• Info on Open Telemetry and example solutions on top by tracetest.io [topic area “monitoring/observability”]
• Introduction to Eclipse Oniro [topic area “ecosystem landscape”]
• Info session on SSI [general technology learning]

 

Looking forward to hearing you next week,

               Daniel