Meeting minutes


Action items



Meeting location

Hotel most of us booked

Wednesday June 30


We'll go for dinner and this is a perfect occasion for other people to join informally to meet up.  

We meet up in Hotel Steigenberger between 19:00 and 19:30. At 19:30 we leave for the restaurant.

Please put your name here or send me (t o m a t alfresco d-o-t com) a mail if you want to join so that we can book a restaurant.

Thursday July 1st

Meeting schedule



9:00 - 10:00


10:00 - 10:30

Round of introductions.  Every company gets 6 minutes :-)

10:30 - 12:00

Validate architecture and look for aspects of the architecture that need further discussion/decisions.

  • Where Activiti came from.  What made jBPM successfull?   
    • We're sensitive on practical api
    • Collaboration aspect: expect renamings if you add api
    • What do we keep and what do we want to improve?
  • PVM architecture overview and core execution algorithm
  • PVM persistence
    • Can we decide on myBatis?

12:00 - 13:30


14:00 - 14:30

Timeline overview

13:30 - 18:00

Scope discussions.  List all the targeted features and indicate if they are 

  • 5.0 : Minimal scope
  • 5.x : Optional
  • Nice ideas

18:00 - ...

Teambuilding ;-)


We'll probably meet up around 18:30 somewhere in the center of Stuttgart.  Later will list the exact time and date.  List your name if you want to join.

Friday July 2nd

Meeting schedule



9:00 - 11:00

Concrete roadmap

11:00 - 12:00

Collaboration practices 

  • Infrastructure: (IRC, mailing lists, forums, jira, roadmap, glossary pvm/bpmn,...)
  • Run update and check before commit
  • Decision process
  • Sprint layout

12:00 - 13:30


13:30 - 15:00

Delayed topics

16:00 - 17:00

Roundup + group hug

Other potential topics



Configuration, initialization of process engines

Currently there is the strategy of setup building jars containing configurations. There is the programmatic creation of a process engine, there is the ProcessEngines registry and the servlet for automatic initialization.

We should establish a common strategy on how we deal with configuration files and initialization.

Following aspects should be considered and as much as possible unified:

Registry pattern
Test APIs

Should the test utilities and APIs be split off into a separate project? Would mean only unit tests in activiti-engine (but that's the way it is now anyway).

DB persistence

Current architecture


Is the current architecture OK for 5.0?

BPMN compatibility

Biggest question around BPMN is the suitability for developers. jPDL was much more readable. Will BPMN shortcut suffice? Will just have to take the pain of a verbose language? Or do we need to go for usability, compactness and readability without compromises.

How do we make it easy for users to work with all these namespaces (if we decide to put custom conveniences in namespaces)

Is there a clear scope we can target? Simple or descriptive conformance? Maybe Bernd could prepare this topic as he's closest to the spec. But most important is not the knowledge of the actual conformance, but arguments that give us guidance on what kind of conformance we target and how strict we'll be. The alternative is that we define our own subset of what we think is useful.

Database upgrades. Automatic QA for upgrade.

Cloud support

The biggest question here is: How will we align the roadmap of researching the cloud solution with the roadmap towards 5.0GA in november?

Query APIs

An important aspect of cloud is the query API. We currently plan to build out the query API similar to jBPM 4. For example


But that might be hard to implement on cloud persistence. Maybe there are solutions. MapReduce?

Delegatable tasks

Define PVM event (api)/history event/event (listeners) and map it to BPMN

Other topics