Re: optimizing and extending for $

> I think it would be a shame if the community were turned
> into some kind of "how much would you pay for that?"
> situation.

It doesn't have to have that spirit.

Take tuning and scaling work, for example. Your architecture affords
much of that, including multiple paths of such work, aiming for
different work-loads.

How else are you going to order that work?

A nice property of the Wiki app is that it is an application with
immediate R&D applications. People planning services 1 year out,
wanting transactions in a scalable architecture with a tractable
programming model, have enough evidence that they can afford to commit
to a svn-backed wiki. And that creates (or at least can create)
demand for the right to shuffle the priority queue of performance
tuning work.

If that demand generates premium fees for the work, well, you can
always use that to support the community.

I think it would be ostrich-like to pretend that svn isn't already, in
some respects, a commercial project. A community of volunteers
shouldn't be corrupted or shut-out by money -- but they shouldn't be
immune to it, either.

-t

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 13 18:37:23 2002