[Starlingx-discuss] TSC & Community Call next week - cancel or keep

[Douglas Lopes Pereira]

+1

Douglas Lopes Pereira
Software Development Manager
M: +55 (19) 99212-3212
Campinas, BR
[Encora]<https://www.encora.com/>
[We are proud to be recognized as Leaders in digital engineering services by Zinnov zones]


________________________________
From: Subramanian, Ramaswamy <Ramaswamy.Subramanian at windriver.com>
Sent: Thursday, June 8, 2023 9:58 AM
To: Scott Kamp <scott.kamp at xunison.com>; Waines, Greg <Greg.Waines at windriver.com>; Ildiko Vancsa <ildiko at openinfra.dev>; StarlingX ML <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] TSC & Community Call next week - cancel or keep

You don't often get email from ramaswamy.subramanian at windriver.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe.

+1



From: Scott Kamp <scott.kamp at xunison.com>
Sent: Thursday, June 8, 2023 6:55 AM
To: Waines, Greg <Greg.Waines at windriver.com>; Ildiko Vancsa <ildiko at openinfra.dev>; StarlingX ML <starlingx-discuss at lists.starlingx.io>
Subject: Re: [Starlingx-discuss] TSC & Community Call next week - cancel or keep



CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

+1



Get Outlook for Android<https://urldefense.com/v3/__https:/aka.ms/AAb9ysg__;!!AjveYdw8EvQ!etFLulmObY18nDA4XB12ksi3rEwF-E_xtrJ7vyYL2-IGH7kdOPgxqj45vJYnKTs-_mqk-MZNJX1PSOrzLwZ-l34zHQ8qFmjZ$>

________________________________

From: Waines, Greg <Greg.Waines at windriver.com<mailto:Greg.Waines at windriver.com>>
Sent: Thursday, June 8, 2023 5:44:49 PM
To: Ildiko Vancsa <ildiko at openinfra.dev<mailto:ildiko at openinfra.dev>>; StarlingX ML <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: Re: [Starlingx-discuss] TSC & Community Call next week - cancel or keep



+1

-----Original Message-----
From: Ildiko Vancsa <ildiko at openinfra.dev<mailto:ildiko at openinfra.dev>>
Sent: Thursday, June 8, 2023 12:20 AM
To: StarlingX ML <starlingx-discuss at lists.starlingx.io<mailto:starlingx-discuss at lists.starlingx.io>>
Subject: [Starlingx-discuss] TSC & Community Call next week - cancel or keep

CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi StarlingX Community,

As you know, the annual Open Infrastructure Summit[1] will happen next week (June 13-15), in Vancouver, Canada.

The questions came up during today’s TSC & Community Call, that with the event happening, whether or not we would like to keep that and other meeting for next week?


With a lot of activities and buzz around StarlingX, the conference will have a good number of contributors on site. To avoid conflicting with the conference, my suggestion would be to cancel next week’s TSC and Community Call (June 14), and reconvene the week after and include an overview and updates from the OpenInfra Summit. What do you think?

Thanks and Best Regards,
Ildikó

[1] https://openinfra.dev/summit/vancouver-2023<https://urldefense.com/v3/__https:/openinfra.dev/summit/vancouver-2023__;!!AjveYdw8EvQ!etFLulmObY18nDA4XB12ksi3rEwF-E_xtrJ7vyYL2-IGH7kdOPgxqj45vJYnKTs-_mqk-MZNJX1PSOrzLwZ-l34zHSU7ecPi$>

———

Ildikó Váncsa
Director of Community
Open Infrastructure Foundation






_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io<mailto:Starlingx-discuss at lists.starlingx.io>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20230609/9ce2a54f/attachment-0001.htm>