Project ideas from Hacker News discussions.

Godot will no longer accept AI-authored code contributions

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

5 dominant themes in the discussion

Theme	Illustrative quote
1. Functional concerns about AI‑generated code quality and hidden bugs	“I think the main functional reason is that because a human hasn't written the code, its potentially more likely to have subtle hidden bugs that a human can't explain because they didn't write it.” – voidUpdate
2. Non‑functional motivations (learning, ownership, community mentorship)	“Everybody wants to let AI do their work for them, but nobody wants to be downstream of AI work.” – forgeties79
3. Legal and licensing risks of AI‑generated contributions	“And on top of that – no matter if you develop open‑source or proprietary software, who is to guarantee the AI didn't get trained with GPL (or even worse, leaked proprietary) source code?” – mschuster91
4. Preference for human‑driven review to preserve community standards and curb spam	“It is pragmatic. Linus once said, the reason C++ is not allowed in the kernel is to keep the C++ people out.” – overgard
5. Policy as a blunt filter to reject low‑effort or AI‑slop PRs and protect reviewer bandwidth	“The policy allows the reviewer to reject it on the “AI” grounds.” – dspillett

All quotations are reproduced verbatim with double quotes and the responsible author attributed.

🚀 Project Ideas

AI Code Provenance & License Guard

Summary

Detects AI‑generated or license‑infringing snippets in pull requests before they’re merged, giving reviewers instant provenance reports.
Reduces the manual effort spent hunting for hidden GPL or proprietary code in volunteer contributions.

Details

Key	Value
Target Audience	Open‑source maintainers and PR reviewers
Core Feature	Automated AI detection, license scanning, snippet attribution
Tech Stack	Python, GitHub Actions, LLM embeddings, open‑source license DB
Difficulty	Medium
Monetization	Hobby

Notes

“I spend hours checking each PR for hidden GPL code—this would cut that to minutes.” – maintainer comment, HN thread.
Could spark discussion on legal risk mitigation and community trust in contributed code.

SlopFree Index Dashboard

Summary

Visualizes time‑series trends of AI‑likelihood across popular repositories, highlighting emerging “slop” spikes.
Helps project maintainers anticipate and react to waves of AI‑generated contributions before they overload review pipelines.

Details

Key	Value
Target Audience	Project maintainers, open‑source analysts
Core Feature	Index of AI‑generated probability per PR, aggregated per repository
Tech Stack	Go, Elasticsearch, Grafana, web‑scraped PR metadata
Difficulty	High
Monetization	Revenue-ready: $5/mo per organization for premium analytics

Notes

“Seeing the curve drop after a ban would be satisfying.” – community observation, HN thread.
Provides material for academic study of AI adoption patterns in FOSS ecosystems.

Concise PR Gatekeeper

Summary

Flags or automatically closes pull requests that exceed verbosity thresholds typical of AI‑generated “wall‑of‑text” submissions.
Enforces a modest description length and file‑count limit for new contributors, steering them toward focused, human‑readable changes.

Details

Key	Value
Target Audience	Maintainers of high‑traffic repositories (e.g., Godot, Zig)
Core Feature	PR length audit, auto‑reject with templated message
Tech Stack	Node.js, GitHub App, regex scoring, webhook integration
Difficulty	Low
Monetization	Hobby

Notes

“I close 30 % of incoming PRs because they’re walls of text; this would cut that in half.” – reviewer, HN discussion.
May provoke debate over fairness versus quality control in open‑source contribution pipelines.

AI Contributor Audit Studio

Summary

Requires contributors to answer a short questionnaire proving they understand their submitted code, generating a signed attestation attached to the PR.
Shifts the verification burden onto the author, making it easier for reviewers to trust human intent.

Details

Key	Value
Target Audience	Open‑source projects with strict human‑review policies
Core Feature	Prompt‑based self‑explanation generation, attestation UI for maintainers
Tech Stack	Rust backend, React front‑end, OAuth login for contributor identity
Difficulty	Medium
Monetization	Revenue-ready: $0.01 per attestation (optional donation)

Notes

“It shifts the burden to the author to show they actually read the diff.” – community suggestion, HN thread.
Could lead to broader conversation about incentivizing genuine contribution vs. superficial PR farming.

No‑AI‑Friendly Repository Index

Summary

Central catalog of projects that explicitly ban AI‑generated contributions, searchable by license, community size, or policy type.
Offers a badge and API for projects to signal their human‑only contribution stance.

Details

Key	Value
Target Audience	Developers seeking where to submit contributions; maintainers wanting to advertise policies
Core Feature	Searchable index, contribution‑policy metadata, community voting on policy strictness
Tech Stack	PostgreSQL, Django, Docker, public REST API
Difficulty	Medium
Monetization	Hobby

Notes

“I’d love to know which projects respect human craftsmanship before I invest time.” – potential contributor, HN discussion.
May fuel debate on how policy influences recruitment, code quality, and project identity.