Just my two cents, but I wanna reiterate what @wwalkingg has mentioned but from a different perspective: contributing to Jetpack Compose/Compose Multiplatform.
Due to the split, it's quite confusing to know where to even contribute a particular fix/feature. While JetBrains' CMP is on GitHub and landing changes is (maybe) as easy as opening a PR, Google's AndroidX has a totally different process. They do support contributions through GitHub, but only for a subset of AndroidX libraries, including Compose Compiler/Runtime, but not UI.
This makes trying to make even a simple fix quite confusing, and instead many (including myself) will just open an issue... wait, where do I open the issue? Google Issue Tracker? Many things end up being ignored for months there. The same issue is on YouTrack, but to a lesser extent. It kinda makes sense, Google/JB employees have limited time and resources and can't tackle every single little thing, and that's why making external contributions easier is gonna be pretty great, and may reduce the overload they face (depends, code review is not easy either :p)