Write pack review guidelines and a content policy

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
documentation

Línea de trabajo

Read CONTRIBUTING.md, docs/authoring/guide.md section 14, .github/PULL_REQUEST_TEMPLATE.md, packs/README.md, and CODE_OF_CONDUCT.md to align the review checklist and content policy with existing guidance. Draft the guidelines, link them from the specified files, update the template, record the structured content notes decision, and review the noir pack as a dry run; done when all acceptance criteria are met.

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

Descripción

area: community area: content priority: medium type: docs

Context

CONTRIBUTING.md lists the requirements and content guidelines for packs, and the authoring guide has a short review section. With generated pull requests and community proposals, reviewers need a repeatable checklist, and players and authors need a public content policy.

Scope

  • A reviewer checklist: lexvm check output and justified warnings; a human playthrough (who, device, time taken compared with the estimate); fairness (signposting, hints, responses to wrong attempts); text quality, length for phone screens and language correctness; license and provenance; historical accuracy and care with sensitive themes; the LLM playtest report when available.
  • A content policy that expands the content guidelines: what is accepted, how mature themes are disclosed to players, how to report a problem with a published pack (issue form) and how it is handled.
  • Decide whether mature themes need a structured field (for example contentNotes). That is a format change and gets its own ADR and issue if chosen.
  • Who may approve packs, and whether generated packs need two reviewers.
  • Align the content pack section of the pull request template.

Acceptance criteria

  • The guidelines are published and linked from CONTRIBUTING.md and packs/README.md.
  • The pull request template references the checklist.
  • The decision on structured content notes is recorded here.
  • The noir pack is reviewed against the checklist as a dry run.

References

  • CONTRIBUTING.md (Contributing a content pack, Review process)
  • docs/authoring/guide.md (section 14)
  • .github/PULL_REQUEST_TEMPLATE.md
  • packs/README.md
  • CODE_OF_CONDUCT.md
Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
1 h 24 min
PR fusionados (30 d)
5

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.

Más de nullthrone/lexvm

Todos los issues de nullthrone/lexvm

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.