KhronosGroup / KhronosGroup/COLLADA2GLTF
Move GLTF library to its own repository?
Open
discussion
- Dominant language
- C++
- Stars
- 573
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
We're using the GLTF library in the Maya2glTF exporter. This library seems useful on its own, outside the scope of Collada2GLTF. Would moving the GLTF lib to a dedicated repository make sense?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue proposes moving the GLTF library used by the Maya2glTF exporter into a dedicated repository. Start by locating the GLTF library and its Maya2glTF and Collada2GLTF dependencies, then determine the repository boundaries and migration work required. Done would be an agreed decision and an implementable migration plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100