Alex Styl
11/12/2022, 10:37 AMAbdelilah El Aissaoui
11/12/2022, 1:14 PMAlex Styl
11/12/2022, 1:39 PMIgor Demin
11/12/2022, 4:36 PMandroidx
repo, where is Jetpack Compose is developed. We usually develop only platform targets there, and make bugfixes in common code. After sometime we upstream some changes to AOSP (to the original androidx repo). That leads to these requirements:
• Contributor have to sign Google CLA
• Contributor should agree that the author field of the commit can be lost (we can merge commits before upstreaming). We'll try to keep though, if possible.
See example of the PR and what we usually ask.
We have a document how to setup Compose repo, but we still doesn't have a document how to contribute. We plan to do that somewhen in the future.
Bugfixes are always welcome, and we will try to review them as we find time. If you plan to contribute a feature, ask us before starting to make changes, especially if the change will be big (create an issue on GitHub, or here, in #compose-desktop)Igor Demin
11/12/2022, 4:38 PMhttps://android.googlesource.com/platform/frameworks/support/+/refs/heads/androidx-main/CONTRIBUTING.mdThis guideline will be useful, if the fix is in common code (that is also used in Jetpack Compose for Android). In that case, make a fix in the original
androidx
repo, following this guide. Google usually review them, not JetBrains.dvdandroid
11/13/2022, 10:44 AMkotlin.compiler.execution.strategy=in-process
• placing println randomly (i had to use something more appropiate, i know)
• attaching compose runtime sources jar in idea won't work
• the only thing it (kinda) worked were error() calls
i've cloned jb-compose, submodules and i've ran publishToMavenLocal scripts like in readme. any tips?