← Back to team overview

mlhim-owners team mailing list archive

Re: Documentation

 

Hi Tim,

No thoughts from me. I think you clarified the issue very well.

Cheers, Luciana.


Em 19/02/2011 10:34, Tim Cook escreveu:
> Hi Ian,
> 
> These should probably be in an FAQ on the MLHIM website.  I am certain
> that there is some confusion due to the fact that there are several
> layers/areas to MLHIM as a project. 
> 
> On Fri, 2011-02-18 at 19:03 -0430, Ian Lawrence wrote:
>> Is the idea to attract developers or end users to the project? (either
>> are equally valid but the answer is important to the choice of tool)
> 
> Exactly.  When I talk about MLHIM.  I am speaking about the
> specifications primarily as well as any governance documents and overall
> network aspects. So the interested parties here are health informatics
> professionals and allied healthcare workers interested in information
> management.
> 
> OSHIP - The concept of a an Open Source Health Information Platform.
> Platform meaning something that contains the reference model in software
> along with other tools to make application development and deployment
> easier/familiar at that level.
> 
> OSHIPpy - the Python language implementation of OSHIP
> OSHIPjava - the Java language implementation of OSHIP
> OSHIPrb - the Ruby language implementation of OSHIP
> OSHIPlua - the Lua language implementation of OSHIP
> 
> So the Python implementation is a good place to use rst and Sphinx; for
> the platform documentation. In fact we had discussed just that issue on
> the OSHIP-dev mailing list recently.  Anyone is welcome to join that
> group but it is moderated simply because all members have commit access.
> https://launchpad.net/~oship-dev 
> 
> There is also an OSHIP-users list for application developers.  However,
> there isn't much going on here now due to the lack of platforms at this
> time. :) https://launchpad.net/~oship-users 
> 
> 
>> For example the Django project docs and indeed site itself is
>> completely written in rst and it is extremely popular with developers.
> 
> Your input would be VERY welcome on this list Ian. 
> 
>> I cannot think of one successful open source project which has
>> documentation based around ODF templates. (not saying there aren't but
>> just that I am not aware of any)
> 
> I agree.  But of course MLHIM is more about overall specifications than
> one implementation.  I think we have a different audience here.  
> 
> 
> Other thoughts?
> 
> 
> Tim
> 
> 
> 
> 
> 

-- 
Esta mensagem foi verificada pelo sistema de antiv�s e
 acredita-se estar livre de perigo.




References