On Saturday 02 December 2006 16:04, Simon James wrote:
>  I wonder how many capable
> contributors there are currently in Australia (or internationally) to
> assist with the ongoing development of Argus or any other health related
> open source projects?

At that stage, it seems the Argus people do not want any assistance in 
development. Maybe even a good thing if the source of software of that kind 
gets ruled by a tight fist. In any case, I have nothing against that. Source 
coming form a single hand has it's advantages.

It' only about the *option*.
Previously, we would have liked to use Argus with an alternative backend 
(Postgres), to be able to use the backend in a proper client-server 
relationship and not just (mis?)using Interbase as a bloated file system 
replacement with search capabilities, to be able too use it with keys and CAs 
of our choice rather than being forced into HeSA.

Syan Tan has actually made most of these necessary changes - on the old source 
tree. To my knowledge, none of these changes were incorporated into the 
current tree. Makes it tedious and frustrating I guess, so I myself won't 
even start

My surgery IT infrastructure is set up to strictly separate data from 
application, and application from system. Makes backing up a trivial and 
reliable unattended exercise, and makes securing the system a much easier 
job. Argus in it's current incarnation would break my paradigm, make my 
backups more complicated and hence less reliable, and I would have to start 
rethinking implications for network security. 

However, if we could fork Argus into our own source tree and simply keep 
patching it with whatever Argus produces, we could have the one solution that 
suits us so well (Postgres backend on separate database server, application 
on application server, HeSA but one of several possible CAs)  regardless of 
whether it would suit others or not. Not having reliable access to current 
code though makes this again a futile exercise

Horst
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk

Reply via email to