Closed Peefy closed 1 year ago
@Peefy can you present KCL at a TAG App Delivery meeting before the next sandbox vote on Sept 12?
cc @joshgav
Thank you @nikhita!
@Peefy we've started to discuss KCL in our Slack channel #tag-app-delivery - would love for you to join the conversation. You can get an invite to CNCF Slack at https://slack.cncf.io/.
You could present at the TAG's Aug 2 or Aug 16 general meetings; DM me in Slack to finalize. We'd like to talk with you all about the values KCL offers users, its high-level technical architecture, your near-term roadmap, and the state of your community and governance. We can ask maintainers of Helm, kpt and ytt to attend and help us review too.
Thank you @nikhita!
@Peefy we've started to discuss KCL in our Slack channel #tag-app-delivery - would love for you to join the conversation. You can get an invite to CNCF Slack at https://slack.cncf.io/.
You could present at the TAG's Aug 2 or Aug 16 general meetings; DM me in Slack to finalize. We'd like to talk with you all about the values KCL offers users, its high-level technical architecture, your near-term roadmap, and the state of your community and governance. We can ask maintainers of Helm, kpt and ytt to attend and help us review too.
@Peefy can you present KCL at a TAG App Delivery meeting before the next sandbox vote on Sept 12?
cc @joshgav
Thank you @nikhita! I will present at the TAG's Aug 16 general meetings and I've joined the slack channel.
Thank you @nikhita!
@Peefy we've started to discuss KCL in our Slack channel #tag-app-delivery - would love for you to join the conversation. You can get an invite to CNCF Slack at https://slack.cncf.io/.
You could present at the TAG's Aug 2 or Aug 16 general meetings; DM me in Slack to finalize. We'd like to talk with you all about the values KCL offers users, its high-level technical architecture, your near-term roadmap, and the state of your community and governance. We can ask maintainers of Helm, kpt and ytt to attend and help us review too.
Thank you @joshgav and your interest in the KCL project! I will present at the TAG's Aug 16 general meetings and I've joined the slack channel. π
Thank you for the presentation @Peefy! Notes and recordings are linked from this issue comment: https://github.com/cncf/tag-app-delivery/issues/430#issuecomment-1693627540
My conclusion is that KCL would be a good fit for CNCF sandbox.
Thank you for the review! I have browsed the notes and recordings linked in the question comment and they have no issues. Thank you to CNCF sandbox for recognizing the KCL project.
After a quick look at the docs, it looks like a great fit. I'm going to review the video as well, but I vaguer it won't change my mind.
/vote-sandbox
@amye has called for a vote on [Sandbox] KCL
(#48).
The members of the following teams have binding votes: | Team |
---|---|
@cncf/cncf-toc |
Non-binding votes are also appreciated as a sign of support!
You can cast your vote by reacting to this
comment. The following reactions are supported:
In favor | Against | Abstain |
---|---|---|
π | π | π |
Please note that voting for multiple options is not allowed and those votes won't be counted.
The vote will be open for 7days
. It will pass if at least 66%
of the users with binding votes vote In favor π
. Once it's closed, results will be published here as a new comment.
/check-vote
So far 54.55%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
6 | 0 | 0 | 5 |
User | Vote | Timestamp |
---|---|---|
rochaporto | In favor | 2023-09-13 6:40:47.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-09-12 16:01:11.0 +00:00:00 |
justincormack | In favor | 2023-09-13 16:04:38.0 +00:00:00 |
mauilion | In favor | 2023-09-13 20:25:15.0 +00:00:00 |
RichiH | In favor | 2023-09-12 23:39:46.0 +00:00:00 |
kgamanji | In favor | 2023-09-12 16:40:32.0 +00:00:00 |
@mattfarina | Pending | |
@dzolotusky | Pending | |
@cathyhongzhang | Pending | |
@nikhita | Pending | |
@erinaboyd | Pending |
/check-vote
So far 63.64%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
7 | 0 | 0 | 4 |
User | Vote | Timestamp |
---|---|---|
justincormack | In favor | 2023-09-13 16:04:38.0 +00:00:00 |
RichiH | In favor | 2023-09-12 23:39:46.0 +00:00:00 |
rochaporto | In favor | 2023-09-13 6:40:47.0 +00:00:00 |
mauilion | In favor | 2023-09-13 20:25:15.0 +00:00:00 |
TheFoxAtWork | In favor | 2023-09-12 16:01:11.0 +00:00:00 |
nikhita | In favor | 2023-09-14 7:55:26.0 +00:00:00 |
kgamanji | In favor | 2023-09-12 16:40:32.0 +00:00:00 |
@mattfarina | Pending | |
@dzolotusky | Pending | |
@cathyhongzhang | Pending | |
@erinaboyd | Pending |
/check-vote
So far 72.73%
of the users with binding vote are in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
8 | 0 | 0 | 3 |
User | Vote | Timestamp |
---|---|---|
TheFoxAtWork | In favor | 2023-09-12 16:01:11.0 +00:00:00 |
dzolotusky | In favor | 2023-09-15 13:47:29.0 +00:00:00 |
rochaporto | In favor | 2023-09-13 6:40:47.0 +00:00:00 |
kgamanji | In favor | 2023-09-12 16:40:32.0 +00:00:00 |
justincormack | In favor | 2023-09-13 16:04:38.0 +00:00:00 |
mauilion | In favor | 2023-09-13 20:25:15.0 +00:00:00 |
RichiH | In favor | 2023-09-12 23:39:46.0 +00:00:00 |
nikhita | In favor | 2023-09-14 7:55:26.0 +00:00:00 |
@mattfarina | Pending | |
@cathyhongzhang | Pending | |
@erinaboyd | Pending |
The vote passed! π
72.73%
of the users with binding vote were in favor (passing threshold: 66%
).
In favor | Against | Abstain | Not voted |
---|---|---|---|
8 | 0 | 0 | 3 |
User | Vote | Timestamp |
---|---|---|
@RichiH | In favor | 2023-09-12 23:39:46.0 +00:00:00 |
@rochaporto | In favor | 2023-09-13 6:40:47.0 +00:00:00 |
@kgamanji | In favor | 2023-09-12 16:40:32.0 +00:00:00 |
@nikhita | In favor | 2023-09-14 7:55:26.0 +00:00:00 |
@dzolotusky | In favor | 2023-09-15 13:47:29.0 +00:00:00 |
@TheFoxAtWork | In favor | 2023-09-12 16:01:11.0 +00:00:00 |
@justincormack | In favor | 2023-09-13 16:04:38.0 +00:00:00 |
@mauilion | In favor | 2023-09-13 20:25:15.0 +00:00:00 |
Hi @Peefy ! Welcome aboard! We're very excited to get you onboarded as a CNCF sandbox project! Here's the link to your onboarding checklist: https://github.com/cncf/sandbox/issues/149
Here you can communicate any questions or concerns you might have. Please don't hesitate to reach out, I am always happy to help!
Thank you @Cmierly ! I'll review the checklist.
Application contact emails
xiaodong.dxd@antgroup.com xpf6677@gmail.com shushan.css@antgroup.com huangch96@gmail.com zongzhe1024@163.com 897013703@qq.com
Project Summary
Constraint-based record and functional language and tools that is primarily utilized in cloud-native configurations and policy scenarios.
Project Description
With cloud-native language and tools, KCL aims to address the cognitive burden of large-scale cloud-native static configuration, YAML/template bloat, and customization/validation of third-party applications through the following features:
Org repo URL (provide if all repos under the org are in scope of the application)
https://github.com/kcl-lang
Project repo URL in scope of application
https://github.com/kcl-lang/kcl
Additional repos in scope of the application
https://github.com/kcl-lang/kcl-go https://github.com/kcl-lang/vscode-kcl https://github.com/kcl-lang/kpm https://github.com/kcl-lang/krm-kcl https://github.com/kcl-lang/kubectl-kcl https://github.com/kcl-lang/helm-kcl https://github.com/kcl-lang/kustomize-kcl https://github.com/kcl-lang/kpt-kcl https://github.com/kcl-lang/kcl-operator
Website URL
https://kcl-lang.io/
Roadmap
https://kcl-lang.io/docs/community/release-policy/roadmap
Roadmap context
N/A
Contributing Guide
https://kcl-lang.io/docs/community/contribute/
Code of Conduct (CoC)
https://github.com/kcl-lang/kcl/blob/main/CODE_OF_CONDUCT.md
Adopters
https://github.com/kcl-lang/kcl/blob/main/ADOPTERS.md
Contributing or Sponsoring Org
N/A
Maintainers file
https://github.com/kcl-lang/kcl/blob/main/MAINTAINERS
IP Policy
Trademark and accounts
Why CNCF?
KCL has reached the production readiness stage and has been recognized by some adopters. We strongly believe that KCL is a missing piece of CNCF in the fields of automation and configuration. By joining CNCF, we aim to increase the project's visibility and promote community adoption and participation, as a strong and well-known organization is essential for driving a language ecosystem. We hope that the CNCF community can provide valuable ideas and contributions to help achieve this goal. Additionally, we look forward to receiving guidance from CNCF in building KCL communities.
We believe that incorporating KCL into the CNCF ecosystem will significantly enhance the project's visibility. Under the guidance of CNCF, we can follow their procedures and standards, set achievable goals to improve our language and tools, promote community participation, and integrate KCL with other cloud-native projects.
Benefit to the Landscape
Firstly, KCL adheres to the Kubernetes Resource Model (KRM) specification, making it an ideal fit for Kubernetes integration. Additionally. Secondly, KCL aims to support a wide range of cloud-native configuration tools. By leveraging the dynamic characteristics of the language, it can non-invasively address the limitations of existing CNCF configuration management tools, potentially simplifying the use of multiple tools in the CNCF landscape.
Cloud Native 'Fit'
KCL was originally designed to tackle the challenges of static configuration and automation in cloud-native configurations, it was built using cloud-native technologies and fits within the CNCF "Automation & Configuration" area.
Cloud Native 'Integration'
KCL integrates with most configuration management tools in the cloud native area, and it also supports abstraction, mutation, and validation of configurations at both the client and Kubernetes runtime.
Cloud Native Overlap
KCL is a programming language with full toolchain implementation that features a distinctive implementation technique and user interface in the cloud-native landscape. Despite its unique qualities, there are also similar projects, such as ytt and tanka, that seek to address the same challenges.
Similar projects
ytt: ytt utilizes a combination of static configuration and dynamic programming language to achieve dynamic expansion of configuration. KCL can accomplish similar functions. Furthermore, KCL offers additional schema, constraint definitions and abstraction capabilities, further simplifying the user configuration interface. Tanka: Tanka is the robust configuration utility for Kubernetes cluster, powered by the jsonnet language. Compared to Tanka and Jsonnet, KCL has done more work in schema definition, static type checking, and constraints to shift configuration risks to the left, rather than bringing errors to the language runtime.
Landscape
Yes
Business Product or Service to Project separation
N/A
Project presentations
https://kcl-lang.io/blog/2022-declarative-config-overview https://medium.com/@xpf6677/gitops-with-kcl-programming-language-cb910230e310 https://medium.com/dev-genius/manage-kubernetes-configurations-with-kcl-oci-artifacts-39d311d366e1
Project champions
N/A
Additional information
Project Introduction Slides