RFC: Policy on bot/vibe-coded/stochastic/tainted/non-human contributions

Open
#103 54 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Domain
documentation

Research direction

Start by reading the RFC body and the existing contributing.md policy it references, then review the 54-comment discussion for the current points of disagreement. Done means the community has reached a decision and the agreed AI policy is documented for application across gbdev projects.

Written by the indexing model from the issue text.

Description

help wanted question

Edit by @avivace

This is an open RFC on adopting an AI policy across gbdev projects. We'd like to hear from the community.

This covers all types of interactions (code, docs, issues, reviews, discussions) and all levels of AI involvement - from fully bot-generated contributions, to AI-assisted work, to using LLMs/copilots as a drafting or editing aid. If you have thoughts on where the line should be drawn (or whether there should be one), please share them.

Original body follows:

// I'm putting this in this repo because it's the de facto gbdev "policy" repo -- in essence: because contributing.md applies to all gbdev repos/projects.
// I want to spend zero time having to think about this, let alone hours burning out trying to (re)write words that people (mis)understand. I'm willing to argue about it if anything reasonable comes up, but I'm not (going to survive) writing an essay upfront.

Why have a policy?
It sends a message about the type of community this is. Sending a clear message enables people to judge if this is a safe place that welcomes them or not. Bots will, of course, be unaffected.

My idea of an acceptable policy would cover the following points:

  • No use of LLMs/chatbots/"AI" to contribute to (interact with) the community is acceptable.
  • Communities are humans.
  • This is a community.

I'm willing to negotiate on this, but not really.

gbdev/gb-asm-tutorial#187, gbdev/gb-asm-tutorial#188
Have a look at how productive these guys are on their hundreds of forks they just started contributing to in seconds. Amazing!

Dominant language
Assembly
Stars
34
Forks
16
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gbdev/gbdev.github.io

All issues in gbdev/gbdev.github.io

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.