Skip to content

Update CODE_OF_CONDUCT to include LLM transparency#3

Merged
JoviDeCroock merged 2 commits intomasterfrom
JoviDeCroock-patch-1
Nov 21, 2025
Merged

Update CODE_OF_CONDUCT to include LLM transparency#3
JoviDeCroock merged 2 commits intomasterfrom
JoviDeCroock-patch-1

Conversation

@JoviDeCroock
Copy link
Member

Added a section on transparency regarding the use of LLMs in issue and pull request submissions.

Added a section on transparency regarding the use of LLMs in issue and pull request submissions.
JoviDeCroock added a commit to preactjs/preact that referenced this pull request Nov 21, 2025
Looks like our global one can then take presedence once preactjs/.github#3 is merged
* Focusing on what is best for the community
* Showing empathy towards other community members

We recognize that LLM's have become an integral tool for many users, however when using LLMs to help write issues or pull requests, disclose this. Transparency preserves the collaborative integrity that makes open-source communities work. It's the difference between "I used AI to help structure this bug report" (honest, helpful) and silently passing off generated content as your own analysis (deceptive, counterproductive). We as maintainers want to engage with humans rather than LLM-generated messages, put time in your issue report and that will be reflected back.
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure that this is enforceable in practice. Wondering if we should rephrase it as something along the lines of:

"Be mindful of maintainers time. When using LLM's to create issues, double check that the content is not hallucinated and matches reality."

Would love to hear @rschristian 's perspective too.

Copy link
Member Author

Choose a reason for hiding this comment

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

The fact that this in there is ample reason to close issues like the signals one. I think it is enforceable and other repos seem to be doing it as well

Copy link
Member

Choose a reason for hiding this comment

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

Fair point.

Copy link
Member

Choose a reason for hiding this comment

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

I think it's enforceable enough. At the end of the day we can already close issues for any arbitrary reason, this just gives a little extra backing when/if we do so.

Co-authored-by: Marvin Hagemeister <hello@marvinh.dev>
@JoviDeCroock JoviDeCroock merged commit efe4128 into master Nov 21, 2025
@rschristian rschristian deleted the JoviDeCroock-patch-1 branch November 21, 2025 20:39
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.

3 participants