Warp wrote:
> Thomas Willhalm <tho### [at] uni-konstanzde> wrote:
> 
>>If they were able to look at the
>>code and comment on it in an early stage of development, it should 
>>speed it up and lead to a better result.
> 
> 
>   Although this is probably true in some cases, it might also be a burden.
> Usually there are as many opinions as coders, and most people are quite
> eager to express them, no matter how useful/useless the opinion is.
> Trying to decipher all the text posted by people and getting the good
> opinions can be a big job... Who is going to do it?

Were the POV team to conduct their design discussions here, or in a 
newly created group, say, povray.developers, they would be perfectly 
able to ignore all traffic from non team members for as long as they 
liked. This would allow serious potential developers to get a feel for 
the new POVRay from the ground up and discuss it amongst themselves. 
Eventually, little by little the team members might peruse bits of the 
chatter and start to identify those people seeming to make worthwhile 
comment. From there the developer network can gradually expand. While 
not necessarily admitting more and more people to the core team itself, 
a broad base of committed developers could be established, thus allowing 
useful opinion to filter through without anyone in particular having to 
monitor all the traffic in the group full time.

Certainly, this is but one way of many that the POV Team might decide to 
go about migrating POV development more open model, but I dont see it as 
particularly problematic.

Post a reply to this message