>Not exactly sure what you're referring to here, but am guessing you mean would there be an offer for integrators/embedders to become committers? I personally think this makes sense for cases like Expresso.
My point was to show my support for Ted's proposal (of sorts) that projects like stxx and sslext become sub projects of the top-level Struts project.
I am not going to argue over the latter point. I could not agree more because projects like Stxx, Ssltext, and Workflow are ``true'' extensions of the Struts framework, because they could not logically exist without the Struts core itself. Whereas Expresso Framework existed long before Struts was a glint in Craig's eye.
From: Peter A. Pilgrim [mailto:[EMAIL PROTECTED]
==////==
==/////==
James Holmes wrote:
+++++1 on this!!
You hit the nail on the head. Many people (mostly managers) are reluctant to adopt Struts add-ons because they are not perceived as having the same "tried and true" stamp as the official Struts core. I think doing this would be a huge boon for Struts and would foster a lot of the development interest that's been talked about over the past couple of days.
Would the same principle work with people who have taken Struts and integrated or embedded as another framework? Having spent some type integrating 1.1 into Expresso Framework in 2002, in our case can we be classified as Struts extenders? Also some repository will not want to become a sub project of Struts because of logical sense, politics or legal entity status?
==////==
Regards
--
Peter Pilgrim
__ _____ _____ _____
/ //__ // ___// ___/ + Serverside Java
/ /___/ // /__ / /__ + Struts
/ // ___// ___// ___/ + Expresso Committer
__/ // /__ / /__ / /__ + Independent Contractor
/___//____//____//____/ + Intrinsic Motivation
On Line Resume
||
\\===> `` http://www.xenonsoft.demon.co.uk/no-it-striker.html ''--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
