Well I thought I had the answer - I used the following approach for a binding I was developing:
@author firstname lastname - Initial contribution with input from Gemini
But then I tried the review policies as mentioned above
But then I got a bit fat slap across the wrists from that:
Author Attribution Tags
Problem:
@author firstname lastname- Initial contribution with input from Geminimentions AI tools. openHAB repository guidelines require using the contributor’s real human name without AI references.
So looks like I will be removing the Gemini reference from there…
So I guess it’s disclosure is just limited to posts in this forum, and marketplace, when it gets put on there… I think I have mentioned vibe-coding in my original post more than a few times AAP (Arrowhead) ECi Alarm Binding , but when I eventually get to finalising it, I think I will need to be aiming for a PR to openhab-addons, not marketplace, due to some dependencies which are a pain via marketplace. Being my first binding, I just trying to convince myself that its truly ready for the real world, with well over 100 hours of vibe coding, integration testing with an emulator, and running against my real alarm… Having run another review using the above MD files, tells me I have a few new things to address…Fortunately none look too ominous…
But I don’t think it matters if its a binding or whatever - I have built/hacked a few integrations in the past using python, for integration to OpenHAB via MQTT, and generally just throw them up on the forum, so people could use them, warts and all, if they wanted. If it was partly based on someone elses work and I leveraged that, I would credit that, and I think it is no different for AI these days.