This PR introduce a doc about AI usage in differents projects of CoMaps
All feedback are appreciated
Text has been reviewed by reverso
Signed-off-by: Jean-Baptiste jeanbaptiste.charron@outlook.fr
ai_usage into main
This PR introduce a doc about AI usage in differents projects of CoMaps
All feedback are appreciated
Text has been reviewed by reverso
Signed-off-by: Jean-Baptiste jeanbaptiste.charron@outlook.fr
Signed-off-by: Jean-Baptiste <jeanbaptiste.charron@outlook.fr>
Thanks for getting this started @jeanbaptisteC!
I think in spirit this is very similar to the agreement that forgejo has adopted for their work, see forgejo/governance#325/
I wonder if it would be easiest to either just adopt their agreement in whole or make adaptations to it if we think it's useful?
My thinking is that the forgejo developers and community has put a lot of effort and discussion into coming up with this (see forgejo/discussions#366) and we could potentially benefit from their work? 🙂
Yes, I agree this idea
I think we can add a mention to allow admins to close a PR or an issue if an user doesn't respect these rules
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?