[Bf-committers] Lack of coordination and communication in Blender development
sergey.vfx at gmail.com
Sun Aug 16 17:05:25 CEST 2015
Kai, its really early days of 2.8 and currently we are collecting all those
design tasks which are feasible to solve during this project. We are also
all aware of issues you had with fracture modifier and will try to end up
with a flexible enough system to support your usecase. But it will also
help if fracture modifier developers will start working on a proposals of
how they see this project to happen in a scope which wouldn't violate
blender core. I know its difficult at this early stage but with
communication with other developers its totally doable.
Mike, I can't think of a design decision being made without mentioning it
in the meeting minutes (which are also shared via blendernetwork).
Proposals are to be put to wiki and mailed here in the list. Design docs
belongs to wiki, but for bigger projects it worth writing a dedicated blog
post at code.blender.org.
On Aug 15, 2015 16:35, "Mike Erwin" <significant.bit at gmail.com> wrote:
> Kai makes a good point.
> Sometimes I'll see something new and think "cool, but why is today the
> first time I'm hearing about this?!?" So I understand the impression of
> things happening behind closed doors. When is the best time to share an
> idea though? The second it's thought up or after working out the details?
> At this point why not code it up to test how well the idea works? And once
> the code is done, why bother presenting it as an "idea" or "design"? It
> works, it's done!
> >From the inside this seems like getting things done. From the outside it
> seems like working behind closed doors. I'm really bad about this myself :)
> but catch myself getting annoyed when other people do the exact same
> things. I don't think anyone is *hiding* their work though. Just following
> habits of not being actively open.
> Even if an area will be "owned" by one or a few people, it's important to
> have designs out in the open so everyone knows what's going on. Earlier is
> better. Lots of comments surrounding any design will be nonsense -- or
> of wildly varying levels of quality" as Martijn put it more politely. But
> I'd rather sift through noise than seem to be working in secret. And it's
> also important to document things that were *considered* but not chosen as
> part of the final design. Broader documentation of decision-making
> processes will reduce surprises and hopefully eliminate the impression that
> core developers ignore the needs and ideas of others.
> What is the proper forum for proposals and other design docs?
> code.blender.org? wiki pages for work in progress? I see posts on
> blenderartists and Twitter and G+, which seem "unofficial" but also reach
> an audience that might not follow the mailing lists or hang out on IRC.
> Great, now I suddenly have the urge to document my own stuff.
> Mike Erwin
> musician, naturalist, pixel pusher, hacker extraordinaire
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers