<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
+1</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
--<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<span class="ContentPasted0">Thales Elero Cervi </span><br>
</div>
<div id="appendonsend"><br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size: 11pt; color: rgb(0, 0, 0);" face="Calibri, sans-serif"><b>From:</b> Ildiko Vancsa <ildiko@openinfra.dev><br>
<b>Sent:</b> Thursday, July 27, 2023 6:20 AM<br>
<b>To:</b> StarlingX ML <starlingx-discuss@lists.starlingx.io><br>
<b>Subject:</b> [Starlingx-discuss] StarlingX Matrix next steps and room structure</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">CAUTION: This email comes from a non Wind River email account!<br>
Do not click links or open attachments unless you recognize the sender and know the content is safe.<br>
<br>
Hi StarlingX Community,<br>
<br>
I’m reaching out with updates about using Matrix as a community chat tool onwards.<br>
<br>
With support from the StarlingX TSC and contributors, and no objections raised, the community decided to move over to Matrix from IRC!<br>
<br>
Next steps:<br>
<br>
- Once the community agrees on a room structure, I will go ahead to create that on the Matrix instance that the OpenDev community is maintaining<br>
- As the #starlingX IRC channel is available through a bridge on Matrix, the channel will still be available to provide a grace period<br>
- I will update the references to the chat platform on the website and other community resources<br>
<br>
<br>
Proposed room structure:<br>
<br>
- General discussions: starlingx-general<br>
- Project team channels:<br>
* starlingx-build<br>
* starlingx-containers<br>
* starlingx-distcloud<br>
* starlingx-distro<br>
* starlingx-docs<br>
* starlingx-flock<br>
* starlingx-networking<br>
* starlingx-openstack<br>
* starlingx-release<br>
* starlingx-security<br>
* starlingx-test<br>
<br>
Does the above room setup work for the community?<br>
<br>
__Please share your questions and concerns by end of day on next Tuesday (August 1).__<br>
<br>
Thanks and Best Regards,<br>
Ildikó<br>
<br>
———<br>
<br>
Ildikó Váncsa<br>
Director of Community<br>
Open Infrastructure Foundation<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Starlingx-discuss mailing list<br>
Starlingx-discuss@lists.starlingx.io<br>
</div>
</span></font></div>
</body>
</html>