[Bf-funboard] Policy

[James Kaufeldt]

Groovy...

Whatever makes talking and criticism easier is a good thing - not afraid 
of that, it is rather welcome and in this context most necessary.

Concerning collection and reviewing, it would be facilitated by some 
sort of document template perhaps. It will be much easier to browse 
through a lot of suggestions from many different sources if they have a 
uniform layout and formatting. Boring and unimaginative perhaps, but 
helpful...

And no - we couldn't possibly order any coders to do anything at all 
really. But the way I see it, it's all about pay-off. Artists spend 
days, weeks, months finishing a piece of work - and they get their 
pay-off when other community members get to see and praise it... I 
figure that coders behave like that too. And if you know that you are 
implementing something than a lot of users want, in more or less the 
exact way that they requested, then you, as a coder, will get your 
pay-off when the community gets to use and praise your feature in the 
next Blender release. I suppose that's how something like this should be 
played. Psychology...

So - as far as databases and specifications go - we must create some 
place somewhere that provides idle coders with well-documented, 
annotated, quality-sealed suggestions/whitepapers/whatever that clearly 
states that "this is the way we want it, and here's the number of users 
who wants it, and here's why they want it"... blah blah... you get the 
idea.... :)

/Jamesk

Ton Roosendaal wrote:

> Hi,
>
> Sounds really OK!
> I would welcome more papers like this. It's easier to talk & 
> criticize  nicely written and illustrated examples. Hope you're not 
> afraid for  that. :)
>
> We also need time to think over how to collect this all, review it, 
> and  decide whether to further pass it on to the coders.
>
> Don't forget that it won't easily work, to order coders around to  
> implement stuff. However great & well documented proposals are, we 
> also  should look at what currently people (like to) work on, to 
> assist them  in working out the specs.
>
> On the other hand, having a good database with accepted features and  
> improvements will help getting focus, and might inspire coders to 
> pick  it up.
>
> -Ton-
>
> On Saturday, Jun 14, 2003, at 19:43 Europe/Amsterdam, James Kaufeldt  
> wrote:
>
>> This sounds very good to me.
>>
>> I've got some suggestions concerning careful improvements of some  
>> already available features - and I believe that sort of things are  
>> perhaps the best startingpoint, i.e. rather "small" improvements 
>> that  most coders could be willing to implement since it would not 
>> seem like  a very huge task.
>>
>> Since Blender currently has a pretty complete set of features, there  
>> is a lot of things that can be seriously improved simply by tweaking  
>> the current tools a bit.
>>
>> So, here's what I'm planning to do in a couple of days::..
>> Carefully write down the stuff I've been thinking about (one feature  
>> at a time) and illustrate this as much as I feel necessary to make 
>> my  points clear. Then I'll simply mail a link to the document in 
>> question  to this list. Very basic procedure, in other words.
>>
>> As time goes by, I will try to stick to one isolated feature (or  
>> mis-feature) at a time, just to get things focused.
>>
>> Sounds OK, yes? :)
>>
>> /Jamesk
>