This post is specifically in reference to Rosé Pine and the unique challenges presented in a community-driven project.
We are adopting a similar policy to several popular projects publicly disallowing LLMs and AI usage1. In short, we do not allow AI contributions.
AI-assisted pull requests have been verbose and disheartening. Rosé Pine in theory is only a palette. I say this often. We are not a business. Rosé Pine is not special. The community, however, is. The community has contributed an exhilarating amount—even before the almighty AI has graced us. Contributors are often accompanied by that little badge labelled: “First-time contributor” — a joyous site! Many times this is a user’s first-time contribution ever. Humans use our themes. Humans will continue to craft our themes.
The only argument I can see for using an LLM in this context, ignoring the detrimental ethical and environmental impact, would be for speed/convenience. Why not have someone else create for you, in mere seconds, exactly what you want? To that I say, want less. Or at least want different (this was Apple’s original motto before “Think different”2). We do not, as a society, need instant gratification. We do not need every desire to come true. We need human connection. We need community. We are a community.
Thank you to the community, seriously. You are all lovely.
Footnotes
-
Multiple sources:
- Zig’s Strict No LLM / No AI Policy
- Gleam’s “We do not accept contributions from AI agents.”
- Fish shell’s AI Contribution Policy
- Changes to SourceHut’s terms of service regarding LLMs
- LibreOffice’s decision to not (currently) include any AI features
- Why Vivaldi won’t follow the current AI trend?
- yt-dlp’s NO AI / NO LLM POLICY
- Asahi Linux’s Generative AI (LLM) Policy
- SourceHut’s terms of service regarding LLMs (also linked inline above regarding ethics)
-
This is (probably) not true. ↩