Proposed AI policy
There is now a proposed AI policy. For discussion of the details, please direct your comments to the PR itself. This discussion thread is a continuation of an earlier discussion. In a relatively short period of time we seem to have arrived a point where some allowance for AI seems necessary. Better to require people disclose the AI model(s) they have used and sign an updated CLA than pretend people aren't already contributing AI-assisted code.
@Dmitry Belyavsky Only those that want to submit work generated by AI will need to sign CLA again. I do not think there is any way around that. Furthermore, we recently do not have any issues with signing CLAs. It was quite a while ago when we saw somebody not willing to sign a CLA. And, frankly, with AI we already have a lot of contributors, more than we can actually currently handle as for reviewing.
Could the existing CLA be taken to mean "does not include AI", so only contributors wanting to use AI would have to sign the updated CLA? That would restrict the disruption to only those affected by it.
@Peter Gutmann that is exactly what the proposed policy says: "The old CLA remains valid for contributions that do not include non-trivial AI-generated content. If you are not using AI assistance, there is no need to re-sign."
@Matt Caswell Ah, reading comprehension fail, it's further down in the "The CLA Requirement" section.
I may have missed it, but Can someone share the updated CLA that we are referncing in the ai-policy? I still see only the 1.0 policy from https://openssl-library.org/policies/cla/
@Craig Lorentzen It hasn't been issued/written yet. As noted in the PR "This presupposes the existence of some version of the CLA with an AI clause", i.e. we know we need one, but haven't issued it yet.
@matt s/It has/It hasn't/
@Richard Levitte (individual) Fixed!
This is excellent! Thank you for sharing this email! All of my comments on the OpenSSL repo were not AI generated. The little bit of allowance I was asking for was just one iteration help with a new dot c file for the atomic operations. I will elaborate on the discussion PR further if @drqedwards is not blocked on there anymore
In case anyone else finds this useful, the Rust folks have been working on something similar, https://github.com/rust-lang/rust-forge/pull/1040, and that in turn links to posts on how other projects have handled it.
🙏. CLA hear would mean Contributor , license agreement. I don’t understand this post completely especially in the context
I am seeking clarification to avoid ambiguity to be on the same page with folks here
Have a nice day
Best regards
Gayatri
@Gayatri Yes CLA == Contributor License Agreement
🙏, for clarification,
Best , Gayatri
What I don't like in the idea is the resigning of the updated CLA. People are negative to the current CLA approach, and resigning will not make the situation any better