Skip to content

Add AI contribution guide#4211

Open
michalhabera wants to merge 2 commits into
mainfrom
michal/ai-contribs
Open

Add AI contribution guide#4211
michalhabera wants to merge 2 commits into
mainfrom
michal/ai-contribs

Conversation

@michalhabera
Copy link
Copy Markdown
Contributor

AI assistance:
I used ChatGPT 5.5 to draft parts of this PR. I reviewed, edited, tested, and take responsibility for the final contribution.

Copy link
Copy Markdown
Member

@jorgensd jorgensd left a comment

Choose a reason for hiding this comment

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

LGTM!

@jhale
Copy link
Copy Markdown
Member

jhale commented May 13, 2026

Looks good; let's see how it goes over the next 6 months and then we can update.

@michalhabera
Copy link
Copy Markdown
Contributor Author

Looks good; let's see how it goes over the next 6 months and then we can update.

Very true. Even if all contributions will be AI assisted in the near future, is would be good to keep the responsibility and model disclosure.

@IgorBaratta
Copy link
Copy Markdown
Member

One small suggestion, I think it would be helpful to explicitly mention the licensing risks associated with AI coding assistants. The main concern is that an AI might inadvertently reproduce restrictively licensed code (like GPL) into the repo. Perhaps making it explicit that the contributor is responsible for verifying this?

@michalhabera
Copy link
Copy Markdown
Contributor Author

One small suggestion, I think it would be helpful to explicitly mention the licensing risks associated with AI coding assistants. The main concern is that an AI might inadvertently reproduce restrictively licensed code (like GPL) into the repo. Perhaps making it explicit that the contributor is responsible for verifying this?

There is the statement:

The contributor must:
...

  • ensure that licensing requirements are satisfied,

Is this not enough?

@IgorBaratta
Copy link
Copy Markdown
Member

One small suggestion, I think it would be helpful to explicitly mention the licensing risks associated with AI coding assistants. The main concern is that an AI might inadvertently reproduce restrictively licensed code (like GPL) into the repo. Perhaps making it explicit that the contributor is responsible for verifying this?

There is the statement:

The contributor must:
...

  • ensure that licensing requirements are satisfied,

Is this not enough?

You're right, I missed that.
I still think there's value in being explicitly clear about AI in this specific context, but happy if you merge without.

@jhale
Copy link
Copy Markdown
Member

jhale commented May 14, 2026

I agree @IgorBaratta, but how should a contributor practically verify this?

@IgorBaratta
Copy link
Copy Markdown
Member

Good point, @jhale.
I think it's hard to verify unless the contributor actively runs their own plagiarism checks or relies on filters (like Copilot's public code blocker), which are not available in most AI assistants.
Maybe "ensure licensing requirements are satisfied" is the best we can do for now without overcomplicating and can always revisit it in 6 months as you suggested!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants