From BlenderWiki

Proposed Topics

- Bmesh development

- Job manager and threaded dev (Sorry, I proposed this thinking I was going to attend the meeting, unfortunately I won't be able to do so. Xat)

QA

Q: There are lots of warnings during compile, is cleaning them up a good starting project?

A: Yes, but be careful some are real bugs, explicit cast is not always the solution. Some implicit declarations can be easily fixed.

Q: How do you prevent two people working on the same bug?

A: If you are going to work on it for a while, leave a reply in the bug tracker. If it's easy to fix, just create a patch and link it in the tracker.

Q: Is it useful to discuss bugs with module owners, will they answer my questions?

A: Most definitely. If the bug requires a non-trivial amount of changes, it's better to discuss them first while you're making them, instead of waiting until the end when you think you are done. Time permitting, module owners are glad to answer code questions. Note that when asking for help locating a bug, that is sometimes 90% of the bug fixing work (it doesn't hurt to ask though).

Q: Aside from fixing bugs, what's a good way to familiarize yourself with the code?

A: You can look at small feature requests or trace an existing feature and do small changes here and there to understand the code flow.

Q: Is there documentation on how the UI works?

A: Some. http://wiki.blender.org/index.php/Dev:2.5/Source/UI/UIlayoutGuide http://www.blender.org/documentation/250PythonDoc/bpy.types.UILayout.html http://wiki.blender.org/index.php/Dev:2.5/Py/Scripts/Guidelines/Layouts http://wiki.blender.org/index.php/Dev:2.5/Source/UI/LayoutEngine You can also look at the UI scripts, like release/scripts/ui/properties_data_camera.py

Q: Any plans to switch to git or mercurial in the future?

A: Not soon.

Q: Is there any management of new features in the same way bugs are tracked(bug tracker)?

A: Not as organized, no. When features are large, they are often done in a branch (if they are not self contained) or in a set of patches until they are of acceptable quality and have been reviewed. Then they can be merged in trunk.

Q: Ok, so am I to understand that new features are our own decision, then presented to the developer in charge and aproved or rejected?

A: It helps if features are discussed first so there is less chance of us rejecting them after they are done. Developers may disagree, if so talking to the module owner is generally best since they will probably decide.

Q: As there is not an official list of new features are we to understand that the module owner is the beholder of the new features list of it's module?

A: Yes. Should be more organized eventually.

Q: Is there an up to date overview of the source folders?

A: http://wiki.blender.org/index.php/Dev:2.5/Doc/Blender_Source/Files_structure