oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi Diego and All,

We are redefining what OSHIP is in the following way.  It is the Open
Source Healthcare Information Platform coded in multiple programming
languages. 

So, my idea is that we have a development branch for each of the
following:

OSHIPpy - Python

OSHIPrb - Ruby

OSHIPjava -Java

OSHIPlua - Lua

OSHIPcpp - C++


We have code for the first three in various states of completion.  So
what are the pros and cons of using one OSHIP repository divided into
separate branches as compared to creating new projects for each?  I lean
towards using the same project with multiple repositories.  It certainly
makes management easier and will easily allow for Blueprints etc. to be
applied to all when it makes sense to do so.

Thoughts?

Cheers,
Tim



-- 
***************************************************************
Timothy Cook, MSc
Project Lead - Multi-Level Healthcare Information Modeling
http://www.mlhim.org 

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home

Attachment: signature.asc
Description: This is a digitally signed message part