Kirstie's proposed revision of the LLM policy#3
Merged
Conversation
rgbkrk
reviewed
Feb 23, 2026
| # Generative AI/LLM Contribution Policy | ||
|
|
||
| Short answer: If you (a human) didn't write the code or documentation or comment, please don't submit it to us. | ||
| We ask that all contributions (through issues and pull requests) are made by a human who is willing to take accountability for the code, documentation or comment they submit. |
rgbkrk
reviewed
Feb 23, 2026
| * We respect the **time** taken to read and review contributions, maintinaing a high standard and supportive community engagement. | ||
| * **security**: JupyterHub is trusted infrastructure for hundreds of thousands of users and we prioritize keeping their data, code, and personal configuration information secure. | ||
| * **veracity**: beyond security, we ensure our tools do what we think they do, and that we respect accuracy in communications within and beyond the scientific open source ecosystem. | ||
| * **our global society**: we seek to minimise environmental impact and human exploitation in the development and deployment of JupyterHub infrastructure. |
rgbkrk
reviewed
Feb 23, 2026
| 1. Only submit code or documentation to JupyterHub that you wrote and that you understand. | ||
| * We have chosen this requirement given our concerns around **copyright**, **reviewer burden**, and to maintain **auditable accountability** for the **veracity** of our work. | ||
| * We leave the interpretation of this request to you: tool-assisted coding and automation leaves some gray areas and we recognize that everyone has different perspectives on the use of LLMs for supporting their open source contributions. | ||
| * We strongly endorse using deterministic tools to check and improve the quality of your code, such as automated code dependency updates, linter auto-fixes, refactor tools, etc. |
rgbkrk
reviewed
Feb 23, 2026
| 2. Communicate in issue and pull request threads in your own words. | ||
| Please do not use the verbatim output of an LLM in conversation with our user, reviewer and maintainer community. | ||
| * We have chosen this requirement given our priority to **value human co-creation**. | ||
| 3. We do not plan to include `AGENTS.md`, `CLAUDE.md` or similar files to our repos as we prefer human contributors follow the [contribution guidelines](guide.md) that already exist. |
There was a problem hiding this comment.
I feel like this is a mis step, because this is our chance to force something in the context window that can inform about the policy directly. Even if just "Refer to contributing docs. NEVER open issues. NEVER open PRs." Not my preferred but I feel it'll give us better balance.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See discussion in jupyterhub#880 to keep the discussion in one place