Contributing to an open-source project is easy:
- Have a look at our issue tracker to select an issue you’d like to fix.
- Fork our github repository.
- Fix your issue.
- Submit a pull-request.
BTW, we have already accepted the first pull-request from an external kontributor: https://github.com/JetBrains/kotlin/pull/1. Thank you, Sergey! When in SPb, drop by our office to collect a T-Shirt.
I would also like to mention James Strachan and Evegny Goldin, who are already Komitters, but not enrolled with JetBrains. Guys are contributing to standard library/KotlinDoc and build tools respectively.
Not really into fixing bugs? Lots of opportunities for you, too!
There are many ways to help Kotlin get better. Here are some examples:
- Mark Derricutt (@talios) recorded a screencast demoing Kotlin IDE.
- Want to do a conference talk on Kotlin? Present the language to your schoolmates or co-workers? Please contact us, we will help you!
- Ken Sipe, Yuri Trukhin and Sergey Lukjanov already presented on Kotlin at different venues.
- Several people contributed external tools making Kotlin support scripting:
- There’s a great idea of implementing Project Euler’s problems in Kotlin
- Some other projects to check out:
If small contributions don’t entertain you that much, you can always go big. There are very important things we cannot handle all at once.
One thing is Eclipse support. We will start a project for Kotlin’s Eclipse plugin pretty soon, and you are very welcome to join and share your experience and passion about it.
We understand the importance of these things, and are willing to help you. See this Akka issue for example.
I’d like to thank each and every kontributor for their help, and I’m very glad seing more of them coming!