Rename the project

[bamboo]

Hi everybody,

As you know, naming things is one of the hardest problems of our field. So when we started this project a few months ago, with all of its challenges still ahead of us, we thought it would be wiser to focus our energy on delivering value first and, instead, settle for the mnemonic name of Gradle Script Kotlin, i.e. support for writing Gradle build scripts in Kotlin.

The name served us well so far, but there's no denying it's a mouthful. As we get closer to our big 1.0 release, we would like to ask for your help in finding a suitable, good, simple—and maybe even beautiful—name for the project. Together we can crack this nut!

Please suggest a name by posting a comment to this issue. Alternatively, vote on an existing suggestion by adding a thumbs up reaction to its comment.

Thanks in advance for participating!

[berkus]

Krokodile

[sdeleuze]

@cbeams I think I would vote for gradle-kotlin.

This is a variation of your gradle-kts proposal. The fact that you are using *.kts files and Kotlin Script is an implementation detail and I don't see a lot of value using it, especially for a project name. The big selling point is that you are using Kotlin as a language.

gradle-kotlin is meaningful, each time I want to refer to "Gradle Script Kotlin" this is the name which comes the first in my mind and this is 100% consistent with the gradle-groovy that you seems to plan later for the Groovy variant.

Keep it simple and meaningful please ;-)

[MrTact]

This is very computer-sciency (or maybe one might argue very Linux-y) but what about gradlek (pronounced "gradle-kay"), in a similar vein to gradlew and also gradle-kotlin (which I like, but is still a bit of a mouthful).

[AlexCzar]

I assumed it will just become stable, docs will be updated and we'll just refer to it as Gradle. Build file having separate extension is enough distinction, in my humble opinion. If we do need the name, my suggestion is

GroK

Which is

1. Short and easy to remember
2. Gradle →←niltoK or Gradle on Kotlin (latter suggested by Madis Pink)
3. Emphasizes intuitiveness and understanding

[sdeleuze]

If Gradle Script Kotlin will be successful (and I expect it to be), I think in the long run people will gradually refer to it just by saying "Gradle" (in a few years) and will use "Gradle Groovy" for the historic variant. So with that in mind, "Gradle Kotlin" would allow a much smoother transition. That's why I am not sure there is a need to create a new product name.

[bamboo]

Hi, everyone!

First of all, thanks for your suggestions, comments and votes. It was really helpful and fun to watch.

After much deliberation we decided to settle on kotlin-dsl. :tada:

In the end we considered the pros listed by @cbeams in his well thought-out comment far outweighted the cons.

The github repository has been renamed to reflect this decision and all mentions to Gradle Script Kotlin have been replaced by Gradle Kotlin DSL (except in past release notes). Please let us know if you find any discrepancies.

If you have a local clone, please update it with the new origin:

git remote set-url origin git@github.com:gradle/kotlin-dsl.git

The base package has also been renamed from org.gradle.script.lang.kotlin to org.gradle.kotlin.dsl so you'll need to update any imports after upgrading to the upcoming 0.10.0.

We hope you are as satisfied with this move as we are.

Thanks for riding along with us!

[sdeleuze]

This new name makes sense. I tend to think in practice people will end up by refering to the variants as Gradle Groovy as a shortcut for "Gradle with Groovy DSL" and Gradle Kotlin for "Gradle with Kotlin DSL".

[santalu]

too late... kotle was such a good name