Module Roles

This page explains the roles and responsibilities of contributors that are part of the various Blender Modules.

BF Blender

This is the Blender Foundation tree, from which official releases are made. Decisions are generally made in consensus by all BF Blender project members or by module owners. However if no consensus can be found the project admins will make the decision.

Project Admins

  • Bastien Montagne
  • Brecht Van Lommel (Coordinator)
  • Campbell Barton
  • Dalai Felinto
  • Sergey Sharybin



Active developers who frequently contribute to parts of Blender can become module owners. Ownership means you have a lot of freedom to work on the modules, decide on implementation and design issues here, and approve or reject patches and feature requests. This based on aligning well with Blender's general design decisions, release planning and roadmap.

Owners should keep track of other module teams to make sure overlapping work is being agreed on, and make sure their own module teams agree on work that's being done.


  • Be available for regular bug fixing in the module (at least for every release)
  • Make sure the module is well tested for a release
  • Organize review of patches as submitted for the module
  • Ensure new features or changes in modules are well documented in wiki.

Project admins approve module ownership.


Module members and owners mostly self organize. When needed, the module coordinator acts as the main point of contact and coordinates efforts.


Module developers design and implement features, review contributions and listen to user feedback, as well as handle bugs reports.

Anyone actively contributing code to a module can be listed as a developer, there is no formal process to join.

Whenever possible, developers are available for bug fixing, reviews and documentation. However, it's more of a loose commitment, based on 'being involved' more than on 'being available'.

User Members

This special module membership is for non-developers, typically artists who will act in the stakeholder role of the module. The entire module team, including the owners, ensure the stakeholders endorse and agree with features and development plans.

User members are appointed by invitation by the module owners.


  • Make sure the module is well tested for a release
  • Help documenting and with release logs
  • Feedback on public forums or mailing lists on feature requests.


When contributing code, module owners can be contacted for development questions and assigned for code reviews.

Developers committing code to areas of which they are not the owner should get a greenlight from the relevant module owners first. Any areas not clearly covered by a module are handled by the project admins.

Once a developer has contributed good quality code, they can be given access to commit directly to the Blender repository. Code review for new features and bigger changes is still done by module owners, while smaller changes can be committed directly.