Do we need an AI contribution policy?

28 views
Skip to first unread message

Lee Yarwood

unread,
Aug 1, 2025, 4:37:59 AM8/1/25
to kubevirt-dev
I've created a community issue asking $subject after a few folks
discussed the topic downstream:

Does the project need an AI contribution policy?
https://github.com/kubevirt/community/issues/411

I'd appreciate thoughts from the community and any missing context
(the current CNCF policy etc) in the issue if anyone is interested.
I'll also raise this during the next community call.

Cheers,

Lee

Fabian Deutsch

unread,
Aug 4, 2025, 4:51:26 AM8/4/25
to Lee Yarwood, kubevirt-dev
On Fri, Aug 1, 2025 at 10:38 AM 'Lee Yarwood' via kubevirt-dev <kubevi...@googlegroups.com> wrote:
I've created a community issue asking $subject after a few folks
discussed the topic downstream:

Does the project need an AI contribution policy?
https://github.com/kubevirt/community/issues/411

IMO - Yes.

We should be clear about if/how KubeVirt accepts AI contributions.

To me we should be open to accept AI co-developed patches.
If we do accept co-developed patches, then we should require transparency on it.

Lee, thanks for collecting some examples on the issue already, I added a link to a similar discussion on lkml - what I like about their approach is to add common coding assistant config files to the main tree.

- faian
 


I'd appreciate thoughts from the community and any missing context
(the current CNCF policy etc) in the issue if anyone is interested.
I'll also raise this during the next community call.

Cheers,

Lee

--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kubevirt-dev/CAPkJ9DtUUQNjf5BGE7E0-%3Dp9Uy2voo9EVqk-E4n6ANNCHSw%3DEQ%40mail.gmail.com.

Itamar Holder

unread,
Aug 5, 2025, 3:05:24 AM8/5/25
to Fabian Deutsch, Lee Yarwood, kubevirt-dev
Lee, thanks a lot for raising this topic! It is indeed interesting and important.

I've commented on the issue.

Lee Yarwood

unread,
Aug 8, 2025, 10:56:17 AM8/8/25
to kubevirt-dev
I've posted a draft for review under
https://github.com/kubevirt/community/pull/415

Comments, suggestions, disgust at the draft ideas etc all welcome!

Cheers,

Lee

Lee Yarwood

unread,
Sep 29, 2025, 5:04:29 PM9/29/25
to kubevirt-dev
Hello Folks,

Just bumping the thread asking for anyone with an interest in this
topic to post to the PR in the coming weeks as I'd like to attempt to
close this PR out (be it merged or closed) by v1.7.0 FF at the end of
October [1] so we can move forward with this during v1.8.0.

Cheers,

Lee

[1] https://github.com/kubevirt/sig-release/blob/main/releases/v1.7/schedule.md

Lee Yarwood

unread,
Jan 21, 2026, 4:41:04 AMJan 21
to kubevirt-dev
Hello Folks,

I'm going to try to close this initial policy PR out in the coming
days and plan on raising it for discussion on today's NA/EU community
call.

Introduce AI contribution policy
https://github.com/kubevirt/community/pull/415

Can I ask anyone interested in this topic to review the latest
revision of the PR ahead of the call so we can work through any
remaining concerns.

Cheers,

Lee

Lee Yarwood

unread,
Feb 3, 2026, 9:49:56 AM (5 days ago) Feb 3
to kubevirt-dev
Hello all,

Many thanks to everyone who contributed in this thread or on the PR,
the policy has now landed and is available below:

https://github.com/kubevirt/community/blob/main/ai-contribution-policy.md

Feel free to reply here with any questions or concerns, PRs are also
welcome if you feel it can be improved.

I've posted the following user-guide PR to link to this policy but I'd
also be happy to list it in full somewhere if folks think that would
be useful:

https://github.com/kubevirt/user-guide/pull/962

Cheers,

Lee
Reply all
Reply to author
Forward
0 new messages