News

Contributing to Kotlin (Kontributing)

As you all know, Kotlin went Open Source two weeks ago. In this post, I give some instructions for prospective contributors and an overview of the contributions we already had.

Kontrbute!

Contributing to an open-source project is easy:

  • Have a look at our issue tracker to select an issue you’d like to fix.
    • We have a special tag for those issues that seem to be easy for newcomers.
    • We also have an assignee in our tracker, named Kontributor, to whom we assign issues that we are hoping to get contributions on.
  • 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:

And remember that your solutions to Web Demo problems are very welcome, as well as new problems. Just twit them.

Bigger things

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.

Another thing, or rather many things, are popular libraries and frameworks. Wouldn’t it be cool to support Play in Kotlin? Or Akka? Or <you name it>?

We understand the importance of these things, and are willing to help you. See this Akka issue for example.

To Conclude

I’d like to thank each and every kontributor for their help, and I’m very glad seing more of them coming!

image description