janniklinde commented on PR #2570: URL: https://github.com/apache/systemds/pull/2570#issuecomment-5277547218
> Good to see this written down, and the restrictions on agents opening PRs, issues, or posting to project channels are stronger than what the foundation requires. Worth keeping. > > Two gaps worth closing: > > The disclosure trailer specifies Assisted-by: AI. ASF generative tooling guidance recommends Generated-by: with the tool named. A bare "AI" record indicates that a tool was used but not which one, so the trailer can't support any later provenance questions, and it won't match the convention other projects use. However, this is also under discussion on legal-discuss at the moment. > > The document is silent on IP provenance. The foundation's concerns are that the tool's terms of use must not conflict with the Open Source Definition, and that any third-party material appearing in the output must be traceable and appropriately licensed. A contributor could follow this document exactly and still commit output from a tool whose terms are incompatible. That is the part that poses a risk to the project and the ASF, and I suggest it should be mentioned. Thank you for pointing out those issues @justinmclean. I opened a follow-up PR (#2588) to address the points on IP provenance. Regarding the disclosure trailer, our AI policy requires disclosure of meaningful AI contributions, which could be a decision affected by an LLM (e.g., a local code review motivating a major manual code change). So I'd be hesitant to use generated-by in these cases. In terms of disclosing used tools, we don't yet have clarity of what exactly should be disclosed (e.g., the top-level tool used to generate code, any LLM model and version that might have contributed, ...), so further discussions are needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
