A number of messages recently sparkled out on the Cocoon developers mailing lists about the future of Cocoon and possible future implementation that might use different approaches and paradigms. Is Cocoon too complex? What's the best diet for the large codebase we've got? Are we fed up with XML configurations all over the place? Should Cocoon aim to be a Ruby On Rails clone for the J2EE world? Or are we doing just fine as we are?
This BOF aims to be a F2F meeting between developers and users to better understand what are the best answers to such questions and to get a first-hand feeling of what's the general feeling about the next generation of Cocoon.