[Bf-committers] Understanding the dev process
j.bakker at atmind.nl
Fri Jul 5 16:32:36 CEST 2019
Currently the process feel like some form of Kanban, that works well when
you have a lot of things to do, with limited number of developers. This
needs more management to get new developers involved and to make sure that
the right stuff is being done.
We have done some stuff to attrack new developers (list of small fixes,
community activities), it is more effective than what we had before, the
last year has proven that. The next step would be to keep this going on,
but also find a way how to keep new developers interested. I mean how many
developers want to do more, but are not able to get to the next level
As I feel it is that the full process feels a bit disconnected. If you look
at the full process for a project what at least take design,
implementation, patch review, initial support, documentation, release note.
The later of these tasks are not always connected with the first part of
My personal goal is to add more feedback loops and team work in the
projects I am a member of. This makes doing projects more interesting
On Thu, Jul 4, 2019 at 3:38 PM Nathan Letwory <jesterking at letwory.net>
> Hey all,
> As you all may know by now I've been asked to help coordinate and manage
> the Blender development.
> To get a better understanding of what these days is going on, and to
> prevent me from just acting through my personal preferences, I'd like to
> hear from the blender developer community how they see the current dev
> I'm most interested in finding out how devs perceive the process: what goes
> well, and even more so what causes trouble.
> An open discussion by anyone on this topic is of course welcome, but I'd
> like (and also a bit expect) input at least from those who are listed on
> the Modules  page.
> /Nathan 'jesterKing' Letwory
>  https://wiki.blender.org/wiki/Modules
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers