Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-18 Thread Ton Roosendaal
Hi, Luckily the "after the 2.6 series" will take a while ;) But seriously, any future we can think of will only work if you can make it work in a natural way. Defining a vision (like the bi-monthly develop focus) is a nice one, but you won't get much volunteers inspired for it. And not with

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-18 Thread Charles Wardlaw
> > regarding Charles's idea about a wiki feature/comp, there has been > http://wiki.blender.org/index.php/Dev:Ref/Competitor_Analysis > for years, already categorized. perhaps we could take an item, > update it for the competitors in that space, and go from there. > That's not a bad idea, althoug

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-18 Thread Roger Wickes
From: Charles Wardlaw To: bf-blender developers Sent: Fri, December 18, 2009 10:01:44 AM Subject: Re: [Bf-committers] Development plan proposal for after the 2.6 series move forwards. Perhaps that conversation could move to a wiki or a google wave thread if the mailing list isn't the pr

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-18 Thread Charles Wardlaw
> > > Bringing some area to be industry leader in 1 or 2 months is > > absolutely impossible, no matter how many developers work on it. > > There are a few areas that could be. UV tools are extremely close for > instance, we are behind headus but not by a large amount. The > modeling tools could

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-18 Thread Raul Fernandez Hernandez
Hi > I think this plan could work, but only if the BF invested funds in >paying relevant developers for the duration of each cycle. I think >this is effectively what the open movie projects accomplish, without >the requirement that the new features must be tested in production of > >Joe Why n

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-18 Thread Tom M
Hi all thanks for the comments, I appear to have not communicated clearly, since there is widespread misunderstanding of what I was proposing. Brecht, > Having all the developers > working on one area would be already very problematic in one company, > but distributed over the internet this just

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-18 Thread Brecht Van Lommel
Hi Tom, Bringing some area to be industry leader in 1 or 2 months is absolutely impossible, no matter how many developers work on it. Development speed does not even remotely scale linearly by the number of concurrent developers working on it. Having all the developers working on one area would be

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-17 Thread joe
I think this plan could work, but only if the BF invested funds in paying relevant developers for the duration of each cycle. I think this is effectively what the open movie projects accomplish, without the requirement that the new features must be tested in production of a short film. Joe On Th

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-17 Thread Martin Poirier
--- On Thu, 12/17/09, Goat Man wrote: > Python itself needs to go somewhere > on that long list, not just something > that will "probably" be used in all those things.  > Blender still can not be > controlled well from larger pipelines because it can not be > automatically > launched and passed

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-17 Thread Goat Man
Python itself needs to go somewhere on that long list, not just something that will "probably" be used in all those things. Blender still can not be controlled well from larger pipelines because it can not be automatically launched and passed a python script that takes over - currently one big lim

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-17 Thread Aurel W.
Hi, if one distinctive part needs to be exceedingly improved, it makes sense to focus on it. However, if so many different things need work anyway, it's more efficient not to focus too much. Otherwise too many developers are working on the same thing, which causes overhead, confusing and makes dec

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-17 Thread Kent Mein
In reply to Tom M (letter...@gmail.com): Hi Tom, It's a good idea, but I'm afraid it will chase away developers if we lock things down too much. Most of the people work on what they want to work on. What your suggesting sounds an awful lot like hey lets make the developers focus on things we wa

Re: [Bf-committers] Development plan proposal for after the 2.6 series

2009-12-17 Thread Raul Fernandez Hernandez
> Hi all, > > I'd like to propose that after the 2.6 series completes that we start > scheduling patch review and perhaps have a development focus. > > My thoughts were to have a 1 or 2 month rotating cycle where we focus > on one area of Blender and try and bring that area to be the industry > l

[Bf-committers] Development plan proposal for after the 2.6 series

2009-12-17 Thread Tom M
Hi all, I'd like to propose that after the 2.6 series completes that we start scheduling patch review and perhaps have a development focus. My thoughts were to have a 1 or 2 month rotating cycle where we focus on one area of Blender and try and bring that area to be the industry leader in terms