On 11/30/05, Joe Germuska <[EMAIL PROTECTED]> wrote: > Presumably the Struts committers are going to heavily involved in the > compatibility, so if for no other reason, it will be easier for us to > work on that in an Apache.org repository.
I plan to be very heavily involved in compatiblity and migration issues. I'd like to start by updating the MailReader to use 1.3 best practices, and then rewrite that version for WebWork 2.2, using WebWork's best practices. Then, I'd like to migrate something with more teeth in it, like the iBATIS JPetShop, as it stands. Based on that experience, I would like to start working on migrations tools, strategies, and documentation that describe and assist moving existing Struts applications to WebWork, in the most painless way possible. I often work with large teams, and I am very aware of the importance of retaining skill sets and working code. Along the way, we are likely to identify some minor features that should be added to WebWork, perhaps as part of the WebWork 2.3 release. My suggestion would be to build the migration tools and documentation at Open Symphony. An important aspect of the migration is that when we are done, we are on the WebWork path and using WebWork best practices. The best place to discover WebWork best practices is by working with the WebWork community. I think it might assuage everyone's concerns if Struts committers were to work on WebWork-centric code at WebWork, before we bring the WebWork codebase through the incubator. As it stands, WebWork 2.2 is still beta, and I believe there are some things planned to be resovled in WebWork 2.3. Perhaps we can help with that too. I'd suggest we keep the WebWork project velocity up, work on the new tools as part of WebWork, and then bring the codebase through the incubator, when it's ready to go. I thnk If some of us spend more time at WebWork, we can build strong ties with the user community that will serve us well when the projects merge. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
