The rigging team of a short film I am rigging for has recently started to switch to mGear from an in house solution and are expecting to expand on mGear quite extensively over the coming year and a half or so. Most of the work will be in our own custom shifter component library + a library of tools those components and our custom steps can use, but we’ll also likely have improvements to upstream into mGear on occasion.
Because I’m so new to mGear, I have a couple questions about contributing and about the codebase.
- Currently with how development works I don’t see many large pull requests or features coming from the community, is that because the development style makes that impractical, or just that there’s more work to be done than people to do it?
- Is there a specific reason that none of the function parameters or returns in the codebase have set types? If I were to add such type hints to functions I wrote and wanted to merge into mainline mGear, would that be a problem? (I’ve been programming for a long time but started using Python after the switch to Python 3 was already widespread, so I’m not sure if this is for compatibility reasons or simply something that hasn’t been tackled yet)
Sorry if the answers to these are obvious and I just missed something.
All of my previous work has been with in-house rigging systems where I can just ask the team and sort of just change whatever is needed. Now that we’re using mGear I’d like to avoid trying to maintain an entire fork of it to make improvements, it’s much easier to work close to the upstream.
Thanks!