What is project vitality?
In a recent Article to the Velocity Development list, the project was brandmarked as being “dead” because there seems to be not much traffic on the development list. What the original author is missing, however is the amount of traffic going through other channels like face-to-face meetings, water cooler discussions or just personal mail.
So what really describes “project vitality”? Is it the number of downloads happening? The number of hits to a web site? If a project really is stable because it is “good enough” and the active developers agree on being picky with patches, does this amount to failing project vitality?
After all, this is open source. And even under a very generous license. So if you need a feature that the code developers won’t implement, why not fork it off? Either internally or in public. Has happened before, will happen again.
apache open source velocity
Leave a Reply