mlhim-owners team mailing list archive

[Timothy Cook <timothywayne.cook@xxxxxxxxx>]

Excellent!


On Fri, Mar 25, 2011 at 6:36 PM, Luciana Tricai Cavalini <lutricav@xxxxxxxxx
> wrote:

> Hi All,
>
> Down here in Brazil, BrOffice is already LibreOffice.
> So, +1.
>
> Cheers, Luciana.
>
>
> Em 24/03/2011 12:19, Timothy Cook escreveu:
> > Hi All,
> >
> > For those not aware.  The OpenOffice project has been forked to
> LibreOffice.
> > It seems to be completely justified to me based on the new owner (Oracle)
> > requiring a copyright assignment.  This is one of the main reasons that
> > MLHIM exists as well.
> >
> > Therefore, unless there is some huge compelling reason not to do so.  I
> > suggest that we now use LibreOffice instead of OpenOffice.
> >
> > Some of the justification is recorded here:
> > http://en.wikipedia.org/wiki/LibreOffice
> >
> > Regards,
> > Tim
> >
> > On Fri, Feb 18, 2011 at 3:01 PM, Tim Cook <timothywayne.cook@xxxxxxxxx
> >wrote:
> >
> >> Hi All,
> >>
> >> As you  all may be aware.  We selected the LyX Document Processor  and
> >> its LaTex format for all of our documentation needs.   However, given
> >> all of the positive things going for LyX; popularity is not one of
> >> them.  Creating and maintaining the massive amounts of documents the
> >> MLHIM project requires is an effort that should be shared among many
> >> people.
> >>
> >> Therefore we should use something that is more popular and familiar and
> >> work around the issues that may arise from it.   It is my opinion that
> >> "it" is OpenOffice.org Writer.  I brought it up in a meeting with a few
> >> of the other MLHIM Owners today and they were in agreement with me.
> >>
> >> If anyone has other ideas or just a disagreement with this decision then
> >> please speak up.  Otherwise I will move forward converting the LyX
> >> documents to OOo docs.
> >>
> >> I will also ask for help in creating a good template for MLHIM
> >> documents.  Someone with some experience in this area would be nice (I
> >> am really bad at it).  Maybe start with ISO standards templates, IETF,
> >> CEN, ANSI ?  and make them a MLHIM Specifications template.
> >>
> >> I prefer that you reply on the mailing list but if you can help and only
> >> want to reply to me that is fine too.
> >>
> >> Thanks,
> >> 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
> >>
> >>
> >
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~mlhim-owners
> > Post to     : mlhim-owners@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~mlhim-owners
> > More help   : https://help.launchpad.net/ListHelp
>
> --
> Esta mensagem foi verificada pelo sistema de antivírus e
>  acredita-se estar livre de perigo.
>
>


-- 
================
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