Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

discussion: guidelines for AI-assisted contributions

Abierto
  • ¿Algo no está bien?
#7 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Área
documentation

Línea de trabajo

Empieza leyendo las políticas enlazadas de Bytecode Alliance, LLVM y Fedora; después, compara las ubicaciones propuestas para CONTRIBUTING, AI Policy y AGENTS.md descritas en el issue. Se considera completado cuando el proyecto haya acordado el alcance y las expectativas de la política para el código, la documentación, las revisiones, la divulgación, la autoría y la rendición de cuentas, y se hayan identificado los archivos de documentación de destino.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

AI-assisted contributions (code, docs, reviews) are becoming common in our project on either documentation or coding. Right now we don't have any written guidance on this, so contributors have to guess what's expected.

This issue is to discuss what the policy should cover. Some questions need to be discussed:

  • Should PRs note when they are substantially AI-assisted (e.g., a line in the PR description or a Co-Authored-By / Assisted-by trailer)?
  • Regardless of tooling, the contributor submitting a PR is responsible for understanding and testing it. Do we want to state this explicitly in CONTRIBUTING or in AI Policy file?
  • Should reviewers treat AI-assisted PRs any differently, or is our normal review bar sufficient?
  • Does the same guidance apply to code, docs, and issue/PR discussions, or do we only care about code?

My personal leaning on the questions above

  • Any tools are fine, but human-in-the-loop is required. Contributors must read and review all AI-generated code or text themselves before asking others to review it.
  • Disclosure is voluntary but AI must not be listed in Co-authored-by. Only humans can be authors and take on the accountability that comes with authorship.
  • The core principle is preventing "extractive contributions": a contribution should be worth more to the project than the maintainer time it takes to review it. Sending unreviewed LLM output to maintainers extracts their time.
  • Copyright responsibility stays with the contributor: regenerating copyrighted material with an AI tool does not remove the copyright.
  • Same guidance applies to all parts.

We could follow the structure used by the Bytecode Alliance wasmtime:

  • An org-level policy file, AI_TOOL_POLICY.md, lives in their governance repo. For us that would be this community repo.
  • Each active project repo carries a thin AGENTS.md with a few hard rules for AI tools themselves (no auto-opened PRs, no auto-comments/reviews, no AI in Co-authored-by), each pointing back to the org-level policy.

Their policy is itself a lightly adapted copy of the LLVM AI Tool Use Policy, which in turn is based on the Fedora Council's policy on AI-assisted contributions, and all under permissive licenses. We can adapt this and add attribution.

Lenguaje dominante
Sin datos de lenguaje
Estrellas
0
Forks
0
Merge medio
11 d 18 h
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.