[Starlingx-discuss] StarlingX Matrix next steps and room structure

[Cervi, Thales Elero]

+1

--
Thales Elero Cervi

________________________________
From: Ildiko Vancsa <ildiko at openinfra.dev>
Sent: Thursday, July 27, 2023 6:20 AM
To: StarlingX ML <starlingx-discuss at lists.starlingx.io>
Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure

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,

I’m reaching out with updates about using Matrix as a community chat tool onwards.

With support from the StarlingX TSC and contributors, and no objections raised, the community decided to move over to Matrix from IRC!

Next steps:

- 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
- As the #starlingX IRC channel is available through a bridge on Matrix, the channel will still be available to provide a grace period
- I will update the references to the chat platform on the website and other community resources


Proposed room structure:

- General discussions: starlingx-general
- Project team channels:
  * starlingx-build
  * starlingx-containers
  * starlingx-distcloud
  * starlingx-distro
  * starlingx-docs
  * starlingx-flock
  * starlingx-networking
  * starlingx-openstack
  * starlingx-release
  * starlingx-security
  * starlingx-test

Does the above room setup work for the community?

__Please share your questions and concerns by end of day on next Tuesday (August 1).__

Thanks and Best Regards,
Ildikó

———

Ildikó Váncsa
Director of Community
Open Infrastructure Foundation






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