I would like to resurface this post once again bec...

# meta

[andylamax]

I would like to resurface this post once again because I believe it is has consistency and maximizes signal to noise ratio. https://kotlinlang.slack.com/archives/C0B8W32VA/p1645632237168149?thread_ts=1644919143.623599&cid=C0B8W32VA

The idea of having compose specific posts/insights/questions which are unrelated to a platform makes it easy to subscribe/follow the things you are interested in most

In the linked thread, Adam suggests that this is a bad idea for online communities, but I respectfully disagree with the claim, coz as member of this community, I tend to jump and overlook most of compose questions just because most of them are platform specific.

The idea of renaming #compose to #compose-android to maintain its members sounds good. And the follow up of creating another channel (be it #compose or #compose-general or #compose-multiplatform) seems convenient. It also sits nicely with the already existing #compose-desktop, #compose-ios, #compose-web and #compose-wear channels. Thoughts??

[louiscad]

That's #meta, and #naming 😄

[andylamax]

@Alina Dolgikh [JB]???

[Alina Dolgikh [JB]]

Hi! Sorry, I missed this one.

Could you please share the examples of questions that can go to #compose /#compose-general?

[andylamax]

E.g 1. Questions regarding general/universal tooling
How do I share resources (something like images, fonts and GIF) between compose-android and compose-web?

E.g 2. Questions regarding compose-runtime only
How can one integrate a TerminalApplier (with something ncurses) to emit ui on the terminal for native targets?? Something like mosaic but for kotlin/native

E.g 3. Questions regarding authoring universal library that be used for both compose-android, compose-desktop and/or compose-web (both DOM and Canvas)

[andylamax]

The list can go on and on and on

[gildor]

I think it would be very hard for people to navigate to channels like #compose-general or #compose-runtime, I think it’s fine to have #compose as general channel even if it has a lot of android specific questions, after all most of things appear first only on Android and it has a lot more features

[Alina Dolgikh [JB]]

Hi! I agree with Andrey. I think people usually mean Jetpack Compose when they say Compose, hence Android related topics.
@andylamax, but I see your point with the example topics. IMO they’d rather fit for #compose-multiplatform channel. It is also an official name of the technology developed by the team at JetBrains. E.g., see the latest release post.
Though, given the #naming is hard, I’d also happy to hear the opinion of @Sebastian Aigner 🙂

[Alina Dolgikh [JB]]

(and sorry for delayed replies. For some reason, I don’t receive notifications from this thread, even though they’re not switched off)

[louiscad]

Do you have this turned on? Maybe you were in Do not disturb mode, or off "working hours" configured in Slack? Slack doesn't send missed notifications in the morning.

[andylamax]

#compose-multiplatform works perfect for this usecase by the way

[Alina Dolgikh [JB]]

I can create a channel. I assume communication and other effort might be needed to redirect people to the new channel. Could you handle it @andylamax?

[andylamax]

Sure I can handle that.

Also a post to #announcements would help introduce this

[Sebastian Aigner]

My main concern is not doing a bait-and-switch, I.e. introducing a channel with the same name as one we previously used (so no turning an existing channel into “just” #compose for the time being. Other than that, if it reflects the actual (vs intended) use of the channels, I don’t have objections to have their naming reflect that.

[Alina Dolgikh [JB]]

Not sure I get your point @Sebastian Aigner. I don’t think we ever had #compose-multiplatform channel

[Sebastian Aigner]

My point is to not name any new channel “compose” without a modifier afterwards.

[Sebastian Aigner]

Because that name was prev taken

[gildor]

I believe the proposal is to keep the compose channel as it is and create a new one, compose-multiplatform

[Alina Dolgikh [JB]]

Hi @Igor Demin could you please review the suggestion. Are you fine with the new channel creation?

[Igor Demin]

So, the structure will be:

#compose - general Compose channel, all discussions regarding Compose are welcome, no matter if it is Jetpack Compose or Compose Multiplatform, platform-specific or platform-independent

#compose-multiplatform - the main scope is discussing developing for multiple platforms, and their differences

#compose-<platform> channels - the main scope - developing for the specific platform

In all channels we also can discuss platform-independent Compose (it includes Compose Runtime, Compose Foundation, Compose Material), but better to discuss that in #compose.

I guess, we lack compose-android then, but it seems Google fine with that and wants to discuss Android questions in #compose?

If I have described it right, and everyone here okay with that, I will discuss that with my team (Compose Multiplatform) and Jetpack Compose team. Personally, I am not against it, and probably for it.

The alternative to the structure I described above is to separate channels by products:

#compose (aka Jetpack) - discussions regarding Jetpack Compose product (setup in Android project, any available Compose API for Android platform)

#compose-multiplatform - discussions regarding the Compose Multiplatform product (Gradle plugin, desktop, web, iOS, developing for multiple platforms, any available Compose API for these platforms)

But probably it is not convenient for community.

[andylamax]

I think the 1st structure is best for the community, I stand to be corrected

[Alina Dolgikh [JB]]

Hi! Thank you @Igor Demin. The first structure sounds good. What was the feedback from the team? Can I create the compose-multiplatform channel?

[Igor Demin]

I still need to discuss that with a couple of people. I think we'll know this week if everyone is one board with that.

[Alina Dolgikh [JB]]

Hi @Igor Demin! Any update on this?

[Igor Demin]

Let's create this channel, there are no objections.

In the description I would write something like this:

Developing on Compose for multiple platforms

[Alina Dolgikh [JB]]

Hi! I’ve created #compose-mp and invited @andylamax and @Igor Demin

[Alina Dolgikh [JB]]

#compose-multiplatform is taken and we couldn’t find by whom

[Igor Demin]

#compose-mp

set the channel topic: Compose Multiplatform

Can we keep the first description? The second description tells that conversations in this channel is about the Compose Multiplatform as a product, but we discussed here that the focus should be not in a product, but about a subset of an area. Compose muliplatform as a product is definitely provides abilities to develop for multiple platforms, but Jetpack Compose also provides ability to develop for WearOS (watches) and ChromeOS (desktop).

[Igor Demin]

#compose-multiplatform is taken and we couldn’t find by whom

Maybe compose-crossplatform then? It also describes the purpose of the channel better.

[Alina Dolgikh [JB]]

@Igor Demin I’ve set the topic same as the description. Does that look good?
I’m afraid using different names for the same thing (multiplatform – cross platform) will be confusing

[Igor Demin]

I’ve set the topic same as the description

Wow, that is new. I thought what we see near the channel name is the description 😄. Probably only few users see the real description.

Looks good to me.

(multiplatform – cross platform) will be confusing

Ok

[andylamax]

So whats next? Do we post the new channel (and it's purpose) on #announcements ?

[Alina Dolgikh [JB]]

Yeah, I can prepare a post for announcement

[Igor Demin]

We should properly describe the difference between #compose. To do that, we need to change the description and the topic of the #compose channel. I suppose, we decided to keep it as the place for all Compose discussions?

I would suggest:

Before:

Description: Discussions around Jetpack Compose
Topic: :jetpack-compose: Project page: <https://developer.android.com/jetpack/compose>, Issue tracker: <https://issuetracker.google.com/issues?q=componentid:612128>
Pinned: Project page, Issue tracker, Releases, Use Compose With Kotli...

After:

Description: Discussions around all things related to Compose
Topic: :jetpack-compose: Jetpack Compose: <https://developer.android.com/jetpack/compose>, Compose Multiplatform: <https://www.jetbrains.com/lp/compose-mpp>
Pinned: Issues (Jetpack), Releases (Jetpack), Use Compose With Kotli...

If it is okay, I will discuss it with relevant peoples. The change of the description is probably okay, but the change of the topic can be controversial.

[Alina Dolgikh [JB]]

Hi @Igor Demin! Thank you. Sounds good to me. I believe you can update the description on your own, once they’re confirmed