Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

catalog: three active entries carry `commercial: false` against the headline promise, and two of them have Evidence that does not establish the value

Geschlossen
  • Stimmt etwas nicht?
#141 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
content, documentation

Rechercherichtung

Start by reviewing CONTRIBUTING and the cited catalog entries: catalog/3d/freepbr.md, catalog/2d/penzilla.md, and catalog/tools/gaea.md. Then inspect the validator and the site search and entry page to understand how catalog status and commercial terms are represented. Decide and document the policy for non-commercial entries, resolve the cited evidence and data defects, and add the proposed validation rule; done means the policy is documented and the listed defects and unsupported values are addressed.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

correction priority: medium

Why it matters

The repo description and README promise "free, commercially usable" sources. Three active entries say the opposite, and on the site they are only distinguished by a small "non-commercial" flag among the search results. For two of them the Evidence section does not support the recorded value, which is exactly the situation needs-review exists for.

Evidence (at 69387df)

entry commercial what the Evidence says
catalog/3d/freepbr.md false consistent: "As long as you don't use these commercially" (2026-08-24)
catalog/2d/penzilla.md false, attribution_required true contradictory: pack pages say "Royalty free and commercial use" (2026-08-24); the licence PDF quoted on 2026-10-04 is a purchase licence; which applies to the free packs is not resolved
catalog/tools/gaea.md false the entry itself says "Prior commercial: false in this catalog was not re-established from a live quote on 2026-08-24"

Small data defects seen in the same pass, worth fixing together:

  • catalog/animation/blender-ellie-poses.md and catalog/characters/blender-human-base-meshes.md share the same url (the blender.org demo-files page); every other URL in the catalog is unique.
  • catalog/animation/cmu-mocap.md and catalog/characters/makehuman.md use http:// URLs.
  • catalog/audio/mixkit-sfx.md has verified: 2026-09-23 while its newest Evidence line is dated 2026-09-24 (the check only rejects the opposite direction).
  • Eight active entries have an Evidence section under 80 characters (3d/3dmodelscc0-* x3, 3d/the-base-mesh.md, audio/kenney-interface-sounds.md, audio/kenney-sci-fi-sounds.md, animation/cmu-mocap.md, tools/google-draco.md).

Suggested approach

Decide the policy once: either commercial: false entries are out of scope (deprecate FreePBR with a pointer to its paid tier, or keep it only as a "free tier is non-commercial" note on the README scope table), or they stay and the site shows a prominent "Not for commercial use" banner on the entry page and excludes them from the default search. Set Penzilla and Gaea to needs-review until a dated quote settles the value. Fix the small defects. Add a validator rule: status: active with commercial: false requires an Evidence line quoting the restriction.

Done when

No active entry has a commercial value its Evidence does not quote; the policy for non-commercial free tiers is written in CONTRIBUTING; the duplicate URL, the two http:// URLs and the mixkit date are fixed.

Vorherrschende Sprache
JavaScript
Sterne
58
Forks
15
Ø Merge
18 Std. 42 Min.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TMHSDigital/Free-Game-Dev-Assets

Alle Issues in TMHSDigital/Free-Game-Dev-Assets

Ähnliche Issues

Weitere Issues zu JavaScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.