Hello Nathalie,

Thank you for the proposal. It seems to be a good approach. A chapter can be added to the README.md files, which already contain a contributing chapter.

Regards,

Arnaud

 

From: Chan King Choy, Nathalie via Tsc <tsc@lists.openampproject.org>
Sent: Wednesday, June 17, 2026 1:01 AM
To: OpenAMP TSC (tsc@lists.openampproject.org) <tsc@lists.openampproject.org>
Subject: [OA-Tsc] Creating AI-generated code policy for OpenAMP

 

AMD General

 

Hi OpenAMP TSC members,

 

The question came up in a recent OpenAMP System Reference call regarding use of AI generated code for OpenAMP.  Many companies are pushing heavily for their engineers to adopt AI assistance wherever possible.

 

Here are some resources to seed the discussion for creating AI-generated code policy for OpenAMP.

 

OpenAMP ties in closely to Linux kernel. Policy for Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/coding-assistants.rst

  • Human is responsible fully responsible for the contribution to the kernel, ensuring it follows the rules & meets license requirements
  • Transparency: Use assisted-by tag

 

OpenAMP ties in closely to Zephyr.  Policy for Zephyr is nearly identical to Linux kernel, like one did copy-paste-tweak of the other: https://docs.zephyrproject.org/latest/contribute/guidelines.html#ai-coding-assistants

 

In case folks want to broaden their analysis, here are some references shared by the Linux Foundation legal team to the LF Member Counsels:

    • Each Linux Foundation project gets to decide for themselves
    • High-level guidelines provided
    • Debian didn’t set an official policy & would handle case-by-case. 
    • Red Hat highlighted list of legal issues related to AI being debated in OSS communities

 

 

What are your thoughts on creating an AI-generated code policy for OpenAMP?

 

Thanks & regards,

Nathalie