Argopy policy for AI-powered contributions

[quai20]

In the past few weeks, argopy faced some contribution requests (last one here : #636) where AI was clearly engaged in the process of either finding the issue, analyzing the code or proposing a solution with some associated unit testing.

After a lot of discussion between @gmaze & @quai20 , it seems important to clarify our position, or argopy position, regarding AI powered contribution to the sotware. We believe that is important to clarify this in a AI_POLICY.md file. This issue aims to define the content of this file.
Some inspiration from other OSS groups :

• Clarifying a CNCF-Wide AI Contribution Policy for Projects? cncf/foundation#1285
• https://github.com/cloudnative-pg/governance/pull/46/changes
• https://github.com/ghostty-org/ghostty/pull/10412/changes

Some points appear important to tackle here :

• Human responsibility in understanding a contribution in the context of the whole software
• Human capability to explain & maintain the proposed code
• Written exchanges in the issues or PR
• Where to put the cursor between AI auto completion aid from a well known collaborator, and a Claude based approach from an outside unknown dev ?
• Copyright & Licensing
• Many other things to be discussed here.
• ...

[gmaze]

@quai20 also I just thought that the policy added by #639 need to find its way into the documentation:

• the text should be added to the Contribution page, probably as new full section.
• this new section could then be mentioned in the Carbon emissions page
• Also, the What's New page should be updated

[gmaze]

And I wonder who we could poke to ask for some feedbacks onto this

[quai20]

Closing the issue & turning this topic into a discussion