- Campbell Barton
- Howard Trickey
Ways to make the code-base more approachable.
- High level documentation for BMesh & mesh editing how internals work & conventions.
- Review TODO’s & assign “Good First Issue”, (we should be more proactive mentoring these projects).
- Add-ons may be candidates for porting to C/C++.
Candidates for Sprints
As Blender is adopting “sprints”, smaller teams to focus on an area,
it is work considering modeling projects which could work as a sprint.
Performance: this is a big topic, see: T73360.
A sprint need not focus on all areas at once, it could be limited to a few we know will be valuable.
This area would likely benefit from more focused attention as well as user feedback.
This could use a workflow/usability pass.
Other topics we considered, although they are lower priority and don’t necessarily require being part of a sprint.
- There are currently many approved UV editing design tasks.
- Kerning, general improvements.
- Improved editing data structure.
- Support for custom-data layers.
Python API: Memory views on internal mesh data
This would allow for fast access to mesh data & may be useful for exporters,
anyone moving data between buffers.
Howard has been added as an owner of the modeling module,
this meeting was the first step to cover areas we think
we could focus on.
Currently there are no plans for when the next modeling meeting should be.