Add guidelines for using AI tools

[chriscool]

There have been discussions both between Git GSoC mentors among themselves and between all the GSoC mentors on the Google Summer of Code Mentors List (google-summer-of-code-mentors-list@googlegroups.com) about applicants using AI more and more. It seems related to a big increase in the number of spam proposals that Git and some other project have been receiving recently.

Let's try to address this issue by providing guidelines for using AI tools to mentoring program candidates.

The Conservancy also recently organized talks about the use of AI tools to develop open source software. I have tried to take this into account especially by adding a "Legal issues" section in the guidelines.

[KarthikNayak]

Thanks @chriscool this looks good, some small nits from me. Feel free to ignore! :)

[sivaraam]

Overall, this seems like a good addition. Thank you for working on this, Christian! Just a few things that I think could be corrected.

[chriscool]

Thanks @sivaraam, @shejialuo and @KarthikNayak for your suggestions! As it looks like you are all overall happy with this, I am going to merge it soon. We can still improve it afterwards. Especially if we then discuss this on the mailing list, there might be a number of additional comments.

[sivaraam]

Sure, Christian. There has been one thing that's been bugging me regarding this for a bit. The guidelines freely cover the proposal related points and code related points across sections. I wonder if it would make sense to restructure the sections a bit to distinguish our thoughts regarding both more explicitly and have general points separately. 🤔

[chriscool]

@sivaraam I am not sure we can make a very significant distinction between code and proposal. In particular, as part of code contributions, writing commit messages and updating documentation share some aspects with writing a proposal.

So I wouldn't be against it if there is a good way to do it, but I don't see a good one right now. If you do, feel free to send a separate PR when this one is merged.