<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7654.12">
<TITLE>RE: [Gllug] open-source workflow / process software?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>You are really looking at two different types of systems.<BR>
<BR>
1. Issue tracking<BR>
There are many open source issue tracking systems, often<BR>
with a plethora of features you don't need. Hacking your<BR>
own may be quicker! (Eg: mantis, bugzilla, redmine.)<BR>
<BR>
2. Real time messaging<BR>
This sort of thing is often called 'enterprise message bus'<BR>
but can basically be anything that sends messages about.<BR>
HTTP, SMTP, instant messaging, etc. XMPP is an open protocol<BR>
that would be a good option for integration here if you<BR>
want to be able to support retries and push-based delivery<BR>
to people while they are roaming about, on their mobile, etc.<BR>
- Some are store/forward, some realtime<BR>
- Some queue forever, some die after awhile failing to<BR>
deliver (ala SMS from the GSM world)<BR>
<BR>
The above are just vague ideas based on the info you gave.<BR>
<BR>
Issues trackers are better for complex process flow.<BR>
<BR>
Something custom-hacked is better for simplistic scenarios<BR>
where custom integration is the key and requirements are unlikely<BR>
to change significantly over time (eg: bring in 2 departments<BR>
of nontechnical personnel...)<BR>
<BR>
- Walter, in sunny .au</FONT>
</P>
</BODY>
</HTML>