There's a formal process for sending proposals for the Kotlin language, and it's called KEEP (Kotlin Evolution and Enhancement Process).

During this year we've been making good use of it from the Arrow maintainers team, since we've filed the KEEP-87, where we propose support for compile time validation and dependency resolution. But no fear! we'll not talk about FP here, just about the complete pipeline we went through to get it done. We've learned a lot during the process, and would love to share our experience.

In this talk, you'll learn:
- What's the KEEP and why it's important.
- Why and how to file a new proposal for the language.
- The importance of having initial feedback before tackling the issue. (We got it from people in the Kotlin compiler team).
- How the Kotlin repository is organized and where you should look at to implement your proposal.
- Which pieces of code we needed to modify and how to achieve our goal (error loggers, argument generators ...etc.)
- How to iterate over it once the initial draft is presented by getting in the JetBrains feedback loop.
- Helping to maintain and evolve the language as a community effort.