I suggest:

1. Refer contributors to the ASF guidance
   <https://www.apache.org/legal/generative-tooling.html> and
2. (continue to) remind contributors to follow all existing Fineract
   contribution guidelines.

The ASF guidance makes sense as a starting point, and is (understandably) quite vague. I like it.

"Generated-by: " or "AI-assisted: " trailers are interesting but the idea is half-baked. I think we should keep an eye on this but not add it as a committer requirement until the left- and right-hand sides are standardized.

I hope we don't need extensive new rules/overhead (despite this new AI era), so I'm -1 for Paul's proposal.

James, I like the ideas in the vibe coding manifesto and I'm nodding at everything else you wrote.

I would support limiting in-flight PRs to, say, 3 or so, but it's still more about PR size/understandability, competence, good intent, and good comms. We already say "no code dumps" and that's a great baseline.

Best,
-Adam

--
Adam Monsen
Software Engineer » Mifos Initiative
Release Manager » Apache Fineract
Author » Steadfast Self-Hosting
PGP key » 0xA9A14F22F57DA18

Reply via email to