A key aspect of the merger is to create migration tools and bridge classes to make it very easy for teams to migrate existing Struts applications to WebWork. Perhaps it would make more sense to first create the migration layer as
as an extension to WebWork in the Open Symphony repository. Then, when the migration layer is ready, and the WebWork codebase is otherwise stable, we could bring the whole enchilada into the Struts repository (via the Incubator).

I do have the time and energy to kickstart the Struts/WebWork migration tools, but I don't want us to put WebWork "on hold" while we create the tools. Once we have a working migration layer, the move to Struts could happen very quickly.

To kick off the merger, I would suggest that we nominate Patrick and Jason as Struts committers, and Don and Ted as WebWork committers. Then, I'd like to create "mirror" versions of the Struts MailReader application, demonstrating best practices for Struts Action 1.3.0 and WebWork 2.2, and use the MailReader as the first migration test case.

More about MailReader ...

* http://opensource.atlassian.com/confluence/oss/x/PAM

-Ted.