personal opinion: your code is bad!

Nobody has claimed this yet.

- hard to read
- use decoratior and metaclass
- 3 types of renderer, cairo/opengl/webgl, BaseRenderer/SubRenderer, Scene/Renderer/MObject, the author of the related code seems superior, using lots of fancy grammer, trying to seperate things up(trying to implement the Factory mode), but the truth is that there are lots of cross-reference. I just wonder how you gonna maintain this mess in the future.

- bad documentation
- many popular python library use auto-generated api reference, which is based on doc-comment of each functio/class/module, BUT your api reference seems to be handwitten line by line.
- tutorials are mostly based on example, there are no documentation introducing pipeline or best-practice or other deeper topic like how you implemented the gpu acceleration. Or maybe your team think the user just need to know how to write construct() function and put all the needed lego blocks(different MObject/Animation) together.

The result is: the potential developer/contributor interested in core function(like rendering process) may get blocked away. It seems that what contributors can do nowadays is some documentation-editing staff only, which souds sucks.

No files or tests are named. Start by reviewing the renderer layers (cairo/OpenGL/WebGL), Scene/Renderer/MObject relationships, and the API reference and tutorials; a contributor would first need to narrow this into a specific, agreed change before completion can be defined.

Written by the indexing model from the issue text.