Question about AI-assisted contributions and an Akahu importer integration

[bedesv]

Hi,

I wanted to ask for clarification on the intent of the No AI contributions rule.

Is the rule mainly intended to prevent low-effort, unreviewed, or poorly understood AI-generated contributions, or is the project not willing to accept code that involved AI generation at all?

The reason I ask is that I have built an Akahuintegration for the data importer and would like to contribute it to the data-importer project. I have a draft PR here: bedesv/data-importer#2

I used AI extensively while building it, but I wrote the initial specification, guided the implementation, reviewed every line myself, and have been using it personally for a couple of months. I would be willing to maintain it if accepted.

There seems to be some interest in this integration from New Zealand users, including this Reddit thread, so I think it could be a useful addition to the project.

I completely understand if the policy means that AI-assisted code cannot be accepted in any form. I just wanted to clarify before spending more time preparing the contribution.

[JC5]

Hey, thanks for starting this discussion.

I can't accept it, sorry about that.

Cheers,
James

[bedesv]

Okay no worries, I'll maintain the fork for now. Do you mind if I look into publishing my fork to Docker Hub?

I would like to contribute this integration back to the mainline data-importer so I will rewrite it (eventually). I saw the PR template asks about AI use in code generation, test/benchmark generation, documentation, and research and understanding. Do you auto-reject if any of these are true?