[Suggestion] Store resources as submodule

[mattrossman]

Currently, setting up this project for local testing requires going into examples/_res and following the instructions to clone the resources repository. This can be problematic because:

• It's an extra step that can be overlooked for contributors
• The main branch of the repository is not guaranteed to be in sync with commits in this repository

This could be handled more elegantly with the resources repo as a Git submodule of this project.

This would mean that:

• Both repositories can be cloned in one step with git clone --recurse-submodules
• The appropriate commit from the resources repository will be versioned with this repository, so examples are guaranteed to work at any point in the project history.

[sketchpunk]

Thats something I was going to do in the next version of ossos, but hopefully have a set of models I made myself so I dont need to worry about copyrights & whatnot.

[trusktr]

I think you can still make it a submodule regardless (put a disclaimer in the README about copyrights if needed).

I made a PR for ossos_next:

• track resources as a git submodule #22

[trusktr]

The ossos_next branch now includes this.