All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Paul Barker" <paul@pbarker.dev>, <docs@lists.yoctoproject.org>
Cc: <yocto@lists.yoctoproject.org>,
	<openembedded-architecture@lists.openembedded.org>
Subject: Re: [docs] [PATCH] contributor-guide: Adopt new AI-Assisted Contribution Policy
Date: Wed, 04 Nov 2026 15:17:10 +0100	[thread overview]
Message-ID: <DMMHOGIG8FZ2.3EGLH78Y5XISP@bootlin.com> (raw)
In-Reply-To: <20261102-ai-policy-v1-1-db2e89267a1e@pbarker.dev>

Hi,

Thanks, will merge to master-next with the following formatting fixes:

diff --git a/documentation/contributor-guide/ai-assisted-contribution-policy.rst b/documentation/contributor-guide/ai-assisted-contribution-policy.rst
index 7b8ee8284..f35b58fdf 100644
--- a/documentation/contributor-guide/ai-assisted-contribution-policy.rst
+++ b/documentation/contributor-guide/ai-assisted-contribution-policy.rst
@@ -11,15 +11,15 @@ include non-trivial AI-generated content.
 
 A *contribution* is anything you send to the project, including:
 
-- Patches, commit messages and cover letters
+-  Patches, commit messages and cover letters
 
-- Review comments, discussions and other mailing list submissions
+-  Review comments, discussions and other mailing list submissions
 
-- Bug reports and comments in Bugzilla
+-  Bug reports and comments in Bugzilla
 
-- Security reports sent to the Security Team
+-  Security reports sent to the Security Team
 
-- Wiki content
+-  Wiki content
 
 *AI-generated content* is anything produced by a Large Language Model
 (LLM) or other generative AI technology, including output from AI
@@ -49,17 +49,17 @@ General conditions
 
     1. Contributors should ensure that the terms and conditions of the
        generative AI tool do not place any contractual restrictions on how
-       the tool’s output can be used that are inconsistent with the
-       project’s open source software license, the project’s intellectual
+       the tool's output can be used that are inconsistent with the
+       project's open source software license, the project's intellectual
        property policies, or the Open Source Definition.
 
     2. If any pre-existing copyrighted materials (including pre-existing
        open source code) authored or owned by third parties are included in
-       the AI tool’s output, prior to contributing such output to the
+       the AI tool's output, prior to contributing such output to the
        project, the Contributor should confirm that they have have
-       permission from the third party owners–such as the form of an open
+       permission from the third party owners-such as the form of an open
        source license or public domain declaration that complies with the
-       project’s licensing policies–to use and modify such pre-existing
+       project's licensing policies-to use and modify such pre-existing
        materials and contribute them to the project. Additionally, the
        contributor should provide notice and attribution of such third party
        rights, along with information about the applicable license terms,
@@ -77,7 +77,7 @@ The Yocto Project is a collaborative endeavour and our community is as
 valuable as our code base for the long-term health of the project. At a
 fundamental level, we each need to take responsibility for what we
 contribute to the project. For example, this includes ensuring that our
-contributions follow the project’s Code of Conduct. It also includes
+contributions follow the project's Code of Conduct. It also includes
 being respectful of the finite bandwidth that we all have for reading,
 reviewing and responding to contributions.
 
@@ -122,7 +122,7 @@ Transparency
 **Contributors need to disclose where they have used AI-generated output
 in their submissions to the project**. As stated above, incidental or
 trivial use of AI-generated output within an otherwise human authored
-submission doesn’t require disclosure - but if in doubt, err on the side
+submission doesn't require disclosure - but if in doubt, err on the side
 of disclosing the use of AI tools.
 
 The use of generative AI and LLMs in software development is a rapidly
@@ -139,7 +139,7 @@ In patches and commits
 ----------------------
 
 **Where AI-generated code is contributed to the project, commit messages
-must include the ``AI-Generated`` tag identifying the AI tool or
+must include the** ``AI-Generated`` **tag identifying the AI tool or
 framework and the specific AI model used**. We encourage contributors to
 be as specific as they can be. For example::
 
@@ -193,7 +193,7 @@ Enforcement
 
 Violations of this policy may result in contributions being rejected or
 deleted as appropriate. Repeated violations will be dealt with through
-the project’s `Code of Conduct`_ policy.
+the project's `Code of Conduct`_ policy.
 
 .. _Linux Foundation Generative AI Policy: https://www.linuxfoundation.org/legal/generative-ai
 .. _Code of Conduct: https://www.yoctoproject.org/code-of-conduct

Antonin

  reply	other threads:[~2026-11-04 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02  9:48 [PATCH] contributor-guide: Adopt new AI-Assisted Contribution Policy Paul Barker
2026-11-04 14:17 ` Antonin Godard [this message]
2026-11-06 10:42   ` [docs] " Paul Barker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DMMHOGIG8FZ2.3EGLH78Y5XISP@bootlin.com \
    --to=antonin.godard@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=openembedded-architecture@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.