About kontributions <!channel>... It is easy to kontribute as QA, to always report bugs, to testing things after, to try out more areas of the language and runtime, and to add third party libraries. It is harder to kontribute to stdlib because that has to have some control and consistency and filter out idiosyncratic views of individual programmers going for something that is used by 80% of Kotlin programmers in 80% of their code (as @orangy says). Compiler and core harder because there is obviously discussions at that level that we can't see, know about, and would be easy to step in the wrong direction or collide with someone, and is much deeper water to get into. Tools like dokka, Gradle and maven plugins, easier because they have less traffic and you can tell when they are dormant and can need help. So that's my view on easy, vs no idea if possible to help. What does the core Kotlin team actually want help with from outside. What areas do they want more community kontributions from, and will they start talking here instead of in private so we can be part of the conversation if we decide to go in deeper?