On 03/10/2025 10:55, Ilya Maximets wrote:
> On 9/18/25 3:30 PM, Eelco Chaudron via dev wrote:
>> Add a section to the submitting-patches documentation describing the
>> use of an "Assisted-by" tag for patches created with AI assistance.
>>
>> Co-authored-by: Mark Michelson <[email protected]>
>> Signed-off-by: Eelco Chaudron <[email protected]>
>> Signed-off-by: Mark Michelson <[email protected]>
>>
>> ---
>> This patch is based on a similar change in the OVN project.
>> For more details, see the link below:
>>
>> https://patchwork.ozlabs.org/project/ovn/patch/[email protected]/
>> ---
>>  .../internals/contributing/submitting-patches.rst   | 13 +++++++++++++
>>  1 file changed, 13 insertions(+)
>>
>> diff --git a/Documentation/internals/contributing/submitting-patches.rst 
>> b/Documentation/internals/contributing/submitting-patches.rst
>> index 8a8bc11b0..cb328af64 100644
>> --- a/Documentation/internals/contributing/submitting-patches.rst
>> +++ b/Documentation/internals/contributing/submitting-patches.rst
>> @@ -357,6 +357,19 @@ Open vSwitch please sign off your work.  The sign off 
>> certifies the following:
>>  
>>  See also http://developercertificate.org/.
>>  
>> +AI-assisted Contributions
>> +-------------------------
>> +
>> +OVS is a Linux Foundation project, and the Linux Foundation's policy for
> 
> I think, we should add the 'Collaborative' before the project to be more
> accurate, in which case may also need to capitalize the P in the 'project'.
> (see examples on the website)
> 
>> +AI-generated patches can be found here:
>> +https://www.linuxfoundation.org/legal/generative-ai .
>> +
>> +OVS allows the use of AI assistants in producing patches. Contributions
>> +which have used an AI assistant should disclose the use of the assistant by
>> +using the "Assisted-by" tag. While AI-assisted patches are allowed, the 
>> author
>> +of the patch is ultimately responsible for ensuring that the AI-generated 
>> code
>> +has not violated any terms of the Developer's Certificate of Origin.
>> +
> 
> This document is pretty consistent with using double spaces between
> sentences, so we should do the same in the added text.
> 
> With these changes, I think the policy itself is fair enough.  The use
> of the tag is a little debatable, but we can tweak this policy if needed
> later.  For now it seems like a decent starting point:
> 

+1

Acked-by: Kevin Traynor <[email protected]>

> Acked-by: Ilya Maximets <[email protected]>
> 

_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to