I totally agree with the described process.
Work on this should be started asap, i think it would be great to have
something to show by the time 4.0 is final.
I think i'll manage some spare time to help build this project, so count
me in.
Cheers
Hugo
Ron Piterman wrote:
Hi all,
There were many idees and proposals on that subjects in the long
thread above.
I would like to sugest the following:
To ground a work-group consisted of members of the tapestry community,
which will follow the idee and realize it.
I guess we have to make some kind of specification.
1)First define our goal,
2)then make a detailed technical specification as of how this would be
realized.
The Tapestry official developers would be encouraged to help, review
aso, specially, but not only, in milesstones, like before something is
being agreed upon.
After that, we can get to work and code and code and code...
I thing for specification definition a sourceforge project can give
the needed logistics of cvs, mailing lists, forum and so.
gmane.org offers mailing lists binding, and I would suggest naming the
lists in gmane under the official tapestry name
(gmane.comp.java.tapestry.component-repository ?) but that should
depend on the approval of howard.
Cheers,
Ron
---------------------------------------------------------------------
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]
