23 views
   owned this note
# CNCF k0sproject community calls This is a document used to collect k0sproject community meeting minutes. The schedule for various community calls is at [k0sproject's meeting calendar]. Remember that k0sproject and its open meetings are always subject to [k0sproject's code of conduct]. [k0sproject's code of conduct]: https://github.com/k0sproject/community/blob/main/CODE_OF_CONDUCT.md [k0sproject's meeting calendar]: https://zoom-lfx.platform.linuxfoundation.org/meetings/k0s ## Template Use this template (copy-paste) for each call. --- ## Day Month Year - which call happened ### Attendees ### Agenda - Intro new joiners #### Open Discussion --- ## 22 September 2026 - Community Office Hours - Eastern ### Attendees - Jussi Nummelin - Natanael Copa - Maciej Szulik - Tom Wieczorek - Samuel Schumacher ### Agenda - ARMv7 32-bit problems with Github Runners. - [PR template and contributing guidelines](https://github.com/k0sproject/k0s/pull/8310) discussion. - Weekend release to address [GHSA-qjgc-wmg7-3jc3](https://github.com/k0sproject/k0s/security/advisories/GHSA-qjgc-wmg7-3jc3). - [1.37 milestone](https://github.com/k0sproject/k0s/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.37). #### Open Discussion --- ## 15 September 2026 - Maintainers call ### Attendees - Jussi Nummelin - Natanael Copa - Jonathan Phan - Serhii Ivanov - Adrian Pedriza - Maciej Szulik - Tom Wieczorek ### Agenda - AI policy [proposal](https://github.com/k0sproject/community/pull/7) - We agreed that we don't need an AI disclosure information. - We will review the k0s pull request template. - [Code guidelines](https://github.com/k0sproject/k0s/pull/8196) - Agreed. Merged. - [Contributor ladder](https://github.com/k0sproject/community/pull/6) - Tagging folks in the pull request as well as in the #k0s-dev Slack channel to get some feedback on this. #### Open Discussion --- ## 8 September 2026 - Comunity hours ### Host ### Attendees: - Jussi Nummelin (maintainer) - Evans Mungai - Aleksey Makhov - Lawrence Keener #### Welcome & Housekeeping - Code of Conduct - Intro new joiners ### Agenda to be discussed - What the core maintainers are working on? - patch release got recently out - 1.37 in core maintainers radar; some bigger changes and features in the plans for it #### Open Discussion Replicated engineers to start collaborating more with k0s. We talked through the contributor ladder and what it entails. Also discussed the upcoming reviewer role. We crossed the AI topic again and while k0sproject does not currently have any policy around this, Jussi shared that the upstream k8s [policy]() --- ## 1 September 2026 - maintainers call ### Attendees: - Jussi Nummelin (maintainer) - Tom Wieczorek (maintainer) - Natanael Copa (maintainer) - Maciej Szulik (contributor) - Serhii Ivanov (contributor) ### Agenda to be discussed - Project reviewer role - Code guidelines - AI policy / challenges with pure AI bots #### Welcome & Housekeeping - Code of Conduct - Intro new joiners #### Open Discussion #### Notes ##### Reviewer role for the project TOC wants to see better contributor ladder with a reviewer role. Jussi has a draft definition for this at https://github.com/k0sproject/community/pull/6 This was discussed and the consensus was that it's a good role. We need to finetune a bit the wording in the PR, call participants need to add review comments in the PR. ##### Code guidelines Tom started to write up some coding guidelines, targeting both humans and AI coding tools. https://github.com/k0sproject/k0s/pull/8196 Everyone agrees that this is a good start and we can build on this base. Serhii raised a very good point in that we should have linters etc to force this, whenever possible. ##### AI policy / challenges with pure AI bots We've recently seen pure AI bots opening both PRs and issues. Often those produce little value comparing to the walls of text that comes with the "contribution". One example is [#8209](https://github.com/k0sproject/k0s/issues/8209) where the bot opened up and issue purely based on a TODO comment in code with no real suggestion or anything. Not really helpfull at all. The worry is that we end up spending a lot of time grooming for these sort of things rather than actually helping k0sproject to grow and become better. We hope the coding guidelines help in this so we'd get PRs, both from bots and real humans, that match the given set of guidelines. Some discussion was also raised whether we need some real AI policy or not but no concrete actions for that, for now.