Communicating is super important!
Blender is a community project. It relies on its users to support each other, spread news, and continuously improve Blender.
With millions of downloads, Blender has relatively few contributors. It is essential that information flows in both directions between users and developers in a useful manner.
General guidelines for communication have been outlined in our Code of Conduct.
The main development discussion mailing list is:
If none of the lists below seem to fit your question, this is the one you want to mail. You can find information on how to subscribe and browse the archives through the bf-committers list info page.
For reading only:
Documentation, Translation and Education:
- bf-docboard: About this wiki and the blender.org manual project
- bf-translations-dev: Blender UI translations
Blender developer Discourse: similar to mailing lists, but in modern forum format. For discussion about Blender development.
Most developers are active on the #blender-coders channel on blender.chat.
Decisions and Planning
Blender's code is organized in modules; libraries or directories with files sharing a certain functionality. For each module, the module owners are responsible for maintenance and bug fixes. They also define - together with their team - roadmaps or todos for the module, aligned with the overall release cycles and roadmaps.
- Blender Modules - who to contact when you have questions or patches for a specific area within the Blender code base.
Weekly Developer Meetings
The Blender developer community has meetings every Monday in #blender-coders on blender.chat, with an alternating schedule to allow developers from both America and Australia/Asia to attend. The topic in the channel has the date of the next meeting.
The schedule switches every other week between:
- 10:00 Central European summer time / 01:00 Los Angeles time / 08:00 UTC
- 18:00 Central European summer time / 09:00 Los Angeles time / 16:00 UTC
Note that the times change for UTC time during winter, when the times are 10:00 CET and 18:00 CET (note contrast with CEST). This means 09:00 UTC and 17:00 UTC during winter.
Our bug tracker and development infrastructure are hosted at developer.blender.org.
- Bug Reports can be filed there, for Blender, Add-ons and infrastructure projects.
- Patches that add or improve code can be submitted for review.
User Feedback and Requests
Blender has magnitudes of more users than people who are involved with making it. That makes handling user feedback and feature requests - or even tracking them sanely - nearly impossible.
Instead we try to organize ourselves in ways that development and users can cooperate closely. For each module in Blender, there's a small and competent team working on it - including users helping out. You can find this information listed above. Feel welcome to use our channels and get involved with making Blender better.
As alternatives we like to mention:
- Add ideas on the community-run Right-Click Select website
- User feedback forum for feedback on ongoing development
- Make sure your proposal is documented and published in public. Post this on the appropriate public lists, or on public forums (such as Blenderartists.org). It doesn't really matter where, a lot of users out there probably can tell you whether it's already there, already planned, a great new idea, or simply not possible.
- There are also companies and freelancers you can hire via Blender Network.