Skip to content

Create AI_POLICY.md #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Camotoy wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Create AI_POLICY.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions AI_POLICY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
Thank you for your interest in contributing to or supporting Geyser! When working with AI tools, here are the parameters we ask that you follow:
Copy link
Member

@onebeastchris onebeastchris Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Thank you for your interest in contributing to or supporting Geyser! When working with AI tools, here are the parameters we ask that you follow:
Thank you for your interest in contributing to or supporting Geyser! When working with AI tools, here are the guidelines we ask that you follow:

- Please refrain from using LLMs in any discussion on GitHub. Specifically for submitting PRs, we want to hear the changes with your own words, and you should be able to understand what a PR is doing without consulting an LLM.
- Using a translator is excluded from these rules, but please also add your original language text under English.
Copy link
Member

@onebeastchris onebeastchris Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Using a translator is excluded from these rules, but please also add your original language text under English.
- Using a translator or spell checker is permissible under these rules. When translating, please also add the text in your original language text under the English version.

- When submitting PRs, please be transparent with any AI tool used to assist with your code, along with what extent the tool was used for. This can just be one sentence: "This PR used \[specific AI tool\] to generate Javadocs."
Copy link
Member

@onebeastchris onebeastchris Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- When submitting PRs, please be transparent with any AI tool used to assist with your code, along with what extent the tool was used for. This can just be one sentence: "This PR used \[specific AI tool\] to generate Javadocs."
- When submitting PRs, be transparent about any AI tool used to assist with your code, alongside to which extent the tool was used for. This can just be one sentence: "This PR used \[specific AI tool\] to generate Javadocs."

Copy link
Member Author

@Camotoy Camotoy Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"alongside to which" I guess this is correct but seems a bit hard to parse. Maybe "and include to"?

Copy link

@dktapps dktapps Mar 22, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When submitting PRs, be transparent about which AI tools were used, and for what purpose.

would make more sense to me

- Pull requests must always be tested by a human before opening, regardless of AI usage.
- Please keep PRs focused on the relevant change or changes. Excessive whitespacing changes or changes outside the scope of the PR are not allowed.
Copy link
Member

@Kas-tle Kas-tle Mar 19, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't seem related to AI, so we could probably just remove this line or add it to existing contributor guidelines?

Copy link
Member

@onebeastchris onebeastchris Mar 19, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AI-coauthored PRs do occasionally introduce unrelated changes or "optimizations", but I agree that with the way it's currently written in, it should be moved elsewhere

- While usage of media assets is rare in our projects, please refrain from using AI-generated media for these use-cases - images, video, audio, etc. We prefer bad human drawings over "good" AI creations!

Excessive use of misused AI will result in closed PRs or bans from contributing to Geyser. We understand that the codebase can be daunting to newcomers, and for those genuinely interested in contributing we are more than happy to assist and teach proper usage!
Copy link
Member

@onebeastchris onebeastchris Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Excessive use of misused AI will result in closed PRs or bans from contributing to Geyser. We understand that the codebase can be daunting to newcomers, and for those genuinely interested in contributing we are more than happy to assist and teach proper usage!
Excessive use of misused AI will result in closed PRs or bans from contributing to GeyserMC. We understand that the codebase can be daunting to newcomers, and for those genuinely interested in contributing we are more than happy to assist!


Thank you!