|
| 1 | +<!-- deno-fmt-ignore-file --> |
| 2 | + |
| 3 | +AI usage policy |
| 4 | +=============== |
| 5 | + |
| 6 | +This policy is inspired by [Ghostty's AI policy][1]. |
| 7 | + |
| 8 | +The Fedify project has the following rules for AI usage: |
| 9 | + |
| 10 | + - *All AI usage in any form must be disclosed.* You must state the tool you |
| 11 | + used (e.g., Claude, Cursor, GitHub Copilot) along with the extent that |
| 12 | + the work was AI-assisted in your pull request description and/or commit |
| 13 | + messages. |
| 14 | + |
| 15 | + - *Pull requests created in any way by AI can only be for accepted issues.* |
| 16 | + Drive-by pull requests that do not reference an accepted issue will be |
| 17 | + closed. If AI isn't disclosed but a maintainer suspects its use, the PR |
| 18 | + will be closed. If you want to share code for a non-accepted issue, open |
| 19 | + a discussion or attach it to an existing discussion. |
| 20 | + |
| 21 | + - *Pull requests created by AI must have been fully verified with human use.* |
| 22 | + AI must not create hypothetically correct code that hasn't been tested. |
| 23 | + Importantly, you must not allow AI to write code for platforms or |
| 24 | + environments you don't have access to manually test on. |
| 25 | + |
| 26 | + - *Issues and discussions can use AI assistance but must have a full |
| 27 | + human-in-the-loop.* This means that any content generated with AI must |
| 28 | + have been reviewed and edited by a human before submission. AI is very |
| 29 | + good at being overly verbose and including noise that distracts from |
| 30 | + the main point. Humans must do their research and trim this down. |
| 31 | + |
| 32 | + - *AI-generated media (images, diagrams, etc.) is allowed only in |
| 33 | + documentation, and must be clearly labeled as AI-generated.* Text and |
| 34 | + code are acceptable AI-generated content per the other rules in this |
| 35 | + policy. For documentation visuals like diagrams or illustrations, |
| 36 | + AI-generated content is permitted but must include clear attribution |
| 37 | + (e.g., “Diagram generated with DALL-E” or “Created using Midjourney”). |
| 38 | + |
| 39 | + - *Violations of this policy may result in being banned from contributing.* |
| 40 | + We want to help contributors learn and grow, but repeated or intentional |
| 41 | + violations of this policy undermine trust and burden maintainers. |
| 42 | + |
| 43 | +These rules apply only to outside contributions to Fedify. Maintainers are |
| 44 | +exempt from these rules and may use AI tools at their discretion; they've |
| 45 | +proven themselves trustworthy to apply good judgment. |
| 46 | + |
| 47 | +[1]: https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md |
| 48 | + |
| 49 | + |
| 50 | +There are humans here |
| 51 | +--------------------- |
| 52 | + |
| 53 | +Please remember that Fedify is maintained by humans. |
| 54 | + |
| 55 | +Every discussion, issue, and pull request is read and reviewed by humans |
| 56 | +(and sometimes machines, too). It is a boundary point at which people interact |
| 57 | +with each other and the work done. It is rude and disrespectful to approach |
| 58 | +this boundary with low-effort, unqualified work, since it puts the burden of |
| 59 | +validation on the maintainer. |
| 60 | + |
| 61 | +In a perfect world, AI would produce high-quality, accurate work every time. |
| 62 | +But today, that reality depends on the driver of the AI. And today, most |
| 63 | +drivers of AI are just not good enough. So, until either the people get |
| 64 | +better, the AI gets better, or both, we have to have rules to protect |
| 65 | +maintainers. |
| 66 | + |
| 67 | + |
| 68 | +AI is welcome here |
| 69 | +------------------ |
| 70 | + |
| 71 | +Fedify is written with plenty of AI assistance, and many maintainers embrace |
| 72 | +AI tools as a productive tool in their workflow. As a project, we welcome |
| 73 | +AI as a tool! |
| 74 | + |
| 75 | +*Our reason for this policy is not due to an anti-AI stance*, but instead due |
| 76 | +to the number of highly unqualified people using AI. It's the people, not |
| 77 | +the tools, that are the problem. |
| 78 | + |
| 79 | +We include this section to be transparent about the project's usage of AI for |
| 80 | +people who may disagree with it, and to address the misconception that this |
| 81 | +policy is anti-AI in nature. |
0 commit comments