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

catalog: a terminal status for per-item aggregators so 40 entries do not sit in `needs-review` forever

Abierto
#99 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript

Línea de trabajo

Start with docs/review-ledger.md and the README status table, then find the catalog validator, status filters, and card and entry page copy. Review the remaining needs-review aggregators and add a Notes line for each explaining how to check its per-file licence. Done means open questions remain needs-review, per-item licences have a clear badge, and the README explains all three states.

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

Descripción

enhancement priority: medium

Why it matters
40 entries are needs-review, and the 2026-10-04 ledger says most of the remaining ones "are mostly per-file aggregators, or questions only the publisher can answer" (Freesound, OpenGameArt, Sketchfab, Lospec, Poly Pizza, NASA Image Library...). They will never become active because their licence genuinely varies per file. Leaving them as needs-review makes the status meaningless as a work queue, hides them behind the default filter, and makes 46% of the video category look unfinished.

Evidence (data audit 2026-10-21)

  • status: active 372, needs-review 40 (audio 8, 3d 7, tools 6, video 6 of 13), deprecated 2.
  • Their licences: custom 17, varies 16, unknown 3. commercial: varies is already a value (16 entries).
  • docs/review-ledger.md, 2026-10-04 section, "Still needs-review" paragraph.

Suggested approach
Add a status such as per-item (licence settled as "varies by file; check each download"), with its own badge and copy on the card and entry page, and keep needs-review strictly for entries with an open question. Move the aggregator entries over in one sweep, each with a Notes line on how to read the per-file licence on that site. Update the validator, the filters, docs/, and the README status table.

Done when
needs-review contains only entries with a stated open question, aggregators show a clear "varies per file" badge, and the status table in the README explains the three states.

Lenguaje dominante
JavaScript
Estrellas
58
Forks
15
Merge medio
18 h 42 min
PR fusionados (30 d)
11

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 TMHSDigital/Free-Game-Dev-Assets

Todos los issues de TMHSDigital/Free-Game-Dev-Assets

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.