I found a boat load of messages that were posted t...
# meta
n
I found a boat load of messages that were posted to #kotlin-native which are related to Compose, but not Kotlin Native (here is an example: https://kotlinlang.slack.com/archives/C3SGXARS6/p1670750089070259 ). Some Compose channels exist but there isn't one that covers general Compose stuff. Confusingly #compose covers JetPack Compose instead of general Compose stuff. Other Compose channels exist like #compose-desktop for example. It appears as though no standard naming is applied to the various Compose channels that exist in the Kotlin Slack.
As a suggestion the Compose channels should follow the following naming scheme: compose-area Example: compose-general It is recommended that the Kotlin Slack have the following Compose channels: • compose-general • compose-android • compose-ios • compose-desktop • compose-web Also the #compose channel should be renamed to compose-android to avoid unnecessary confusion, and the repeat of the episode that occurred on the #kotlin-native channel. No Compose messages should be posted to the #kotlin-native channel since that detracts from the related messages (makes it more difficult for Kotliners to obtain assistance), and creates unnecessary noise.
a
Hi! Here is similar conversation https://kotlinlang.slack.com/archives/C0B8W32VA/p1666693082218589 We will create #compose-multiplatform channel
1
👍 1
i
#compose can be used for all Compose questions, general or platform specific.
🆗 1
n
With that being the case the description will need to be updated for #compose to reflect it.