User:Dfelinto/Drafts/DevelopmentStructure

Development Structure

"Everyone should have all the information they need to work." - Ton Roosendaal, October 2019

The modules should be empowered, the design steps should be formalized and reinforced, and we should have a clear definition of everyone's roles and its expectations for the entire team, as well as contributors.

Blender-Development-Structure.png


There is a static part of the Blender development structure that is responsible for everyday patch review, roadmaps, bug fix and general maintenance.

Another side of the development team is responsible for new projects and research & development.

When module owners are assigned as a project leader, they should stay away from the regular maintenance task as much as possible. This allows for housekeeping, as well as the vision being passed "down the line".