current state and future of KCL

[MirKml]

First, thanks for impressive work on such a nice, feature rich configuration language.
But I'm little bit concerned.
Whole 2024 was amazing. New features every month, regularly releases, blog posts.

But in 2025 this pace is gone. 2 bugfix releases in 6 months, no newsletters, blogs, no new features. Commit rate is very low...

What is the future, roadmap for KCL? KCL ecosystem is huge, language, bindings, library, packages.... it can became obsolete very quickly.

[daudcanugerah]

https://cloud-native.slack.com/archives/C05TC96NWN8/p1744642425501609 its from cnfc slack channel

[mi-bauer]

Can you summarize or quote it? Accessing the info doesn't work for me, as I don't have an account for this slack channel.

[johnallen3d]

I figured out how to log in a week or two back. The gist was that a similar question was posed (e.g. is KCL still maintained) and the general response was that internal work responsibilities for @Peefy et al. had picked up quite a bit, reducing the time available to dedicate to KCL.

There's more in the thread but I think this captures the highlight (response from @He1pa).

[Peefy]

Yes, as a part-time maintainer, I still hope that KCL will get better and better. I will try my best to maintain it in my spare time, and I also hope that more capable and willing contributors will join.

[f4z3r]

@Peefy I am currently evaluating whether it would make sense to use KCL to replace Kustomize, CUE, and Go Templating all in one for our infrastructure declaration at work. Should this be the case, I would be very interested in contributing to this project, and potentially even help out as a maintainer if you want. I should be able to get time from work allocated to work on this (around 15-20%). Let me know if you think this would be doable. Of course, it would still be interesting to know how much work others might still be putting into this project, as I would not like to have a central piece of our infra management rely on a product that is barely maintainable 😄

[Peefy]

Welcome! I'm currently involved in the daily maintenance and development, and there are other maintainers also continuously contributing. Of course, as AI develops, maintaining them will likely become easier because the project has a large amount of testing history, facilitating closed-loop AI iteration.