Hi Devs

I’d like to propose we put together some guidance and policies within our
Fineract community for AI assisted and AI generated code.  Maybe this needs
a vote at some point but for now I think it’s useful to discuss.  Later I
think it belongs at the level of coding and process guides.

This is an active area of discussion within the broader open source
movement and within each project of open source foundation.  AI tooling is
evolving much faster than copyright law and best practices can be written
so our discussion isn’t a final destination.

First it must be said, all contributors sign an ICLA (individual
contributor license agreement), which is a legal document. It is required
for Committers.  This states that irrespective of the manner in which the
PR was created- any auto completing IDE or whatever- the Contributor “owns
it”.  This is at the core of the current ASF policies for ai. Please review
https://www.apache.org/legal/generative-tooling.html#approved-tools-list

I’d like to suggest that we encourage good use of AI tools.  For example, other
projects at the ASF are reportedly using AI tools for test coverage. For
us, this requires some Fineract and financial domain knowledge.

We also have heard of examples of projects being bombarded by new “vibe
coded” PRs.  One way to deal with that is to disallow more than one active
PR under consideration.

See also
https://vibe-coding-manifesto.com/. For other considerations.

Thoughts?

Thanks

Reply via email to