KhronosGroup / KhronosGroup/glTF-Project-Explorer
Tracking the KTX 2.0 ecosystem
Open
- Dominant language
- TypeScript
- Stars
- 95
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
@weegeekps @javagl any thoughts on how we should do this?
E.g., new JSON for a standalone database of the KTX 2.0 ecosystem, just start simple with a new boolean field in the current project JSON, etc.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by reviewing the current project JSON and the registry's existing data flow, then clarify whether KTX 2.0 should use a standalone JSON database or a boolean field; done requires an agreed representation and tracking behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100