gsoc26-AI-policy.md

# code
  - you can and SHOULD use AI when writing code
  - please avoid some of the things that AI likes to do in code:
    - write long, unnecessary comments on self explanatory code
    - use non-ascii characters in comments
    - generate redundant (even though it may be correct) code
    - write repetitive code that could be easily refactored
    - reimplement functionality that can be taken from a library
  - in short, PRs that are AI generated without human guidance tend to be unnecessarily long
  - these PRs will NOT be reviewed (to save on the reviewer time)
  - more of an advice than a policy... ask the AI questions
    - you should review each lines it writes
    - if something is not clear to you, ask it what it does and why it is needed
    - in some cases it will explain - and you have learned something new
    - in some cases it will say something like:
      "You are absolutely right! 
      this line is needed only if your code runs in outer space in proximity to a black hole - 
      you can safely remove it"...

# communication
  - would advise against using AI when writing the proposal - they should be concise and accurate
    - proposals are NOT judged for style or language
  - please avoid using AI to write emails (or any other communication)
    - instead of writing a prompt saying what the email should say - just send that information
    - same amount of work for you, much less to read for the recipient