[Bf-committers] DOF camera parameters.- Alexander
car
bf-committers@blender.org
Thu, 10 Jun 2004 11:23:05 -0400
> If you have a CVS tree of your own, you could try merging in the
> latest Blender CVS code. This is what the Tuhopuu people do to keep
> up-to-date with the main BF-Blender tree. I've done it once, with,
> errmm... "mixed" success, to keep the Aqsis tree up-to-date with
> Tuhopuu.
> There are instructions in the CVS manual. Online here:
> https://www.cvshome.org/docs/manual/cvs-1.11.16/cvs_13.html#SEC103
> Chris Want, from Tuhopuu, pointed me at those when I faced the problem
> initially.
>
> As far as the question of feature inclusions go, here's my 2 cents:
> Basically, every GPL project has maintaners and committers, whose job
> is to direct the course of software, and, in some cases, decide
> against inclusions of particular code/features. Generally, these
> people have the roles they do because of their experience, or simply
> because they were willing to do the work when others weren't. In
> general, I think it's always best to respect the opinion of these
> people. This is not un-democratic, because the GPL license allows
> *anyone* to start a fork if they thought that the majority would
> follow their lead. However, to retain their community of developers
> and users, the project maintainers must be sensitive to the
> requirements.
> In this area, I think Ton has done an incredible job - certainly among
> the best of any Open Source identity I've ever come across. If he
> opposes a particular feature, the first question that comes into my
> mind is: why? I'm sure there must be a reason; and I'm guessing Ton
> will have a reasonable answer to that question that has the
> community's best interests at heart.
>
Very True, But you are going to have a new problem to, When it comes
time for it to be ported to BF that will become a new problem as the
bases tend to change somewhat.
No matter, it a whiles off till then.