On Sat, 24 Sep 2011 21:27:18 +0200, Robert Meggle <robert.meg...@care2x.org> wrote:
> Please see attached the roadmap for care2x 3.0. Some of you recognized > that there is something going on here - mostly on the branch called > "gettext". This is/was the "codename" for this new release what we > will fix now soon as first release candidate with several changes. > > Please read it carefully and feel free to contact me, Gjergj or Mauri > if you have questions. It is strange that after so many years in the Care2x project there are still people that do not have a clue of what a software package to support a Healthcare Information System is. About this paper, it could be a single page going like this: 1. The single most pragmatic and useful initiative in the Care2x project continues to be care2x_tz (I am sure that that's what has been keeping Care2x alive) 2. The wild goose chase of the last couple of years has been: PHP6, a phone interface, GUI reshaping. Like all the other previous wild goose chases in the Care2x project, this one did not and will not bring any new interest and people to the Care2x project. 3. There is a strong urge to "command and control" the project which, as everybody knows, is very difficult in any software project and totally impossible in an Open Source Software project. The page 9 of this paper is totally surrealistic corollary of this new round. 4. What Care2x really needs is a radical reduction in complexity, including: a) stop trying to be all things to all people b) use a single platform for development and develop code to a single platform: there were times when it was very difficult to understand if a given bug was related to the code, to the needed supporting software or to the emulator platform used to try to run all this in a different OS c) use a single widely available platform (price free and open source): with single, specific, OS flavor, DBMS, Web server, Web interface. Everybody must be using the same platform and living the same day-to-day problems, to be able to quickly see what is related to the Care2x code and what is due to idiosyncrasies of the platform; d) reduce the number of tables needed to make Care2x run to half of what they are now; e) modularize code. If the code logic blocs are really modularized (into closed black boxes), anybody will be able to quickly code and put into place an alternative bloc without breaking the rest of the system; f) do not attempt to "command and control" putative developers. Do not attempt to force project's roadmap, just to be able to convert it into a quick cash cow. In the case of the Care2x project people just keep arriving and leaving without seeing that illusive cow; Somewhere in the paper it is written: "Build a standardized process and business outcomes" Beware of the fact that standardization and innovation are opposite variables. Since Elpidio's first code releases we have had more and more standardization and less and less innovation and creativity... and it has not been the best thing regarding the project health and wealth. Regards, JA ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Care2002-developers mailing list Care2002-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/care2002-developers
