Hi folks,

I would like to propose that Velocity step out from the Jakarta
umbrella and become a TLP at Apache.  Here's why:

Jakarta is being pushed toward a focus on singular components.  It is
still my opinion that the core of Velocity fits this focus rather
well.  However, there has been over the years a (slowly) growing
community of other Velocity projects.  Some of these are very
component-ish (like DVSL), but others are not (like VelocityView).
So, while it is entirely feasible that Velocity could remain at home
in Jakarta, it is not so for much of VelocityTools.  Also, there are
other Velocity based projects outside of the ASF (such as the Click
framework) that are unlikely to be welcome to join the larger Velocity
community so long as it is under the Jakarta umbrella and unlikely to
want to be there.

In light of all this, I feel that Velocity and its larger community
will find greater benefit from each other's company and mutual
interest than we would as a restricted part of the very disparate and
rather segregated Jakarta "community."  As a TLP, Velocity should be
free to invite other Velocity-based projects to come alongside and
continue to develop not-really-component-ish things like the bulk of
the VelocityTools project.

That said, i'd love to hear what the rest of you think about this.  :)
Votes and feedback on this proposal are quite welcome from both
committers and non-committers!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to