Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<h1><span style="color: rgb(0,51,102);"><strong>Meeting minutes</strong></span></h1>

<p><span style="color: rgb(0,0,0);">Joram?</span></p>

<h1><span style="color: rgb(0,51,102);"><strong>Action items</strong></span></h1>

<ul>
	<li>Create wiki page in which companies share their motivation to participate in Activiti</li>
</ul>

<h1>Attendees</h1>

<ul>
	<li>Tom Baeyens</li>
	<li>Joram Barrez</li>
	<li>David Syer</li>
	<li>Micha Kiener</li>
	<li>Agim Emruli</li>
	<li>Christian Stettler</li>
	<li>Stefan Niederhausen</li>
	<li>Bernd Ruecker</li>
	<li>Jacob Freund</li>
	<li>Esteban Robles</li>
	<li>Christian Mulder</li>
</ul>

<h1><span style="color: rgb(0,51,102);"><strong>Goals</strong></span></h1>

<ul>
	<li>Define the roadmap as concrete as possible</li>
	<li>Jumpstart collaboration process and practices</li>
</ul>

<h1>Meeting location</h1>

<p><a href="http://www.reinform.de/reinform/anfahrt/loeffel.php">http://www.reinform.de/reinform/anfahrt/loeffel.php</a></p>

<h1>Hotel most of us booked</h1>

<p>http://www.steigenberger.com/en/Stuttgart</p>

<h1>Wednesday June 30</h1>

<h3>Dinner</h3>

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

<p>We meet up in <a href="http://www.steigenberger.com/en/Stuttgart">Hotel Steigenberger</a> between 19:00 and 19:30. At 19:30 we leave for the restaurant.</p>

<p>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.</p>

<ul>
	<li>Tom Baeyens</li>
	<li>Joram Barrez</li>
	<li>David Syer</li>
	<li>Agim Emruli</li>
	<li>Christian Stettler</li>
</ul>

<h1>Thursday July 1st</h1>

<h3>Meeting schedule</h3>

<table class="confluenceTable"><tbody>
<tr>
<th class="confluenceTh"><p> Time </p></th>
<th class="confluenceTh"><p> Topic </p></th>
</tr>
<tr>
<td class="confluenceTd"><p> 9:00 - 10:00 </p></td>
<td class="confluenceTd"><p> Coffee </p></td>
</tr>
<tr>
<td class="confluenceTd"><p> 10:00 - 10:30 </p></td>
<td class="confluenceTd"><p> Round of introductions.  Every company gets 6 minutes :-) </p></td>
</tr>
<tr>
<td class="confluenceTd"><p> 10:30 - 12:00 </p></td>
<td class="confluenceTd"><p> Validate architecture and look for aspects of the architecture that need further discussion/decisions. <br class="atl-forced-newline" /></p>
<ul>
	<li>Where Activiti came from.  What made jBPM successfull?   
	<ul>
		<li>We're sensitive on practical api</li>
		<li>Collaboration aspect: expect renamings if you add api</li>
		<li>What do we keep and what do we want to improve?</li>
	</ul>
	</li>
	<li>PVM architecture overview and core execution algorithm</li>
	<li>PVM persistence
	<ul>
		<li>Can we decide on myBatis?</li>
	</ul>
	</li>
</ul>
</td>
</tr>
<tr>
<td class="confluenceTd"><p> 12:00 - 13:30 </p></td>
<td class="confluenceTd"><p> Lunch </p></td>
</tr>
<tr>
<td class="confluenceTd"><p> 14:00 - 14:30 </p></td>
<td class="confluenceTd"><p> Timeline overview </p></td>
</tr>
<tr>
<td class="confluenceTd"><p> 13:30 - 18:00 </p></td>
<td class="confluenceTd"><p> Scope discussions.  List all the targeted features and indicate if they are  <br class="atl-forced-newline" /></p>
<ul>
	<li>5.0 : Minimal scope</li>
	<li>5.x : Optional</li>
	<li>Nice ideas</li>
</ul>
</td>
</tr>
<tr>
<td class="confluenceTd"><p> 18:00 - ... </p></td>
<td class="confluenceTd"><p> Teambuilding ;-) </p></td>
</tr>
</tbody></table>

<h3>Dinner</h3>

<p><span style="color: rgb(0,0,0);">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.</span></p>

<h1><span style="color: rgb(0,51,102);"><strong>Friday July 2nd</strong></span></h1>

<h3><strong>Meeting schedule</strong></h3>

<h1>Other potential topics</h1>

<ul>
	<li>how much separate libraries would we target?  e.g. pvm, bpmn, task, identity, persistent-api</li>
	<li>how would the API look like?  now processEngine.getXxxxService()</li>
	<li>how would the docs be structured?</li>
	<li>how would the links between task completion and process continuation be implemented?</li>
	<li>how to offer the test helper method implementations?</li>
</ul>

<h6>Configuration, initialization of process engines</h6>

<p><span style="color: rgb(0,0,0);">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.</span></p>

<p><span style="color: rgb(0,0,0);">We should establish a common strategy on how we deal with configuration files and initialization.</span></p>

<p><span style="color: rgb(0,0,0);">Following aspects should be considered and as much as possible unified:</span></p>

<h6>Registry pattern</h6>

<ul>
	<li>auto scanning and init and destroy</li>
	<li>basic process engine creation</li>
	<li>support for multiple engines</li>
	<li>ant process engine initialization, caching and destruction. also, how does an ant task reference a process engine</li>
</ul>

<p><span style="color: rgb(0,0,0);">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).</span></p>

<h4>DB persistence</h4>

<p>Current architecture</p>

<p><span style="color: rgb(0,0,0);">Alternatives</span></p>

<ul>
	<li>JSON serialization into DB</li>
	<li>Cloud bigtable persistence</li>
</ul>

<p>Is the current architecture OK for 5.0?</p>

<h4><span style="color: rgb(0,51,102);"><strong>BPMN compatibility</strong></span></h4>

<p><span style="color: rgb(0,0,0);">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.</span></p>

<p><span style="color: rgb(0,0,0);">How do we make it easy for users to work with all these namespaces (if we decide to put custom conveniences in namespaces)</span></p>

<p><span style="color: rgb(0,0,0);">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.</span></p>

<p><span style="color: rgb(0,0,0);">Database upgrades. Automatic QA for upgrade.</span></p>

<h4>Cloud support</h4>

<p><span style="color: rgb(0,0,0);">The biggest question here is: How will we align the roadmap of researching the cloud solution with the roadmap towards 5.0GA in november?</span></p>

<h4>Query APIs</h4>

<p><span style="color: rgb(0,0,0);">An important aspect of cloud is the query API. We currently plan to build out the query API similar to jBPM 4. For example</span></p>

<table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>
taskService.createTaskQuery()
.processInstanceId(processInstanceId)
.activityName("task1")
.orderAsc(TaskQuery.PROPERTY_NAME)
</pre></td></tr></table>

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

<h4>Delegatable tasks</h4>

<ul>
	<li>Process instance migration</li>
	<li>History / reporting</li>
	<li>Email notifications / email form processor</li>
	<li>Business calendar</li>
	<li>Rules integration</li>
	<li>web service invocation</li>
	<li>Functional activity types / connectors: SQL, SAP/Abab, file, esb, xml transformation</li>
	<li>Identity pluggability + LDAP implementation</li>
	<li>Nomenclature</li>
</ul>

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

<h4>Other topics</h4>

<ul>
	<li>Discuss decision process</li>
	<li>Common 'terminology list'</li>
	<li>OSGi compatibility</li>
	<li>Process class loading</li>
	<li>To what extend can we have a dependency on Spring for core Activiti functionality?</li>
	<li>Naming of Job (name clash with spring Batch)</li>
	<li>Choreography: could it be a way to handle the multiplicity mismatches?</li>
	<li>Work out the cloud example: Elect the next european president, or process the voting for the next eurovision song contest.</li>
</ul>