|
| 1 | +# AI Usage Policy |
| 2 | + |
| 3 | +This policy was adapted from the [ghostty project](https://github.com/ghostty-org/ghostty/). |
| 4 | +The original version can be found [Ghostty's PR #10412](https://github.com/ghostty-org/ghostty/pull/10412). |
| 5 | + |
| 6 | +The NetExec project has strict rules for AI usage: |
| 7 | + |
| 8 | +- **All AI usage in any form must be disclosed.** You must state |
| 9 | + the tool(s) and model(s) you used (e.g. Claude Code, Cursor, Opus 4.6, |
| 10 | + Codex 5.2, etc) along with the extent that the work was AI-assisted. |
| 11 | + |
| 12 | +- **Pull requests created in any way by AI can only be for accepted issues.** |
| 13 | + Drive-by pull requests that do not reference an accepted issue may be |
| 14 | + rejected and closed. If AI isn't disclosed but a maintainer suspects its use, |
| 15 | + the PR may be rejected and closed. If you want to share code for a |
| 16 | + non-accepted issue, open a discussion or attach it to the existing issue. |
| 17 | + |
| 18 | +- **Pull requests created by AI must have been fully verified with |
| 19 | + human use.** AI must not create hypothetically correct code that |
| 20 | + hasn't been tested. Importantly, you must not allow AI to write |
| 21 | + code for platforms or environments you don't have access to manually |
| 22 | + test on. |
| 23 | + |
| 24 | +- **Issues and discussions can use AI assistance but must have a full |
| 25 | + human-in-the-loop.** This means that any content generated with AI |
| 26 | + must have been reviewed _and edited_ by a human before submission. |
| 27 | + AI is very good at being overly verbose and including noise that |
| 28 | + distracts from the main point. Humans must do their research and |
| 29 | + trim this down. |
| 30 | + |
| 31 | +- **No AI-generated media is allowed (art, images, videos, audio, etc.).** |
| 32 | + Text and code are the only acceptable AI-generated content, per the |
| 33 | + other rules in this policy. |
| 34 | + |
| 35 | +- **Bad AI drivers will be banned** You've been warned. We love to help junior |
| 36 | + developers learn and grow, but if you're interested in that then don't use |
| 37 | + AI, and we'll help you. |
| 38 | + |
| 39 | +- **Official maintainers have the final say** We always strive to be helpful, |
| 40 | + but there are limits. If you submit agregiously terrible AI generated code |
| 41 | + with no review, we may ban you without word. We do not want to waste our |
| 42 | + time reviewing slop if the contributor can't be bothered to review the work |
| 43 | + themselves. |
| 44 | + |
| 45 | +These rules apply only to outside contributions to NetExec. Maintainers |
| 46 | +and trusted contributors are exempt from these rules and may use AI tools at |
| 47 | +their discretion; they've proven themselves trustworthy to apply good judgment. |
| 48 | + |
| 49 | +## There are Humans Here |
| 50 | + |
| 51 | +Please remember that NetExec is maintained by humans. |
| 52 | + |
| 53 | +Every discussion, issue, and pull request is read and reviewed by |
| 54 | +humans (and sometimes machines, too). It is a boundary point at which |
| 55 | +people interact with each other and the work done. It is rude and |
| 56 | +disrespectful to approach this boundary with low-effort, unqualified |
| 57 | +work, since it puts the burden of validation on the maintainers. |
| 58 | + |
| 59 | +In a perfect world, AI would produce high-quality, accurate work |
| 60 | +every time, but today that is simply not true. This is compounded by the fact |
| 61 | +that accessibility to AI is high, allowing low skilled individuals to think |
| 62 | +that they are contributing useful code. Even many skilled programmers do not |
| 63 | +understand how to use it effectively. This has opened up a waterfall of low |
| 64 | +quality contributions across the Open Source community, wasting resources. |
| 65 | + |
| 66 | +## AI is Welcome Here, Within Reason |
| 67 | + |
| 68 | +NetExec maintainers acknowledge AI as a productive tool to some workflows, and |
| 69 | +are open to leveraging this technology to improve NetExec; however, there are |
| 70 | +many low quality AI tools whose use results in pure slop being generated. The |
| 71 | +security communinity is not immune from AI psychosis, over-hype, or FOMO. |
| 72 | +As with any new technology, it is important to understand how it works and how |
| 73 | +to best use it, not blindly apply it to every use case with the hope that it |
| 74 | +will fix all your issues. |
| 75 | + |
| 76 | +We include this section to be transparent about the project's usage about |
| 77 | +AI for people who may disagree with it. |
0 commit comments