KhronosGroup / KhronosGroup/glTF-Sample-Assets
Contribution reqs for this repo
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 108
- Avg merge
- 9h 39m
- Merged PRs (30d)
- 4
Description
I propose that all sample models satisfy these two reqs:
- If a model was created by some software tool (e.g., exporter or converter), it MUST contain
asset.generatorproperty with software's name and version. - Models must have
asset.copyrightproperty and/orREADME.mdfile with attributions and usage info.
CC @pjcozzi @bghgary @javagl
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's sample models and their README.md files, checking whether each model has the requested asset.generator metadata and attribution or usage information. Done means the sample assets consistently meet both contribution requirements and their documentation records the needed attributions.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100