Henning P. Schmiedehausen wrote:
> "Will Glass-Husain" <[EMAIL PROTECTED]> writes:
> 
>> 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)
> 
> Yes. There might also be some discussion whether we will start new
> Velocity projects inside the TLP at all.
> 

I don't see any problem with that, as long as it's not unrelated, like
Maven was inside Turbine.

>> --> strong or growing community of its own
> 
> +1
> 
>> --> the integration of Velocity is a key part of the project
> 
> +1
> 
>> 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)
> 
> Not sure here.

Why?

> 
>> --> Port of Velocity to another platform?  (e.g. nVelocity)
> 
> That is the usual Language/Tool clash. If there were a (hypothetical)
> Apache .NET TLP, would nVelocity go there or to us?

Us.  I'd fight against a .NET TLP.  Putting that aside, we'd want
nVelocity to be in lock-step with us as much as possible, so things like
configuration files and templates were portable.

> 
>> --> Web framework closely tied to Velocity (Click, Turbine?)
> 
> Click: yes. Turbine: no. 
> 
> Reason: Click is built intimately around Velocity. Turbine just
> happens to treat Velocity as a first class citizen but there is no
> reason why you couldn't use any other templating solution or JSP with
> Turbine. And the templating is just a very small part of Turbine at
> all.
> 
>> Not saying all of the above are candidates.  But would they fit our
>> desired umbrella?
> 
> My € 0.02 :-)
> 
>       Best regards
>               Henning
> 


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

Reply via email to