New or aspiring developers can find more detailed information on the new developer info page.
Special interest mailing lists are:
- bf-blender-cvs: All Blender source commit logs
- bf-python: Python API conformance and development
- bf-extensions-cvs: Extensions (Python Add-on) commit log
- bf-cycles: Cycles render engine
- bf-vfx: Visual effects development, motion tracking
- bf-translations-dev: Blender UI translations
- robotics: Robtics, special interest group
- soc-2012-dev: Google Summer of Code 2012 developers
The developers are active on the #blendercoders channel on the freenode.net IRC network.
The Blender developer community has meetings every Sunday in the #blendercoders channel starting at 16h Central European time (in winter and summer).
Meeting reports are sent to bf-committers. Most of the time the agenda is decided at the start of the meeting, so if you have something that needs to be discussed, be there in time.
Our trackers and project site are hosted at projects.blender.org.
- Bug Tracker
- Patch Tracker
- Patches can be submitted for review to the patch tracker. It helps to notify the developers on both the mailing list and in the IRC channel #blendercoders on Freenode.net.
- To Do Tracker
- While we try to address all the issues reported to us, there are cases that prove to be very hard to fix for various reasons. When after a while a bug is still deemed hard to fix, it is often moved to the todo tracker or it is kept in the bug tracker, but closed and marked as Todo. This makes it easier to search for these bugs later.
- For Blender 2.5 development we have also a list of todo items in our wiki. These items are mostly those that are also closed and marked Todo in the Blender 2.5 tracker.
This wiki is mainly for projects that are actually worked on (implementationally). If you have an idea, you can go here:
See the Module Owner list for who to contact when you have questions or patches for a specific area within the Blender code base.