On 9/25/06, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
Starting a new thread...
First, project characteristics. I'd argue that a good project for the
TLP would have
--> developers who are part of the Velocity community (either active
on the mailing lists, and better yet those who have contributed
patches or bug reprots)
--> strong or growing community of its own
--> the integration of Velocity is a key part of the project
i liked the way Geir said it, that it should only work with Velocity
(i.e. not function w/o Velocity. If Velocity is optional or
tangential, then it is unlikely the projects community will be as
invested in Velocity's future.
Second... project content... What are some typical kinds of projects
that might fall under the TLP umbrella, and why?
--> A way of making Velocity accessible for new use? (e.g. Texen,
Anakia, DVSL, a JSP tag library based on Velocity expressions)
definitely. and on the subject, we probably should make Texen and
Anakia fully qualified subprojects, rather than bundle them with the
core.
--> Port of Velocity to another platform? (e.g. nVelocity)
that's a tricky one...
--> Web framework closely tied to Velocity (Click, Turbine?)
Velocity is optional for Turbine users, so i don't see that as a fit.
Not saying all of the above are candidates. But would they fit our
desired umbrella?
WILL
--
Forio Business Simulations
Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
