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!

About Andrey Breslav

Andrey is the lead language designer working on Project Kotlin at JetBrains. He also works on making the Java language better, serving as a Java Community Process expert in a group for JSR-335 ("Project Lambda"), and occasionally speak at software conferences such as Devoxx or JavaOne.
This entry was posted in General. Bookmark the permalink.

14 Responses to Contributing to Kotlin (Kontributing)

  1. Otto Christian says:

    This is definitely helpful to know where one can contribute to the Kotlin project, thanks!

    One of the pet peeves I have about open source projects is sometimes it’s hard to know how to contribute, unless you’re already an experienced developer and can dive into some complex code. Making it easy for people to contribute gets more people involved and excited about the project.

  2. Guangyu says:

    Would you tell us some message on the part of ‘module and compile’?
    Since the concept of module is very important( dependency, runtime representation, its relation with OSGi, etc ), and you pointed out that “Modules are being redesigned” in http://confluence.jetbrains.net/display/Kotlin/Modules+and+Compilation.

  3. Could you please add my project into third-party tools list?

    This is SumblimeText 2 Package for Kotlin. It contans Kotlin syntax defenition map (primary based on grammar). Here is project page: https://github.com/vkostyukov/kotlin-sublime-package

  4. Eric Palmer says:

    What is the best way to contribute example code samples for people starting out?
    I’m looking forward to help out!

    Thanks

    Eric

  5. not-important says:

    If Andrey is working on JSR-335 and Kotlin, is this not a conflict of interest? Making the JSR as bad or as late as possible could be e.g. perceived as a benefit for Kotlin?

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">