I just wanted to give the Drools community a heads-up that the OSWorkflow community might be merging with us - not confirmed yet, but their project lead is keen. Our unified process work has matured and we are now very close to having a migration path for OSWorkflow users, who are keen to migrate to an actively maintained project. We've spoken to Diego Naya Lazo, the project lead and author of the OSWorkflow Book http://www.infoq.com/articles/naya-lazo-osworkflow, and he is liasing with his community to see if they are happy to move forward with this. The Drools process stuff also needs a name, as sub project - remember we have total unification and integration between the rules and process (see blog http://blog.athico.com/search/label/Rule%20Flow). So we can either go down generic routes - Drools Flow, Drools Rules, Drools Events. Or have something a bit more fun Drools Meastro, Drools X, Drools Fusion - X is there sa I don't have a fun name for the rule part. The idea is we will split the manual up into separate books that will start from the understanding of a person from that discipline, before jumping deep into how the techs are integrated. This is huge news and puts us firmly onto the path of a unified modelling environment, and hopefully an end to the days of having to choose and purchase separate and poorly integrated products for rules, processes and complex event processing. Mark