Read and comment on upcoming Kotlin language features before they ship
Track the status of a specific language proposal from idea to stable
Understand the rationale behind an existing Kotlin language design decision
Submit feedback on proposals still in public discussion phase
| kotlin/keep | docker/docs | ethereum/ethereum-org-website | |
|---|---|---|---|
| Stars | 3,711 | 4,570 | 5,926 |
| Language | Markdown | Markdown | Markdown |
| Setup difficulty | easy | easy | moderate |
| Complexity | 2/5 | 1/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
KEEP stands for Kotlin Evolution and Enhancement Process. This repository is where the team behind the Kotlin programming language publicly documents proposals for changes to the language and its standard library. Kotlin is a programming language developed by JetBrains, widely used for Android app development and server-side software. Each proposal is called a KEEP and receives a sequential number. The documents are written in Markdown and stored in this repository. They cover both planned changes that are still being designed and changes that have already been built into the language. The actual code implementing a proposal lives in a separate Kotlin source code repository, this one only holds the design documents and discussion records. The process has three stages. First, a proposal is published here and assigned a KEEP number. Second, a public discussion opens on GitHub Discussions, where community members can read the proposal and share feedback. Third, the proposal is either accepted, rejected, or sent back for more work. Each document header tracks the current status, using labels like Public Discussion, In Progress, Experimental, Stable, or Declined. Beyond full proposals, the repository also contains a notes directory for early-stage ideas that are not yet ready to be formal proposals. These are directions the team is considering but needs more community input on before shaping into a complete design. If you want to suggest a new language feature, the repository directs you to file a ticket in Kotlin's public issue tracker and describe your real-world use case rather than submitting a pull request. For existing proposals still under discussion, feedback goes into the corresponding GitHub Discussion thread.
The official repository where the Kotlin team publishes design proposals for new language features and standard library changes, with public community discussion before acceptance or rejection.
Mainly Markdown. The stack also includes Markdown.
Not specified in the explanation.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.